- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 19 Jun 2019 16:49:26 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Should option/optgroup be able to set counters?`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: Should option/optgroup be able to set counters?<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/4004<br> <dael> TabAtkins: Technically per CSS they are decendent of replaced so don't generate boxes. if continuing the current resolution that counters work on box tree there's no box to let them set or change counter. Howveer FF and previous Edge allow it. Chromium does not<br> <rachelandrew> I'll take a better look at issue 3846 and see if I have any thoughts from the authoring pov.<br> <dael> TabAtkins: There are use cases for this and a chromium issue to fix and allow setting of counters.<br> <dael> TabAtkins: Chrome devs discussing if they should, bbut no conclusion<br> <dael> TabAtkins: This may effect related issues like if SVG elements can set counters.<br> <dael> TabAtkins: We need to figure out exact terminology. fantasai prop is go one level up to also things that are like boxes, but not css boxes for layout terms and allow those to host counters.<br> <dael> TabAtkins: I'm fine with that. prop is allow optin/optgroup and other things that are like boxes outside the css model to effect counters<br> <dael> astearns: sgtm<br> <dael> AmeliaBR: Makes sense. I'd like a more explicit definition to what is and isn't like a box<br> <dael> TabAtkins: I prefer to define a new term other specs could hook and we define what that is for HTML and SVG. Other mockups could say they are that thing even though they don't generate css boxes<br> <dael> astearns: Other comments?<br> <TabAtkins> s/mockups/markup languages/<br> <dael> smfr: Sounds a little confusing for interactions with display:none. If you have optgroup that contributes to counters and you display:none it does it still contribute?<br> <dael> TabAtkins: I don't think display:none does anything to optin<br> <dael> smfr: If you have one of these how do you stop contributing to counters<br> <dael> TabAtkins: You don't set the counter. the display:none wasn't an intentional choice, it was legacy<br> <dael> smfr: Sounds like it will complicate code to determine what contributes to counters. May be odd interaction with other properties is what I'm saying<br> <dael> fantasai: I kinda disagree, I would expect diplay:none to have effect on counters. You're processing css properties and counters is one of them. I don't have strong opinion on this<br> <dael> TabAtkins: If someone with FF or older Edge can check that link I want to see if display has effect in other<br> <dael> smfr: [missed]<br> <futhark> Display:none affected in firefox<br> <smfr> webkit shows the ‘bar’ in the testcase<br> <futhark> that is, removed from select rendering<br> <dael> Rossen_: We do not support counters inside of display:none. Only time we did something more interesting is if gCS was called inside and we'd have something to calculate in the sub tree. I think we backed it out because it was fragile<br> <dael> fantasai: I htink prop is that anything that is a replaced element has nothing to do with counters or we have something represented in render tree and not display:none and they can have counters<br> <dael> astearns: Either way impl would need to change b/c we're not interop<br> <dael> TabAtkins: Yeah<br> <dael> TabAtkins: And we're buckwild with what styles can effect inside a select<br> <dael> fantasai: If we have an idea we want to do this how aout TabAtkins and I come up with specific wording that deals with the issues brought up here. We can bring it back and htink about how it effects different impl<br> <dael> astearns: Objections to that path?<br> <dael> ACTION TabAtkins and fantasai develop spec text for https://github.com/w3c/csswg-drafts/issues/4004<br> <trackbot> Created ACTION-881 - And fantasai develop spec text for https://github.com/w3c/csswg-drafts/issues/4004 [on Tab Atkins Jr. - due 2019-06-26].<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4004#issuecomment-503641351 using your GitHub account
Received on Wednesday, 19 June 2019 16:49:28 UTC