Re: [Lynx-dev] Lynx access to gmail accounts

[Jude DaShiell]

I can't recommend edbrowse now since for the last few versions the
setup.ebrc script has been removed.  That script when run asks a user
questions and using their answers sets up their .ebrc file for them.  That
is the configuration file on which edbrowse runs.  Having edbrowse on my
machine I failed to configure everything properly and was unable to access
gmail in the usual way.  The good news is edbrowse still has support and
is up to version 3.8.0 so it's possible the setup.ebrc script will be
restored to a future version.


On Wed, 17 Nov 2021, Karen Lewellen wrote:

> Jude,
> To be specific.
> Edbrowse can visit a page like this,
> mail.google.com
> allow one to enter their username and password,
> Then present  the basic html webpage for gmail?
> Karen
>
>
>
> On Wed, 17 Nov 2021, Jude DaShiell wrote:
>
> > edbrowse can do gmail.  The edbrowse approach is to take all javascript in
> > and ignore everything that doesn't make sense for a text terminal.
> >
> >
> > On Wed, 17 Nov 2021, David Woolley wrote:
> >
> >> On 17/11/2021 22:02, dan d. wrote:
> >>> For that matter, is there a general solution for web pages which refuse
> >>> lynx
> >>> for that reason?
> >>
> >> There can't be any general solution other than to use a browser that fully
> >> implements HTML 5, EcmaScript, and the associated browser and document and
> >> CSS
> >> object models.  That would be such a radical rewrite that would have little
> >> or
> >> no original code, or code structure, left.
> >>
> >> I believe other text browser implement certain common idioms, but are not
> >> general solutions.
> >>
> >> I'm not convinced it is possible in a text browser, but the way to do it
> >> would
> >> be to put a character cell rendering engine onto the Firefox or Chrome
> >> engines, not to adapt the Lynx code.
> >>
> >> (To get something that worked well in text-only, but only for well written
> >> pages, you would also need to fully implement Aria support. This is a way
> >> of
> >> telling accessibility tools the real semantics of the page, even when the
> >> HTML
> >> semantics are only used for visual effect, and therefore requires
> >> accessibility aware authoring.)
> >>
> >>
> >
> >
>