W3C home > Mailing lists > Public > public-css-archive@w3.org > November 2017

[csswg-drafts] [css-list-3] List-item outside markers

From: François REMY via GitHub <sysbot+gh@w3.org>
Date: Fri, 03 Nov 2017 18:20:16 +0000
To: public-css-archive@w3.org
Message-ID: <issues.opened-271072149-1509733215-sysbot+gh@w3.org>
FremyCompany has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-list-3] List-item outside markers ==
https://drafts.csswg.org/css-lists-3/
> This spec is not yet ready for implementation. It exists in this repository to record the ideas and promote discussion. 

https://drafts.csswg.org/css-lists-3/#positioning
> This section is not ready for implementation. It is an unreviewed rough draft that hasn’t even been properly checked for Web-compatibility.

http://www.w3.org/TR/CSS22/generate.html#propdef-list-style-position
> The marker box is outside the principal block box. The position of the list-item marker adjacent to floats is **undefined** in CSS 2.2. CSS 2.2 **does not specify** the precise location of the marker box or its position in the painting order, but does require that for list items whose 'direction' property is 'ltr' the marker box be on the left side of the content and for elements whose 'direction' property is 'rtl' the marker box be on the right side of the content. The marker box is fixed with respect to the principal block box's border and does not scroll with the principal block box's content. In CSS 2.2, a UA **may hide** the marker if the element's 'overflow' is other than 'visible'. (This is expected to change in the future.) The size or contents of the marker box **may affect** the height of the principal block box and/or the height of its first line box, and **in some cases may** cause the creation of a new line box.

That's a lot of things left undefined. I think it's more than time to clean up this mess, and I'm glad to report it should be easier than fixing tables :)

I intend to describe at TPAC how Edge implements markers, which I think is similar to how Chrome implements it (bugs and tweaks apart) and would like to start a rewrite of the marker spec to align with this "ideal" implementation so we can all fix bugs and finally achieve interop here. 


Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/1934 using your GitHub account
Received on Friday, 3 November 2017 18:20:19 UTC

This archive was generated by hypermail 2.3.1 : Friday, 3 November 2017 18:20:19 UTC