From: Tomasz Piotrowski <tpiotrowski@fizyka.umk.pl>
To: Eli Zaretskii <eliz@gnu.org>
Cc: tpiotrowski@is.umk.pl, Lars Ingebrigtsen <larsi@gnus.org>,
37159@debbugs.gnu.org
Subject: bug#37159: 26.1; svg images in eww
Date: Tue, 27 Aug 2019 10:01:52 +0200 [thread overview]
Message-ID: <C19DB789-FF9F-460A-A5B7-51F0200C3E33@fizyka.umk.pl> (raw)
In-Reply-To: <83o90bdp7b.fsf@gnu.org>
Well, my opinion on this is that either I have to keep switching to Chrome to use wikipedia, or I could use eww for my work. I don’t know how many others have the same issue, but it is a serious flaw in eww from my point of view. Many thanks to Lars for pinpointing the reason of certain svg images not rendering properly in eww.
Tomasz
Wiadomość napisana przez Eli Zaretskii <eliz@gnu.org> w dniu 27.08.2019, o godz. 09:47:
>> From: Lars Ingebrigtsen <larsi@gnus.org>
>> Cc: tpiotrowski@is.umk.pl, 37159@debbugs.gnu.org
>> Date: Tue, 27 Aug 2019 08:59:20 +0200
>>
>> I'm not quite sure what a solution here would be. shr could parse the
>> SVG data (it's just XML, after all) and insert a stroke (i.e.,
>> foreground) colour if none is specified, and one that's sufficiently
>> different from the background colour that the image would be kinda-sorta
>> readable.
>>
>> But is it worth it just to display these unusually degenerate SVG
>> images?
>
> I don't know enough to have an opinion that matters.
>
>>> Btw, why does EWW break the text line when it encounters an image?
>>
>> When doing the layout, in general the dimensions of the images isn't
>> known -- the images are fetched asynchronously after displaying the
>> text.
>>
>> There's also a historical reason -- the code was written before shr did
>> pixel-based layouts, so even if it knew the dimensions, it couldn't do
>> anything about it. That could be fixed now (so that if the <img> has a
>> width attribute, the layout engine could use it and insert the
>> placeholder there).
>
> Something to work on in the future, I think.
>
> Thanks.
next prev parent reply other threads:[~2019-08-27 8:01 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-23 12:55 bug#37159: 26.1; svg images in eww Tomasz Piotrowski
2019-08-23 17:29 ` Lars Ingebrigtsen
2019-08-24 7:56 ` Tomasz Piotrowski
2019-08-25 5:49 ` Lars Ingebrigtsen
2019-08-25 6:21 ` Tomasz Piotrowski
2019-08-25 7:35 ` Eli Zaretskii
2019-08-25 8:10 ` Tomasz Piotrowski
2019-08-25 8:20 ` Eli Zaretskii
2019-08-25 10:12 ` Tomasz Piotrowski
2019-08-25 10:15 ` Tomasz Piotrowski
2019-08-26 4:56 ` Lars Ingebrigtsen
2019-08-26 5:33 ` Tomasz Piotrowski
2019-08-26 6:25 ` Tomasz Piotrowski
2019-08-26 7:48 ` Eli Zaretskii
2019-08-26 7:50 ` Lars Ingebrigtsen
2019-08-26 8:02 ` Eli Zaretskii
2019-08-27 6:59 ` Lars Ingebrigtsen
2019-08-27 7:47 ` Eli Zaretskii
2019-08-27 8:01 ` Tomasz Piotrowski [this message]
2019-09-04 15:04 ` Tomasz Piotrowski
2019-09-09 15:20 ` Tomasz Piotrowski
2019-09-14 8:59 ` Alan Third
2019-09-14 12:05 ` Lars Ingebrigtsen
2019-09-14 14:49 ` Lars Ingebrigtsen
2019-09-14 15:51 ` Eli Zaretskii
2019-09-14 15:54 ` Alan Third
2019-09-15 12:17 ` Lars Ingebrigtsen
2019-09-16 8:44 ` Tomasz Piotrowski
2019-09-16 12:27 ` Lars Ingebrigtsen
2019-09-16 14:29 ` Tomasz Piotrowski
2019-09-16 18:34 ` Lars Ingebrigtsen
2019-09-18 7:18 ` Tomasz Piotrowski
2019-09-18 13:43 ` Lars Ingebrigtsen
2019-09-19 8:20 ` Tomasz Piotrowski
2019-09-19 11:02 ` Alan Third
2019-09-19 13:59 ` Lars Ingebrigtsen
2019-09-20 18:56 ` Alan Third
2019-09-20 19:09 ` Tomasz Piotrowski
2019-09-20 19:18 ` Lars Ingebrigtsen
2019-09-20 19:22 ` Tomasz Piotrowski
2019-09-20 19:26 ` Eli Zaretskii
2019-09-20 20:48 ` Tomasz Piotrowski
2019-09-21 6:28 ` Eli Zaretskii
2019-09-21 17:32 ` Tomasz Piotrowski
2019-09-20 20:56 ` Lars Ingebrigtsen
2019-08-26 4:54 ` Lars Ingebrigtsen
2019-08-26 7:46 ` Eli Zaretskii
2019-08-26 7:49 ` Tomasz Piotrowski
2019-08-25 22:34 ` Jordan Wilson
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=C19DB789-FF9F-460A-A5B7-51F0200C3E33@fizyka.umk.pl \
--to=tpiotrowski@fizyka.umk.pl \
--cc=37159@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=larsi@gnus.org \
--cc=tpiotrowski@is.umk.pl \
/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).