- From: Emilio Cobos Álvarez via GitHub <sysbot+gh@w3.org>
- Date: Thu, 16 Nov 2023 15:56:42 +0000
- To: public-css-archive@w3.org
emilio has just created a new issue for https://github.com/w3c/csswg-drafts: == [css-content] content: "" should probably generate no text nodes == ... because an empty text node would generate a baseline. Here's a [test-case](https://bug1855583.bmoattachments.org/attachment.cgi?id=9363953) that shows the difference on Chromium (because Chromium has a bogus optimization that prevents an empty text node from having a layout box unless editable). https://drafts.csswg.org/css-content/#strings is not particularly clear on what exactly the generated DOM would look like for `content: ""`. Right now browsers differ but not generating a text node seems reasonable behavior, and we'd be willing to align Firefox with other browsers assuming the spec is updated to be explicit about this. This came up in https://bugzilla.mozilla.org/show_bug.cgi?id=1855583 cc: @dshin-moz, @tabatkins, @fantasai Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/9606 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 16 November 2023 15:56:44 UTC