- From: CSS Meeting Bot via GitHub <sysbot+gh@w3.org>
- Date: Wed, 03 Nov 2021 21:21:48 +0000
- To: public-css-archive@w3.org
The CSS Working Group just discussed `Directionality vs Shadow DOM`, and agreed to the following: * `RESOLVED: accept fantasai's proposal, get it written into spec, have tests updated to match` <details><summary>The full IRC log of that discussion</summary> <fantasai> Topic: Directionality vs Shadow DOM<br> <astearns> github: https://github.com/w3c/csswg-drafts/issues/6609<br> <dholbert> emeyer: what the WG needs to do is look at the concrete proposal that fantasai put in the whatwg thread<br> <dholbert> emeyer: and resolve whether that's how directionality and shadow dom interact with each other<br> <dholbert> emeyer: it's fantastically clear, fantasai ++<br> <astearns> proposal: https://github.com/whatwg/html/issues/3699#issuecomment-951423468<br> <dholbert> emeyer: whatwg wants to know how csswg thinks they should interact<br> <TabAtkins> q+<br> <dholbert> emeyer: fantasai has a proposal, we need to decide if that's what we want to sign on to<br> <florian> seems right to me, and I fully trust fantasai to get this right<br> <dholbert> TabAtkins: I have given this a read over, it's a slightly more detailed version of what I wanted to propose. Agree 100% with fantasai's proposal<br> <dholbert> astearns: how does this proposal match existing tests<br> <dholbert> emeyer: it may not; but existing tests were created based on the conversation in this thread. need to update tests to match our resolution<br> <dholbert> emeyer: I'll have some tests I need to change, not a problem<br> <dholbert> astearns: only problem could be if updated tests show browsers are failing in ways that keep them from being able to implement the proposal<br> <dholbert> fantasai: they are currently failing to match the proposal; that's been known. Current behavior in browsers is not what we want<br> <dholbert> astearns: we have looks like 3 reviews of the proposal which are thumbs up<br> <dholbert> astearns: proposed resolution is to accept fantasai's proposal, get it written into spec, have tests updated to match<br> <dholbert> astearns: objections?<br> <dholbert> RESOLVED: accept fantasai's proposal, get it written into spec, have tests updated to match<br> <dholbert> astearns: who is going to do spec edits?<br> <dholbert> fantasai: it's a shadow dom spec issue, outside the scope of the csswg<br> <dholbert> fantasai: nothing we need to update in our own specs<br> </details> -- GitHub Notification of comment by css-meeting-bot Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/6609#issuecomment-960097880 using your GitHub account -- Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config
Received on Wednesday, 3 November 2021 21:21:50 UTC