Re: HTML-Info design

[Lars Ingebrigtsen]

Ivan Shmakov <address@hidden> writes:

>       Given that SHR only does columns inside <table />, – using the
>       closest <td /> or <th /> ancestor for the purpose would solve
>       the issue.

At some point, eww will also support CSS layouts.

>       However, given that using tables for layout tends to create
>       accessibility issues out of nothing (did I hear someone saying
>       Emacspeak in this discussion?), why exactly can’t we provide
> the
>       user a way to get rid of all the “layout” tables at once?

The layouts sometimes have semantic meaning, and there's no easy way to
separate a "layout table" from a "non-layout table".  I just got a
ticket confirmation email, for instance, that had a lot of "bla bla",
but would have been completely incomprehensible if the things that
needed to be lined up hadn't been lined up.

People use layouts because they use layouts, and eww should strive,
within what's practical given Emacs' layout engine, to replicate those
layouts.  Having a "readability" command to make the layout go away can
also be nice in some circumstances, but that should remain a user
command.  As it is now.

-- 
(domestic pets only, the antidote for overdose, milk.)
  bloggy blog http://lars.ingebrigtsen.no/