bug#34920: 27.0.50; Poor eww rendering of SourceHut file "trees"

[Stefan Monnier <monnier@iro.umontreal.ca>]

> shr will never support more than an itsy-bitsy CSS subset (due to both
> speed and layout considerations),

[ Never say never, but, yes, that sounds about right.  ]

> so fetching CSS externally would be a disservice to the users.

Not sure I understand why you think so: is it because of (1) the time wasted
fetching it or (2) the slowdown imposed by parsing it or (3) the slowdown
imposed on the rendering when the CSS is large or (4) ...?

My impression is that just (1) would rarely be a performance
problem (assuming it's just one CSS file) and that the parsing could
ditch all the irrelevant properties we don't support anyway so the
impact of (3) should be minor.  So is it (2)?

> And asking web designers to change their pages so that they'll look
> better in non-CSS browser isn't really scaleable.  :-)

So what the solution?


        Stefan