On 3/27/19 5:19 AM, L. David Baron wrote:
On Wednesday 2019-03-27 01:42 +0100, Mats Palmgren wrote:
FYI, the CSS Lists spec isn't very well maintained, sadly,
so it's not up-to-date with recent resolutions. So, some
of the finer details in there might be wrong, but I think
most of it regarding
On Wednesday 2019-03-27 01:42 +0100, Mats Palmgren wrote:
> FYI, the CSS Lists spec isn't very well maintained, sadly,
> so it's not up-to-date with recent resolutions. So, some
> of the finer details in there might be wrong, but I think
> most of it regarding counters is correct.
If you've been
On 3/27/19 12:30 AM, Domenic Denicola wrote:
(On-list this time)
However, the actual semantics for how list items work are exclusively
defined by CSS ([css-lists], [css-pseudo]). The above mentioned HTML
elements/attributes simply maps to the relevant CSS properties, using
a built-in
(On-list this time)
> However, the actual semantics for how list items work are exclusively defined
> by CSS ([css-lists], [css-pseudo]).
> The above mentioned HTML elements/attributes simply maps to the relevant CSS
> properties, using a built-in 'list-item' counter.
Where does [css-lists]
On 3/25/19 6:21 AM, Domenic Denicola wrote:
> The spec at https://drafts.csswg.org/css-lists/#declaring-a-list-item
> seems to contradict that hard-fought consensus. It seems like a
> regression to implement list item numbering according to that spec,
> instead of according to HTML.
As others
Note that the spec does not yet reflect the decisions made at the last F2F, or
the subsequent decisions from Issues.
___
dev-platform mailing list
dev-platform@lists.mozilla.org
https://lists.mozilla.org/listinfo/dev-platform
On Tuesday 2019-03-26 14:25 -0700, Domenic Denicola wrote:
> It's great to hear that this isn't a regression in the way I expected. I
> think I was thrown off by the phrasing of the OP, which implied to me a
> switch from following the HTML spec to following the CSS lists spec. As I
> noted,
It's great to hear that this isn't a regression in the way I expected. I think
I was thrown off by the phrasing of the OP, which implied to me a switch from
following the HTML spec to following the CSS lists spec. As I noted, the CSS
lists spec contradicts the HTML spec, e.g. disallowing
On Sunday 2019-03-24 22:21 -0700, Domenic Denicola wrote:
> 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
>
On 25/03/2019 06:21, Domenic Denicola wrote:
> 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
>
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,
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
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
13 matches
Mail list logo
