Ticket #4214 (closed feature: wontfix)
Normalize support for CSS Transforms via css() method
|Reported by:||zachstronaut||Owned by:|
jQuery normalizes CSS opacity across browsers, I thought it could also normalize support for CSS Transforms so that the end user didn't have to make css() calls for both WebkitTransform and MozTransform properties.
Specificically, rather than calling for example:
$('#foo').css('MozTransform', 'rotate(45deg)'); $('#foo').css('WebkitTransform', 'rotate(45deg)');
The user could simply call:
Implementing these change was relatively easy using jQuery.props and a function to discover the correct property. It is also forward compatible for when 'transform' is no longer a CSS3 draft property.
jQuery.attr() -- which is called from jQuery.prototype.css() -- already uses jQuery.props to map some properties to other values.
jQuery.curCSS() on the other hand manually does some mapping with 'float' but doesn't use jQuery.props. If we do *not* change jQuery.curCSS() to also use jQuery.props the same way jQuery.attr() does, then the side effect is that CSS Transforms can be *set* cross-browsers with jQuery.prototype.css() but you would not be able to *get* them.
I've attached a patch against jquery.js 1.3.2
- Priority changed from minor to low
- Status changed from new to open
- Component changed from core to css
- Milestone changed from 1.4 to 1.5