W3C home > Mailing lists > Public > www-style@w3.org > July 2011

Re: [css3-speech] cue <uri> load fails

From: Daniel Weck <daniel.weck@gmail.com>
Date: Wed, 6 Jul 2011 17:12:57 +0100
Message-Id: <221345C0-1F4E-4541-A59E-8E7E9FAB0E09@gmail.com>
To: "www-style@w3.org style" <www-style@w3.org>, fantasai <fantasai.lists@inkedblade.net>
I agree. Fixed in the latest editors' draft.
/Daniel

On 30 Jun 2011, at 02:10, fantasai wrote:

> http://dev.w3.org/csswg/css3-speech/#cue-props
>
>  # When a user agent is not able to render the specified auditory  
> icon,
>  # it is recommended to produce an alternative cue. (e.g. popping up a
>  # warning, emitting a warning sound)
>
> ...
>
>  # If the URI resolves to something other than an audio file, such as
>  # an image, the resource is ignored and the property treated as if it
>  # had the value ‘none’.
>
> I don't think these behavior should be different. Consider: suppose  
> the
> cue resolves to an audio resource, but the UA doesn't recognize the
> resource. Is an alternative cue played, or is the cue silent?
>
> If the UA can't play the specified URI for *any* reason, it should  
> do X.
> That simplifies the expected behavior and avoids any ambiguities  
> deriving
> from the exact conditions of why the UA can't play the specified URI.
>
> Also wrt "warning sound", I suggest that X be either
>  - no cue
>  - an alternative cue, such as a bell
> and not
>  - an alternative cue, such as a warning sound
> since I believe there should be no expectation that the following  
> content
> indicates a problem. :)
>
> ~fantasai
>

Daniel Weck
daniel.weck@gmail.com
Received on Wednesday, 6 July 2011 16:13:26 GMT

This archive was generated by hypermail 2.3.1 : Tuesday, 26 March 2013 17:20:42 GMT