From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: 34920@debbugs.gnu.org
Subject: bug#34920: 27.0.50; Poor eww rendering of SourceHut file "trees"
Date: Thu, 21 Mar 2019 14:48:53 +0100 [thread overview]
Message-ID: <m3d0mkz6be.fsf@gnus.org> (raw)
In-Reply-To: <jwvd0mkl680.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 21 Mar 2019 09:20:02 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
> 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)
It's seldom just one CSS file, and CSS files these days are often big
auto-generated monstrosities...
> 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)?
(3) is minor, while (2) could be an issue.
But my point is that since we support very little CSS, spending time
fetching something that in 99% of the cases will make no difference to
our rendering is a disservice to the users. eww is slow enough as it
is.
>> 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?
Accept that most complex web pages will look like crap in shr and use it
for what it's suited for. :-)
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-03-21 13:48 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-03-19 20:00 bug#34920: 27.0.50; Poor eww rendering of SourceHut file "trees" Stefan Monnier
2019-03-19 20:22 ` Lars Ingebrigtsen
2019-03-19 21:49 ` Stefan Monnier
2019-03-19 21:54 ` Lars Ingebrigtsen
2019-03-21 1:01 ` Stefan Monnier
2019-03-21 8:19 ` Lars Ingebrigtsen
2019-03-21 12:14 ` Stefan Monnier
2019-03-21 12:44 ` Lars Ingebrigtsen
2019-03-21 13:20 ` Stefan Monnier
2019-03-21 13:48 ` Lars Ingebrigtsen [this message]
2019-03-21 17:09 ` Basil L. Contovounesios
2019-03-22 0:39 ` Stefan Monnier
2019-03-23 15:24 ` Lars Ingebrigtsen
2019-05-13 19:32 ` Lars Ingebrigtsen
2019-04-09 23:54 ` Noam Postavsky
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
List information: https://www.gnu.org/software/emacs/
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=m3d0mkz6be.fsf@gnus.org \
--to=larsi@gnus.org \
--cc=34920@debbugs.gnu.org \
--cc=monnier@iro.umontreal.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.
Code repositories for project(s) associated with this public inbox
https://git.savannah.gnu.org/cgit/emacs.git
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).