- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Thu, 02 Mar 2023 00:22:43 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[selectors-4] Add pseudo-class to establish before-change style for css-transitions on new elements.`, and agreed to the following: * `RESOLVED: Accept restrictions in https://github.com/w3c/csswg-drafts/issues/8174#issuecomment-1431243750 with exception if :is and :where` <details><summary>The full IRC log of that discussion</summary> <dael> chrishtr: Allowing transition to present first frame in cases where it was not present. Seemed like positive feedback but discussion didn't conclude about if there should be restrictions to make it performant enough<br> <dael> chrishtr: Rune did a prototype that he added a comment on. Has a list of 8 inclusions/exclusions.<br> <dael> TabAtkins: Subject means the part of the selector getting styled<br> <dael> chrishtr: makes sense. [reads list]. The prototype works as expected for us. Concerns with definition?<br> <TabAtkins> q+<br> <dael> fantasai: No concerns, but want dbaron and emilio to be happy with definitions<br> <dael> flackr: I know last time we discussed I believe they both were on and didn't have immediate concerns. I believe subject restriction was from emilio to make it performant<br> <dael> flackr: Not to say we can't defer, but I believe they have locked<br> <dael> chrishtr: That's my recollection as well. If no other concerns today perhaps we can resolve and then we can reopen if they do have a concern<br> <fantasai> wfm<br> <dael> chrishtr: Would that be okay?<br> <dael> Rossen_: Sounds okay<br> <Rossen_> ack fantasai<br> <Rossen_> ack TabAtkins<br> <dael> TabAtkins: The list of conditions is good. Only concern is restriction on is/where/structural pseudos. not makes sense, but is and where in all cases seems excessive. As noted in thread would restrict some nesting and doesn't give you anything<br> <dael> TabAtkins: So long as allbranches of is/where have the inital pseudo class it should work. You can re-write to move the initial out but in nesting that's not plausible<br> <dael> TabAtkins: If we can relax that bit I'd be happy.<br> <dael> chrishtr: Do you mean every branch as nesting?<br> <dael> TabAtkins: If every comma sep selector has the initial pseudo it's valid just as if you put it outside the is<br> <dael> fantasai: What does that have with nesting?<br> <dael> TabAtkins: Not technically using :is it's desc as behaving similar with regards to parent selector<br> <dael> fantasai: but this can be an exception<br> <dael> TabAtkins: No reason for exception because it's not the nesting but that it's in every branch of the selector<br> <TabAtkins> .foo:is(.a:initial, .b:initial) should be valid, along the .foo:initial:is(.a, .b) which is currently valid<br> <dael> fantasai: Feel like that makes it more confusing. Obvious it's valid when it's outside and valid when inside. Saying has to be in all 3 but not 2 gets complicated<br> <dael> TabAtkins: [missed] in all branches<br> <dael> TabAtkins: The rule is it has to be on the subject in all branches. It's an extension of the existing rule. If it's on all branches it can go into and is/where<br> <dael> fantasai: Defer to impl. I think it's a little confusing<br> <dael> TabAtkins: Unhappy with behavioral differences for is/where when there isn't a reason<br> <dael> chrishtr: Makes sense to me<br> <TabAtkins> but .foo:is(.a:initial, .b) would make the initial not match<br> <dael> Rossen_: Augment prop to exclude is and where from the second list item? Or all 4?<br> <dael> TabAtkins: has and not are not selecting the subject so they are fine to exclude<br> <dael> TabAtkins: is/where are allowed if on the subject in every arguement would need to be explicit<br> <dael> Rossen_: Prop: accept list of restrictions in https://github.com/w3c/csswg-drafts/issues/8174#issuecomment-1431243750 as proposed by Rune excluding :is and :where. Draw attention to emilio and dbaron to review<br> <dael> Rossen_: Draw attention to Rune to make sure it's implementable with the change to is/where<br> <dael> TabAtkins: If there's impl complexity I'm fine<br> <dael> Rossen_: Accept restrictions in https://github.com/w3c/csswg-drafts/issues/8174#issuecomment-1431243750 with exception if :is and :where<br> <dael> Rossen_: Obj?<br> <dael> RESOLVED: Accept restrictions in https://github.com/w3c/csswg-drafts/issues/8174#issuecomment-1431243750 with exception if :is and :where<br> <dael> ACTION: chrishtr get feedback from dbaron emilio and Rune<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8174#issuecomment-1451086591 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Thursday, 2 March 2023 00:22:45 UTC