Re: [csswg-drafts] [css-mediaqueries-5] Note/Issue on not shipping early proposals (#4834)

The CSS Working Group just discussed `[css-mediaqueries-5] Note/Issue on not shipping early proposals`.

<details><summary>The full IRC log of that discussion</summary>
&lt;dael> Topic: [css-mediaqueries-5] Note/Issue on not shipping early proposals<br>
&lt;dael> github: https://github.com/w3c/csswg-drafts/issues/4834<br>
&lt;dael> florian: As far as I'm aware the video-* MQ are not implemented and they do have an existential issue so maybe warning should stay there. Unless they are shipping? I think the warning is right<br>
&lt;dael> astearns: Yes and no. Have other things in other specs with issues<br>
&lt;dael> florian: This is a it may be completely wrong issue. If it's shipping, fine, but if it's not shipping<br>
&lt;dael> astearns: I'm inclined to not put the warning in so we could get impl experiance. If resolution of issue is this was bad people can take it out. That's the risk of impl something in a spec not in CR<br>
&lt;dael> florian: Useful to highlight we don't know what's right but think this is wrong<br>
&lt;dael> fantasai: I think that's fine. But also if someone is shipping something with the warning epople should talk to the WG before shipping<br>
&lt;dael> astearns: I think it makes sense to have a not ein the spec saying we have an issue and this may change<br>
&lt;dael> florian: Okay. I'll take that into account<br>
&lt;fantasai> s/shipping/shipping, shouldn't just leave the spec and impl disagreeing/<br>
</details>


-- 
GitHub Notification of comment by css-meeting-bot
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/4834#issuecomment-960250739 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 22:41:54 UTC