W3C home > Mailing lists > Public > www-style@w3.org > August 2007

Re: 3rd call: CSS2: howto disable audio?

From: Doug Schepers <schepers@w3.org>
Date: Wed, 01 Aug 2007 16:05:36 -0400
Message-ID: <46B0E790.3050007@w3.org>
To: www-style CSS <www-style@w3.org>

Hi, David-

David Woolley wrote (on 8/1/2007 3:20 AM):
> 
> Doug Schepers wrote:
>> David Woolley wrote (on 7/27/2007 3:09 AM):
>  Once you start using plugins you have left the scope of W3C regulation
>>> and you have decided to enter an essentially unregulated market.
>>
>> What?  That's not at all true.  There are plugins for SVG, MathML, 
>> XForms, SMIL
> 
> Being unregulated means unregulated.  Banning W3C technology based 
> plugins would be a regulation 

You are not being at all clear in your assertion.  Could you define what 
you mean by "unregulated"?  And who mentioned banning plugins based on 
W3C tech?


> (although I think SVG is a poor example, 
> as my impression is that the original main one, from Adobe, was written 
> with little regard to integrating with the rest of the W3C technologies).

Your impression is wrong, and smacks of FUD.  The original Adobe viewer 
went out of its way to allow scripting between DOMs, and inline SVG (as 
far as the current technology allowed for IE and Netscape/Mozilla, which 
subsequently changed its plugin scheme).  The viewer integrated most of 
DOM2/3, XLink, and CSS.  I believe that internal builds allowed HTML 
inside SVG's foreignObject, though I don't think that was ever a public 
release.  They also experimented with XPath integration.  What more 
integration could you reasonably ask for?


>>> In practical terms, plugins are quite likely to completely bypass the 
>>> browser when generating sound.
>>
>> Only if the plugin vendor decides to make them so.  If they have clear
> 
> Many plugins start as being independent programs.  That's particularly 
> true in the sound area, where the main choice is between Real Audio and 
> Windows Media Player.  As such, they don't make use of more browser 
> infrastructure than is strictly necessary to allow them to be used.

Even assuming that's true (you've made the claim, but provided no 
evidence), what's happened in the past informs but does not dictate what 
may happen in the future.  Has attention been paid to specifying how 
plugins might integrate with W3C tech, regarding audio and other 
multimedia?  Can you cite any instance where a plugin creator explicitly 
ignored something like an audio control?

You've clipped out the most important part of my email, that which calls 
for a serious analysis of potential future functionality.

Regards-
-Doug Schepers
W3C Staff Contact, SVG, CDF, and WebAPI
Received on Wednesday, 1 August 2007 20:05:50 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Monday, 27 April 2009 13:54:51 GMT