Remove support for prefixed transforms

NEW
Unassigned

Status

()

Core
CSS Parsing and Computation
5 years ago
a month ago

People

(Reporter: Ms2ger, Unassigned)

Tracking

(Depends on: 1 bug, Blocks: 1 bug, {dev-doc-needed, site-compat})

Trunk
dev-doc-needed, site-compat
Points:
---
Dependency tree / graph

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

5 years ago
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.

Comment 1

5 years ago
why? wouldn't it be easy to support the alias indefinitely? 


..damn interpreted language ways....
(Reporter)

Comment 2

5 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.

Comment 3

5 years ago
I didn't think about how it promotes using the un-prefixed version until now. Interesting.

Comment 4

5 years ago
(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.

Comment 5

5 years ago
aha, avoid the cargo cult cut-and-pastes from breaking

Updated

3 years ago
Depends on: 772417
Keywords: dev-doc-needed

Comment 6

3 years ago
We could implement a pref first, like in bug 804944.
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

a month ago
Blocks: 775235
You need to log in before you can comment on or make changes to this bug.