- From: jinlongz <jinlongz@oupeng.com>
- Date: Fri, 31 Aug 2012 16:16:02 +0800
- To: www-style <www-style@w3.org>
- Cc: "Zi Bin Cheah" <zibin@opera.com>
- Message-ID: <201208311616016033494@oupeng.com>
I just translated css3-conditional[1] and I'd like to share my opinions. ISSUE 3: "Is any further allowance for forward-compatible parsing needed, for Example, to allow additional features (such as, say, selector tests) to be added to the ¡®@supports¡¯ rule? Or are these forward- compatible parsing rules the best solution for such future expansion anyway?" I think it's fine to only make @supports support CSS values. At least making @supports do CSS selectors doesn't seem necessary. Whenever there's a browser that doesn't support a CSS3 selctor, the declarations are already ignored. ISSUE 5 Given that this @-rule is intended primarily for user style sheets, what should this specification say about its use in author style sheets? Should it be forbidden? Should use instead be discouraged? Or should this specification remain neutral on the topic, since there are valid uses in author style sheets? I think this section should apply to author style sheets. As what follows, I think there are use cases here. ISSUE 8: "@document" syntax doesn't offer any ability to do negations, which has been requested in Mozilla bug 349813. I also think @document should support the "not" syntax. Many sites publish common style sheets for the whole site, say, reset.css and such. It would be useful to be able to exclude certain special pages from using these style sheets with something like @document :not url('example.com/particular') [1] http://www.w3.org/html/ig/zh/wiki/Css3-conditional Zhang Jinlong --- Web Specialist Tel : 136-5112-3546 skype : jinlong3546 QQ : 237585693 Weibo : http://weibo.com/newwave
Attachments
- image/png attachment: 2531_c-logo.png
Received on Saturday, 1 September 2012 11:43:15 UTC