Re: [csswg-drafts] [css-nesting] Problem with mixing properties and selectors (#8249)

@tabatkins The slimmed down option 3 – with required leading `&` - was proposed during the call to break the standstill we were in: 

1. Option 3 – which was already chosen as the winner before and was as good as ready to ship – only needed the final stamp of approval.
2. Giving option 3 the stamp of approval would have resulted in a formal objection because we lacked data about a relaxed/infinite lookahead being viable or not.

With that slimmed down option 3, vendors could ship at least “something” _(which could still be upgraded to the full Option 3)_ while also preventing the formal objection from happening. It also worked around other discussions that were still ongoing at the time (e.g. _“How would it desugar?”_).

Would this have been ideal to authors? Probably not, but at least it would have allowed them to cover only the basic cases.

But the entire suggestion is no longer valid I think, as @emilio offered a better escape hatch to the standstill by looking into the viability of infinite lookahead. As detailed in https://github.com/w3c/csswg-drafts/issues/8249#issuecomment-1396198517 by @plinss that research won’t prevent Option 3 from shipping. Correct me if I’m misunderstanding Peter, but it would boil down to:

- At “worst”, we end up with Option 3, because the research backs the assumptions made.
- At best, we end up with the Sass-like syntax, because it turned out to be easier to implement.
- Scenario in between is that we end up with a shipping Option 3 that gets upgraded to the Sass-like syntax by implementers when there’s engineering capacity for it.

So yeah, Option 3 is the version that’s still on the table and the one that will go out the door. Maybe it’ll even get an extra upgrade before it does.

-- 
GitHub Notification of comment by bramus
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/8249#issuecomment-1398047751 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Friday, 20 January 2023 08:13:44 UTC