- From: Florian Rivoal via GitHub <sysbot+gh@w3.org>
- Date: Thu, 13 Oct 2016 08:02:48 +0000
- To: public-css-archive@w3.org
This has been there since the last level of the spec, which is already a REC. I agree that the likelyhood of running into an interlaced display is going down and that the use-case is fairly narrow to start with, but I don't think there is anything inherently wrong with this MQ. The cost of standardizing seems to have already been paid, and it is already implemented https://www.w3.org/Style/CSS/Test/MediaQueries/20120229/reports/implement-report.html#parsing-scan That said, I just realized there is a difference between the level 3 version of this feature, and the level 4 one: in level 3, this was meant only to apply to the TV media type, but in level 4 there is no such restriction. I guess this leaves us with a two main options: - Tie it back to the tv media type, which is deprecated, so deprecate this as well: everybody must parse it, everybody must return false. - Keep it in as it is specified in level 4: everybody must parse it, and must return true to either `progressive` or `interlace` @tabatkins Do you remember if the difference between the two levels was intentional? What's your take on this, should we revert the change and make it forever useless, or keep it and impose a small but non zero cost on implementors to adjust their behavior to the new spec? -- GitHub Notification of comment by frivoal Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/594#issuecomment-253442827 using your GitHub account
Received on Thursday, 13 October 2016 08:02:56 UTC