- From: Geoffrey Sneddon via GitHub <sysbot+gh@w3.org>
- Date: Tue, 17 Apr 2018 07:47:35 +0000
- To: public-css-archive@w3.org
gsnedders has just created a new issue for https://github.com/w3c/csswg-drafts: == App. A: Aural style sheets is informative yet sounds normative == This goes all the way back to 2002 when it was made informative in ac046f711d. > This chapter is informative. - [ ] It's an appendix, not a chapter. > The properties in this appendix apply to a media type 'aural', that was introduced in CSS2. The type 'aural' is now deprecated. - [ ] Are we informatively deprecating aural? > User agents should allow the values corresponding to '0' and '100' to be set by the listener. - [ ] Are we using RFC 2119 "should" informatively? What does it mean that a UA should implement this as an informative statement? > This property specifies whether text will be rendered aurally and if so, in what manner. - [ ] Does it? I thought the property didn't really exist; the appendix is, after all, informative. > For information, here is the list of properties implemented by Emacspeak, a speech subsystem for the Emacs editor. - [ ] Why are we informatively giving an implementation report for an informative appendix in the spec? More generally, why is this appendix even here? We obviously don't expect/want anyone to implement it (otherwise it would've been made normative again), so what do we gain by having it here? Should we define `display: run-in` (which was also in CSS2) informatively as well and rename it "Appendix A. Abandoned Features"? Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/2586 using your GitHub account
Received on Tuesday, 17 April 2018 07:47:39 UTC