- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 02 Sep 2020 23:20:48 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `[selectors] Let :is() have better error-recovery behavior than normal Selectors`. <details><summary>The full IRC log of that discussion</summary> <dael> Topic: [selectors] Let :is() have better error-recovery behavior than normal Selectors<br> <dael> github: https://github.com/w3c/csswg-drafts/issues/3264<br> <dael> ericwilligers: We resolved to have better error recovery but WK shipped without and FF is about to. Is it too late or do we still want error recovery?<br> <dael> TabAtkins: If possible I'd like to have it. If we have to oh well, but it's bad behavior without<br> <dael> ericwilligers: Who wants to do spec update?<br> <dael> ericwilligers: We resolved on issue but spec isn't updated<br> <dael> TabAtkins: I'll do it if we agree today to proceed<br> <dael> Rossen_: We're wanting to hold previous resolution that requires error recovery and make that edit into spec? Or are we trying to relax the error recovery and not proceed with edits?<br> <dael> ericwilligers: [missed]<br> <dael> ericwilligers: I'm propsing the first, that we go ahead and make edit.<br> <dael> Rossen_: You're proposing add it to spec and pester impl to do that<br> <dael> ericwilligers: Yes<br> <astearns> notes that Emilio says he's OK implementing it<br> <dael> Rossen_: Alright. Any thoughts on that? Are we still committed and have TabAtkins add edits?<br> <dael> TabAtkins: We'd need FF or WK dev to be okay doing change<br> <dael> Rossen_: emilio is signaling he's fine with change. Only WK is going to be required to update. Anyone from WK on?<br> <dael> smfr: If emilio is fine changing we're fine changing<br> <dael> Rossen_: We have a resolution to do error recovery. Do we need resolution to have TabAtkins edit it in?<br> <dael> Rossen_: We'll close no change but to put in the required edits<br> <dael> Rossen_: Thank you<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/3264#issuecomment-686088149 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 2 September 2020 23:20:50 UTC