[Bug 28943] avoid "nuked"

https://www.w3.org/Bugs/Public/show_bug.cgi?id=28943

Shane McCarron <shane@aptest.com> changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
                 CC|                            |shane@aptest.com

--- Comment #1 from Shane McCarron <shane@aptest.com> ---
(In reply to Philippe Le Hegaret from comment #0)
> Art reminded me about this one, so here is a proper bug.
> 
> In 
>  http://www.w3.org/TR/dom/#interface-domerror
> 
> [[
> On 7/10/14 12:25 PM, Glenn Adams wrote:
> > The language "nuked from orbit soon" and "will be nuked" needs to be 
> > rewritten. This level of informality is inappropriate for a W3C REC 
> > track document. Better to say "expect to be deprecated" or similar.
> 
> I agree with this proposal (particularly since "nuke" might not 
> translate accurately).

+1 - this needs to be changed.  THe change is completely editorial as long as
the warning remains intact.  Please change this.


> 
> > It is annoying that a search for "Warning!" in the document fails (at 
> > least on Chrome and Firefox) because it is injected from a content 
> > style property.
> 
> This seems a bit like a personal preference to me. As such, I don't 
> think it should block the LCWD publication although if Glenn created a 
> PR that was agreeable to Robin, then I  don't see any harm in merging it.

Actually, it is an A11Y concern.  Text that comes in via CSS is often missed by
screen readers.  This text should be inline in the document so that it appears
in the DOM.  There are many sources for such information about those
limitations, including guidance from the W3C.  For a decent non-standards
article about just why it is bad, see
http://www.ssbbartgroup.com/blog/csscontentproperty/

-- 
You are receiving this mail because:
You are the QA Contact for the bug.

Received on Monday, 13 July 2015 15:28:33 UTC