Open
Bug 770560
Opened 12 years ago
Updated 2 years ago
Remove support for prefixed transforms
Categories
(Core :: CSS Parsing and Computation, task)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: Ms2ger, Unassigned)
References
(Depends on 1 open bug, Blocks 1 open bug)
Details
(Keywords: dev-doc-needed, site-compat)
We introduced unprefixed versions of transforms in bug 745523; at some point in the future we'll need to remove support for the prefixed variants.
why? wouldn't it be easy to support the alias indefinitely? ..damn interpreted language ways....
Reporter | ||
Comment 2•12 years ago
|
||
It wouldn't be too hard. However, it would encourage people to use the prefixed version, which means that their sites would only work in Gecko-based browsers. Mozilla's goal is to advance the open web, not to encourage a Gecko-specific web, so we want authors to use standard features, rather than Gecko-proprietary ones.
I didn't think about how it promotes using the un-prefixed version until now. Interesting.
(In reply to scientes from comment #1) > why? wouldn't it be easy to support the alias indefinitely? You must have missed bug 765645 (btw, silence is the only response to that so please don't add comments) Going by that it would probably be wise to remove the javascript alias MozTransform at the same time as the CSS prefix instead of waiting a further 4 years afterwards.
Updated•10 years ago
|
Keywords: dev-doc-needed
We could implement a pref first, like in bug 804944.
Comment 7•9 years ago
|
||
Posted the site compatibility doc: https://www.fxsitecompat.com/en-US/docs/2015/prefixed-css-animations-transforms-transitions-support-will-be-removed/
Keywords: site-compat
Updated•5 years ago
|
Type: defect → task
Updated•2 years ago
|
Severity: normal → --
Updated•2 years ago
|
You need to log in
before you can comment on or make changes to this bug.
Description
•