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: Sat, 23 Mar 2019 16:24:54 +0100 [thread overview]
Message-ID: <m3zhply5o9.fsf@gnus.org> (raw)
In-Reply-To: <jwv1s2zlp6c.fsf-monnier+emacs@gnu.org> (Stefan Monnier's message of "Thu, 21 Mar 2019 20:39:32 -0400")
Stefan Monnier <monnier@iro.umontreal.ca> writes:
>> Would an opt-in user option not suit, assuming an initial PoC succeeds?
>
> I was thinking a command that you can run to re-render with the remote
> CSS, but that's basically the same idea.
>
> If it gives useful results, we could go crazy and introduce some config
> var indicating which remote CSS are worth downloading and which aren't.
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.
--
(domestic pets only, the antidote for overdose, milk.)
bloggy blog: http://lars.ingebrigtsen.no
next prev parent reply other threads:[~2019-03-23 15:24 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 [this message]
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=m3zhply5o9.fsf@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).