Re: [Bulk] Re: 3rd call: CSS2: howto disable audio?

There is a proposal in HTML5 to create an <audio> element.  I would  
assume that:

audio {
 display:none;
}

would disable the playing of that sound, but I think that's up for  
the HTML Working Group to decide what CSS properties apply to it.  If  
they ask for the working group's feedback, we'll certainly give it,  
and there is some overlap on the two working groups (at least two  
members of the CSS WG that I know of are on the HTML WG as well).

You could also reach out to the plugin vendor and ask them to check  
the DOM and check the display state of their element (if they can do  
that, I don't see why they couldn't unless there's a sandbox issue,  
but I'm pretty sure Flash has access to the DOM and could check its  
display state).  You could also build a custom widget that respects  
display state.

There are technological options beyond propping up straw men about  
representing users.

Kevin Lawver - kevin.lawver@corp.aol.com - "Web Standards Guy"
AIM Social Media | W3C: AOL AC Rep, member of CSS and Web API Working  
Groups

blog: http://lawver.net | presentations: http:// 
presentations.lawver.net | go write something: http://ficlets.com


On Jul 27, 2007, at 5:01 AM, ~:'' ありがとうございました。  
wrote:

>
> David,
>
> is there an inherent or natural reason that current browsers don't
> play any audio formats natively?
>
> bearing in mind that the original browsers did not display images,
> and the next generation didn't use "plugins" to display images.
>
> cheers
>
> Jonathan Chetwynd
>
>
>
> On 27 Jul 2007, at 08:09, David Woolley wrote:
>
>
> ~:'' ありがとうございました。 wrote:
> > Also, as you are aware, plugins are treated as one group so the
> > user has
>
> Once you start using plugins you have left the scope of W3C
> regulation and you have decided to enter an essentially unregulated
> market.
>
> In practical terms, plugins are quite likely to completely bypass the
> browser when generating sound.
>
> --
> David Woolley
> Emails are not formal business letters, whatever businesses may want.
> RFC1855 says there should be an address here, but, in a world of spam,
> that is no longer good advice, as archive address hiding may not work.
>
>
>
>

Received on Friday, 27 July 2007 12:12:52 UTC