From: Lars Ingebrigtsen <larsi@gnus.org>
To: Stefan Monnier <monnier@iro.umontreal.ca>
Cc: "Basil L. Contovounesios" <contovob@tcd.ie>, 34920@debbugs.gnu.org
Subject: bug#34920: 27.0.50; Poor eww rendering of SourceHut file "trees"
Date: Mon, 13 May 2019 15:32:04 -0400 [thread overview]
Message-ID: <87ef52up57.fsf@mouse.gnus.org> (raw)
In-Reply-To: <m3zhply5o9.fsf@gnus.org> (Lars Ingebrigtsen's message of "Sat, 23 Mar 2019 16:24:54 +0100")
Lars Ingebrigtsen <larsi@gnus.org> writes:
> That's a possibility, but like I said, shr supports such a minimal
> subset of CSS that you're not going to see much, if any, difference.
>
> And there's no way to determine what CSS files are going to contain the
> stuff we support, so you'd have to fetch and parse them all.
Anyway, making shr being ACID compliant (or something along those lines)
is, I think, beyond the scope of a bug report -- if shr is going to
render HTML according to the CSS specs, it's a monumental project (and
is, I believe) make shr so slow that you can't use it, anyway.
So I'm closing this bug report. :-/
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-05-13 19:32 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
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 [this message]
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=87ef52up57.fsf@mouse.gnus.org \
--to=larsi@gnus.org \
--cc=34920@debbugs.gnu.org \
--cc=contovob@tcd.ie \
--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).