From: Jim Porter <jporterbugs@gmail.com>
To: "Eli Zaretskii" <eliz@gnu.org>,
"Sebastián Monía" <sebastian@sebasmonia.com>
Cc: 59549@debbugs.gnu.org, nicholasdrozd@gmail.com
Subject: bug#59549: EWW ordered list display irregularity
Date: Tue, 5 Nov 2024 11:50:19 -0800 [thread overview]
Message-ID: <aaf83e70-a232-8f58-c07a-de5561ac64a7@gmail.com> (raw)
In-Reply-To: <86a5edtxms.fsf@gnu.org>
On 11/5/2024 9:10 AM, Eli Zaretskii wrote:
>> From: Sebastián Monía <sebastian@sebasmonia.com>
>> Cc: 59549@debbugs.gnu.org
>> Date: Tue, 05 Nov 2024 09:38:28 -0500
>>
>> If we think it is OK to render the empty items, then we could close this
>> bug instead of merging. Either way, one less item in the TODO list ;)
>
> Thanks.
>
> I'm not enough of an HTML expert to be sure that this is the right fix
> in general, sorry. I hope someone else will be able to tell.
I think the current behavior with the empty list item is correct,
actually. Other browsers don't show the list item (and renumber the list
as appropriate) because the CSS rule for ".mw-empty-elt" has "display:
none". EWW/SHR don't parse CSS[1], and so we show the empty item.
You can see the same "problem" in Firefox if you load
<https://en.wiktionary.org/wiki/locus#Noun> and go to View -> Page Style
-> No Style. Since that's roughly what EWW/SHR is doing, I think we're
consistent with other browsers here.
[1] Well, they can parse some limited inline CSS using the "style"
attribute, but that doesn't apply here since the styling comes from a
CSS class.
next prev parent reply other threads:[~2024-11-05 19:50 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-11-24 18:29 bug#59549: EWW ordered list display irregularity Nicholas Drozd
2024-09-23 19:07 ` Sebastián Monía
2024-10-03 18:27 ` Sebastián Monía
2024-11-05 14:38 ` Sebastián Monía
2024-11-05 17:10 ` Eli Zaretskii
2024-11-05 19:50 ` Jim Porter [this message]
2024-11-06 3:20 ` Sebastián Monía
2024-11-06 12:37 ` Eli Zaretskii
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
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=aaf83e70-a232-8f58-c07a-de5561ac64a7@gmail.com \
--to=jporterbugs@gmail.com \
--cc=59549@debbugs.gnu.org \
--cc=eliz@gnu.org \
--cc=nicholasdrozd@gmail.com \
--cc=sebastian@sebasmonia.com \
/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 external index
https://git.savannah.gnu.org/cgit/emacs.git
https://git.savannah.gnu.org/cgit/emacs/org-mode.git
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.