W3C home > Mailing lists > Public > www-svg@w3.org > January 2008

Filter Meeting (was: Property to disable SVG filters)

From: Doug Schepers <schepers@w3.org>
Date: Wed, 23 Jan 2008 16:27:58 -0500
Message-ID: <4797B15E.2060307@w3.org>
To: Oliver Hunt <oliver@apple.com>, Timothy Rowley <tor@us.ibm.com>, Erik Dahlström <ed@opera.com>, "robert@ocallahan.org" <rocallahan@gmail.com>, MenTaLguY <mental@rydia.net>, www-svg <www-svg@w3.org>

Hi, Tor, Roc, Oliver, Erik, Mental, and SVG WG-

I'd like to propose that we have a short meeting dedicated to this. 
Since this is a time-critical decision for Mozilla, I'd like to see if 
we can come to a mutual solution for the best way to handle this as 
promptly as possible.

We can dedicate the first part of our normal SVG teleconference tomorrow 
to this topic.  We have a phone bridge and an IRC channel where we 
scribe and post links.  If you can make it, please RSVP and I'll send 
you the details.  Here are the normal meeting times (sorry, Mental, I 
don't know your timezone):

Thursday, January 24, 2008 at 19:30:00 UTC

Oslo, Sweden:    Thu 8:30 PM	
Boston, USA:     Thu 2:30 PM	
Austin, TX:      Thu 1:30 PM
San Francisco:   Thu 11:30 AM	
Wellington, NZ:  Fri 8:30 AM
Sydney, AU:      Fri 6:30 AM

-Doug Schepers
W3C Team Contact, SVG, CDF, and WebAPI

Oliver Hunt wrote (on 1/23/08 2:24 PM):
> This worries me, we already have filterRes which can be used to tune 
> down the quality in exchange for performance.  I'm not sure what the 
> benefit of having a vendor specific css property to (effectively) just 
> disable filters despite them being otherwise supported by the engine.
> --Oliver
> On 23/01/2008, at 11:03 AM, Dr. Olaf Hoffmann wrote:
>> As far as I understand this, such a property
>> '-moz-filter-rendering' can only be used as a
>> property for example in an external style sheet,
>> the style element or the style attribute, not as
>> a presentation attribute?
>> Another approach would be to use an own
>> namespace an the extension mechanism of
>> SVG to avoid conflicts and problems with
>> undefined attributes. Such an approach
>> pronounces, that there is currently no such
>> attribute in any SVG version, whatever the
>> future may bring.
>> There are a few similar things from adobe
>> arround using such an extension.
>> If it was no problem that adobe used its
>> own namespace and extensions, then it
>> should be no problem for mozilla too ;o)
Received on Wednesday, 23 January 2008 21:28:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 8 March 2017 09:47:12 UTC