From: Deedra Waters <curi0315@tampabay.rr.com>
To: speakup@braille.uwo.ca
Subject: Re: asp
Date: Thu, 25 Apr 2002 14:29:33 -0400 (EDT) [thread overview]
Message-ID: <Pine.LNX.3.96.1020425142819.24204A-100000@deedra> (raw)
In-Reply-To: <000b01c1ec86$6ebf7b20$7f7ef59b@essex.ac.uk>
it should be. but if lynx sees it as bad html, then maybe there's
something I'm missing somewhere.
it works fine with links, but because of the way that the page is designed
it's hard to navigate with links, because of the way the page looks on the
screen.
On Thu, 25 Apr 2002, Saqib Shaikh wrote:
> Someone please correct me if I'm wrong, but since ASP is server-side
> technology, by the time the page gets to the local machine it should be
> using standard-ish HTML?
>
> Saqib
> ----- Original Message -----
> From: "Deedra Waters" <curi0315@tampabay.rr.com>
> To: <speakup@braille.uwo.ca>
> Sent: Thursday, April 25, 2002 7:12 PM
> Subject: Re: asp
>
>
> > It acceps cookies just fine. it just comes back with something about bad
> > html, use trace to diagnose, or something along those lines.
> >
> >
> > On Thu, 25 Apr 2002, Janina Sajka wrote:
> >
> > > Are you accepting the .asp cookies?
> > >
> > > That tends to be a threshold question. No cookies, no content from .asp.
> > >
> > > BTW: That's not specific to lynx. It's specific to cookies.
> > >
> > > On Thu, 25 Apr 2002, Deedra Waters wrote:
> > >
> > > > Does anyone know of a text based webbrouse that supports asp? I'm
> > > > currently using lynx, but it doesn't seem to like the pages much.
> > > >
> > > >
> > > > _______________________________________________
> > > > Speakup mailing list
> > > > Speakup@braille.uwo.ca
> > > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > > >
> > >
> > > --
> > >
> > > Janina Sajka, Director
> > > Technology Research and Development
> > > Governmental Relations Group
> > > American Foundation for the Blind (AFB)
> > >
> > > Email: janina@afb.net Phone: (202) 408-8175
> > >
> > > Chair, Accessibility SIG
> > > Open Electronic Book Forum (OEBF)
> > > http://www.openebook.org
> > >
> > >
> > > _______________________________________________
> > > Speakup mailing list
> > > Speakup@braille.uwo.ca
> > > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> > >
> >
> >
> > _______________________________________________
> > Speakup mailing list
> > Speakup@braille.uwo.ca
> > http://speech.braille.uwo.ca/mailman/listinfo/speakup
> >
>
>
> _______________________________________________
> Speakup mailing list
> Speakup@braille.uwo.ca
> http://speech.braille.uwo.ca/mailman/listinfo/speakup
>
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
asp Deedra Waters
` asp Janina Sajka
` asp Deedra Waters
` asp Saqib Shaikh
` Deedra Waters [this message]
` asp Janina Sajka
` asp Igor Gueths
` asp Janina Sajka
` asp Deedra Waters
` asp Toby Fisher
` asp Alex Snow
` asp Toby Fisher
` asp Alex Snow
[not found] ` <Pine.LNX.4.33.0204260056250.8774-100000@frontdoor.g0ucu.fr eeserve.co.uk>
` asp Liz Hare
` asp Alex Snow
` asp Toby Fisher
` asp Deedra Waters
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=Pine.LNX.3.96.1020425142819.24204A-100000@deedra \
--to=curi0315@tampabay.rr.com \
--cc=speakup@braille.uwo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for read-only IMAP folder(s) and NNTP newsgroup(s).