[csswg-drafts] [css-lists] Should option/optgroup be able to set counters? (#4004)

• From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
• Date: Tue, 04 Jun 2019 20:54:09 +0000
• To: public-css-archive@w3.org
• Message-ID: <issues.opened-452203293-1559681647-sysbot+gh@w3.org>

tabatkins has just created a new issue for https://github.com/w3c/csswg-drafts:

== [css-lists] Should option/optgroup be able to set counters? ==
Should one be able to use 'counter-increment'/etc on `<option>`/`<optgroup>` (and other replaced-element form-control descendants)?

I think a strict reading of the spec says no - since `<select>` is replaced, its children don't generate CSS boxes, and things that don't generate CSS boxes can't interact with counters.

However, that text was written with `display:none` in mind, not necessarily replaced element descendants.

Here's an example: <https://codepen.io/kizu/pen/PEJgpr>. Apparently this works in Firefox, and pre-chromium Edge, but it does not work in WebKit or Chrome.

Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4004 using your GitHub account

Received on Tuesday, 4 June 2019 20:54:11 UTC