3rd call: CSS2: howto disable audio?
|
View:
New views
7 Messages
—
Rating Filter:
Alert me
|
 |
|
|
|
Re: 3rd call: CSS2: howto disable audio?
by fantasai
::
Rate this Message:
~:'' ありがとうございました。 wrote: > > CSS2: howto disable audio? > > Bert, > > I've already raised this issue twice***, but not received a response. > > Please could you consider how to disable audio with CSS2? > and let me know asap? > *** > http://lists.w3.org/Archives/Public/www-style/2007Apr/0008.html * > http://lists.w3.org/Archives/Public/www-style/2007Jul/0044.html ** > > > **CSS & audio > > How can the user disable audio? If the audio was triggered by aural CSS, then you could turn it off with CSS rules, but the testcase you have attached is not using aural CSS, it's embedding the audio file via HTML. ~fantasai |
|
|
Re: 3rd call: CSS2: howto disable audio?
by "~:'' ありがとうございました"
::
Rate this Message:
fantasai, thank you for your response, however this issue* is not directly related to aural CSS. regards Jonathan Chetwynd *Had aural CSS been chosen, relatively few visitors would have the opportunity to hear sound. On 23 Jul 2007, at 19:15, fantasai wrote: ~:'' ありがとうございました。 wrote: > CSS2: howto disable audio? > Bert, > I've already raised this issue twice***, but not received a response. > Please could you consider how to disable audio with CSS2? > and let me know asap? > *** > http://lists.w3.org/Archives/Public/www-style/2007Apr/0008.html * > http://lists.w3.org/Archives/Public/www-style/2007Jul/0044.html ** > **CSS & audio > How can the user disable audio? If the audio was triggered by aural CSS, then you could turn it off with CSS rules, but the testcase you have attached is not using aural CSS, it's embedding the audio file via HTML. ~fantasai |
|
|
Re: 3rd call: CSS2: howto disable audio?
by fantasai
::
Rate this Message:
~:'' ありがとうございました。 wrote: > > fantasai, > > thank you for your response, however this issue* is not directly related > to aural CSS. My point is, you are complaining to the wrong people. If the sound is coming from the plugin, then you need to complain to the makers of the plugin. A plugin is arbitrary executable code: if it makes too much noise, CSS can't do anything about that. ~fantasai |
|
|
Re: 3rd call: CSS2: howto disable audio?
by "~:'' ありがとうございました"
::
Rate this Message:
Fantasai, that's all too easy an excuse, aka passing the buck. I do take your point, but however dont agree that it's necessarily only a plugin issue. for instance it's likely the plugin - can - raise an interface that provides a means to disable. However the author may chose to make this very small, off screen, or not visible. it's also true that the user agent, application or browser may provide an audio interface. furthermore client-side script can be used to play audio. However as the current functioning W3C specifications are designed in such a way that CSS provides sound on event, which is a reasonable expectation; is it not a sensible expectation that there should equally be a way for CSS to disable or prevent audio? for instance via a user style sheet? regards Jonathan Chetwynd On 24 Jul 2007, at 06:24, fantasai wrote: ~:'' ありがとうございました。 wrote: > fantasai, > thank you for your response, however this issue* is not directly > related to aural CSS. My point is, you are complaining to the wrong people. If the sound is coming from the plugin, then you need to complain to the makers of the plugin. A plugin is arbitrary executable code: if it makes too much noise, CSS can't do anything about that. ~fantasai |
|
|
Re: 3rd call: CSS2: howto disable audio?
by fantasai
::
Rate this Message:
~:'' ありがとうございました。 wrote: > > Fantasai, > > that's all too easy an excuse, aka passing the buck. > I do take your point, but however dont agree that it's necessarily only > a plugin issue. Then show me a testcase where it's not a plugin issue. > for instance it's likely the plugin - can - raise an interface that > provides a means to disable. > However the author may chose to make this very small, off screen, or not > visible. > > it's also true that the user agent, application or browser may provide > an audio interface. > furthermore client-side script can be used to play audio. > > However as the current functioning W3C specifications are designed in > such a way that CSS provides sound on event, which is a reasonable > expectation; is it not a sensible expectation that there should equally > be a way for CSS to disable or prevent audio? See, now you're saying that CSS is controlling the sound of your plugin. This is not the case. The W3C specifications do not say whether the plugin provides sound or does not provide sound. The W3C does not standardize plugins. The CSS specifications talk about whether the 'play-during' property provides sound, and you can override /that/ in a user style sheet, but this is not relevant to the test cases you have posted here. ~fantasai |
|
|
Re: 3rd call: CSS2: howto disable audio?
by "~:'' ありがとうございました"
::
Rate this Message:
fantasai, "this is not relevant to the test cases you have posted here." sums up the issue as well as it could. the issue is that specifications, whilst not created irrespective of each other, aren't necessarily able to foresee usage. the fact is that without some change it's possible and even likely that we could all receive massive amounts of unwanted audio spam on websites. spam audio that it seems could be hard to control. especially given that users may chose to disable client-side script for precisely this type of reason. regards Jonathan Chetwynd On 24 Jul 2007, at 09:44, fantasai wrote: ~:'' ありがとうございました。 wrote: > Fantasai, > that's all too easy an excuse, aka passing the buck. > I do take your point, but however dont agree that it's necessarily > only a plugin issue. Then show me a testcase where it's not a plugin issue. > for instance it's likely the plugin - can - raise an interface that > provides a means to disable. > However the author may chose to make this very small, off screen, > or not visible. > > it's also true that the user agent, application or browser may > provide an audio interface. > furthermore client-side script can be used to play audio. > However as the current functioning W3C specifications are designed > in such a way that CSS provides sound on event, which is a > reasonable expectation; is it not a sensible expectation that there > should equally be a way for CSS to disable or prevent audio? See, now you're saying that CSS is controlling the sound of your plugin. This is not the case. The W3C specifications do not say whether the plugin provides sound or does not provide sound. The W3C does not standardize plugins. The CSS specifications talk about whether the 'play-during' property provides sound, and you can override /that/ in a user style sheet, but this is not relevant to the test cases you have posted here. ~fantasai |
| Free embeddable forum powered by Nabble | Forum Help |
