[Bug 16374] Allow transform function list with out explicit separation

https://www.w3.org/Bugs/Public/show_bug.cgi?id=16374

--- Comment #7 from Dirk Schulze <dschulze@adobe.com> 2012-03-14 17:52:43 UTC ---
(In reply to comment #4)
> Is there precendent in any other css property that takes a bare list of
> functions?
Just checked -webkit-filter: drop-shadow(10px 10px 10px blue)sepia(); and it
works as well.

(In reply to comment #6)
> It's cool that everyone supports this, but I fear that adding so much
> flexibility now removes any flexibility for us in the future. Imagine that we
> need to add some characters after the parentheses for some reason (4d
> transforms!!) or remove parentheses - we won't be able to do it if we
> explicitly allow this.
> 
> On the other hand, codifying existing behaviour is generally a good thing.

Wow! 4D? Don't we support it already with transitions and animations? :D

But I understand the concerns. Nevertheless, we would have to deal with it if
we need the flexibility as well. Even if unspecified, we could potentially
break existing content if we need the separation later.

-- 
Configure bugmail: https://www.w3.org/Bugs/Public/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the QA contact for the bug.

Received on Wednesday, 14 March 2012 17:52:50 UTC