From: Linux for blind general discussion <blinux-list@redhat.com>
To: Linux for blind general discussion <blinux-list@redhat.com>
Subject: Re: text browsers and current web standards
Date: Fri, 23 Jun 2017 12:39:36 -0400 (EDT) [thread overview]
Message-ID: <alpine.NEB.2.20.1706231238500.5107@panix1.panix.com> (raw)
In-Reply-To: <CAO2sX31stFjZt3HYO2uME7kUMGSmXhof=tkL-gxA+2WV623pfg@mail.gmail.com>
edbrowse does support some javascript but not the whole set if memory
serves.
On Fri, 23 Jun 2017, Linux for blind general discussion wrote:
> Date: Fri, 23 Jun 2017 08:31:34
> From: Linux for blind general discussion <blinux-list@redhat.com>
> To: blinux-list@redhat.com
> Subject: Re: text browsers and current web standards
>
> As much as I think every web "standard" aside from vanilla HTML should
> be avoided unless absolutely necessary(and even then, why use HTML if
> plain text can get the job done?), I agree it's a necessary evil to
> have the means of dealing with pages made by those who put eye candy
> and fancy layouts before content and ease of use(seriously, some
> websites make me wonder if whoever designed the UI even knows what a
> keyboard is). I mean, in web terms, JavaScript is as old as dirt, yet
> as far as I know, there is no text mode browser with even partial
> javascript support, and while I have NoScript in my Firefox to block
> all that JavaScript that likes to trip up Orca, some sites are
> completely unusable without the monstrosity.
>
> Anyways, as Aptitude isn't getting any hit for clifox even after
> adding contrib and non-free to my sources.list, mind providing a link
> to more information or perhaps a link to download a development build?
> I suspect a hypothetical modern text browser with it's own backend
> would be much smaller, but being able to use Firefox from the terminal
> and get rid of Orca and what of my xserver Firefox doesn't force me to
> install would definitely be a step in the right direction as far as
> I'm concerned.
>
>
--
next prev parent reply other threads:[~ UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion [this message]
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
` Linux for blind general discussion
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=alpine.NEB.2.20.1706231238500.5107@panix1.panix.com \
--to=blinux-list@redhat.com \
/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).