W3C home > Mailing lists > Public > public-css-bugzilla@w3.org > July 2012

[Bug 18436] Re-add support for skew()

From: <bugzilla@jessica.w3.org>
Date: Tue, 31 Jul 2012 23:19:19 +0000
Message-Id: <E1SwLih-00022W-Ev@jessica.w3.org>
To: public-css-bugzilla@w3.org
https://www.w3.org/Bugs/Public/show_bug.cgi?id=18436

--- Comment #6 from Sylvain Galineau <sylvaing@microsoft.com> 2012-07-31 23:19:19 UTC ---
(In reply to comment #5)
> (In reply to comment #4)
> > (In reply to comment #3)
> > > (In reply to comment #1)
> > > > Did IE 10 keep skew(x, y) while also unprefixing?
> > > 
> > > Tested it on last IE 10 public preview and it is supported there.
> > 
> > Indeed; it was supported in IE9 and remains supported in unprefixed IE10. We
> > have no plans to remove support at this time.
> 
> If we add skew() again, we won't be able to remove it again. I don't have
> strong feeling on adding it again, but still don't think that this function
> makes sense. I don't think that edge still supports skew() in the latest
> version, but will check tomorrow.

If existing content depends on it to a point where implementations suffer from
not supporting it then we're not able to remove it *today*. If by 'it doesn't
make sense' you mean 'it's redundant' then sure; I don't understand what real
harm there is in that though. It's unfortunate but there are worse problems.

-- 
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 Tuesday, 31 July 2012 23:19:20 GMT

This archive was generated by hypermail 2.2.0+W3C-0.50 : Tuesday, 31 July 2012 23:19:21 GMT