Intent to implement and ship: CSS counter-set property
Summary: The counter-set CSS property assigns an absolute value to a CSS counter. (It behaves the same as counter-increment but assigns instead of increments.) It will be used internally to map to set the value of the built-in 'list-item' counter (see separate announcement following this). Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1518201 Link to standard: https://drafts.csswg.org/css-lists/#propdef-counter-set Platform coverage: All platforms Estimated or target release: Firefox 68 Preference behind which this will be implemented: none DevTools bug: none Do other browser engines implement this? No, as far as I know. web-platform-tests: I added some under css/css-lists/. (It will also be tested indirectly through .) Is this feature restricted to secure contexts? No /Mats ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Intent to implement and ship: built-in CSS counter 'list-item'
Summary: The built-in 'list-item' counter is used to implement HTML / (and other elements with display:list-item) using CSS. I'm also removing our old (frame-based) code for list item counters, which had a number of decades-old bugs (bug 4522 et al), was rather slow (bug 3246) and crashy (bug 1515124). Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=288704 Link to standard: https://drafts.csswg.org/css-lists/#declaring-a-list-item Platform coverage: All platforms Estimated or target release: Firefox 68 Preference behind which this will be implemented: none DevTools bug: none Do other browser engines implement this? No, as far as I can tell. web-platform-tests: I added a couple of WPTs in css/css-lists/ and there are some in css/CSS2/lists which we now pass. Also, given that we now use this built-in counter for all display:list-item elements we should have basic coverage from existing tests for those. Is this feature restricted to secure contexts? No /Mats ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Intent to implement and ship: CSS ::marker pseudo-element
Summary: The ::marker pseudo-element represents the automatically generated marker box of a list item. It allows authors to style the marker and generate content for it through its 'content' property (like ::before/::after). Bug: https://bugzilla.mozilla.org/show_bug.cgi?id=205202 Animation support is pending: https://bugzilla.mozilla.org/show_bug.cgi?id=1538618 Link to standard: https://drafts.csswg.org/css-pseudo-4/#marker-pseudo https://drafts.csswg.org/css-lists/#markers https://github.com/w3c/csswg-drafts/issues/3499 Platform coverage: All platforms Estimated or target release: Firefox 68 Preference behind which this will be implemented: none DevTools bug: none (I've checked that a ::marker shows up as a pseudo in the panel with ::before/::after and it appears to work fine) Do other browser engines implement this? Safari implements limited support for ::marker (it doesn't support the 'content' property, and it has no support for the built-in 'list-item' counter, both which are major pieces of this general feature). Chrome supports none of it AFAICT. https://wpt.fyi/results/css/css-pseudo web-platform-tests: There are some tests in css/css-pseudo/ and I've added a bunch more. Is this feature restricted to secure contexts? No Many thanks to Emilio who patiently reviewed all of these list item related changes. /Mats ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to implement and ship: built-in CSS counter 'list-item'
Some time ago we spent some effort documenting a cross-browser mostly-interoperable behavior for list-item-like behaviors, in https://github.com/whatwg/html/pull/2002 and linked threads. The result is the spec at https://html.spec.whatwg.org/multipage/grouping-content.html#list-owner and the tests at https://github.com/web-platform-tests/wpt/tree/master/html/semantics/grouping-content/the-ol-element . The spec at https://drafts.csswg.org/css-lists/#declaring-a-list-item seems to contradict that hard-fought consensus. It states simply that > Additionally, list items automatically increment the special list-item > counter. Unless the counter-increment property manually specifies a different > increment for the list-item counter, it must be incremented by 1 on every > list item, at the same time that counters are normally incremented. This omits all the details at https://html.spec.whatwg.org/multipage/grouping-content.html#ordinal-value , e.g. reversed="", the collection of owned list items, value="" attribute parsing, etc. It seems like a regression to implement list item numbering according to that spec, instead of according to HTML. > web-platform-tests: An important thing to test here is the result of getComputedStyle on list items as a result of this change. HTML specifies that ordinal values are displayed on list items without any counter CSS properties involved, and from what I can tell, https://drafts.csswg.org/css-lists/ does not change that. (The appendix at https://drafts.csswg.org/css-lists/#ua-stylesheet is informative, not normative.) So, including tests that getComputedStyle continues to return no results for the counter-related properties or pseudo-elements seems important to maintaining interop on this front. ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
Re: Intent to implement and ship: built-in CSS counter 'list-item'
On Sunday, March 24, 2019 at 10:21:10 PM UTC-7, Domenic Denicola wrote: > the tests at > https://github.com/web-platform-tests/wpt/tree/master/html/semantics/grouping-content/the-ol-element correction, https://github.com/web-platform-tests/wpt/tree/master/html/semantics/grouping-content/the-li-element is where most of the tests landed. The pull request was https://github.com/web-platform-tests/wpt/pull/4169 . ___ dev-platform mailing list dev-platform@lists.mozilla.org https://lists.mozilla.org/listinfo/dev-platform
