

Re: CSS3 Speech module: Comments and Corrections

From: Orion Adrian <oadrian@hotmail.com>
Date: Sat, 08 May 2004 13:58:16 -0400
To: www-style@w3.org
Message-ID: <BAY1-F19Q4ZLsluP1q000008f79@hotmail.com>

>>>>    element{
>>>>     content:none;
>>>>     cue-before:url(johnwayne.aiff);
>>>>    }
>>>    element { content: url(johnwayne.aiff); }
>>Isn't there a subtle difference between 'content' and 'cue-before'?
>Both of these would be dangerous if a user agent, presenting the document 
>both visually and aurally, parsed media="aural" (or @media) rules, but 
>replaced the elemnent's content for media="screen" too, then the text quote 
>would be lost too! I know that is incorrect parsing of the rules, but I 
>have no idea how buggy speech renderers are. I'm not disabled myself and 
>don't have any to test with, besides my computer's built-in text-to-speech 
>engine which can't see CSS.

I don't think it's a wise idea to change specs to meet the bugs of the 
existing applications. We should re-examine the specs for difficulty of 
implementation, but changing it without that re-examination is just writing 
specs to bugs.

Orion Adrian
Received on Saturday, 8 May 2004 13:58:57 GMT
