css vendor prefix error #2015
Comments
|
Yes, trying this on Safari 8 via Browserstack I agree it's failing. The problem seems to be that if you explicitly set the vendor-prefixed property on a style then Safari starts responding to that property on any I don't know that this is something we can fix. Is there a reason you just don't let us do the prefixes for you? |
|
This bug is caused by: Line 265 in 740e190 If we find neither the original style property nor a prefixed one, we return the original one from Later when we try to set We should fix it. |
This prevents jQuery from caching a prefixed property name if provided directly by the user, e.g. the following code: elem.css( "mozTransition", "all 1s" ); should not prevent one from from later setting the transition directly: elem.css( "transition", "all 1s" ); on a browser not understanding the unprefixed version which is the case for Safari 8 & transition. Fixes jquerygh-2015
This prevents jQuery from caching a prefixed property name if provided directly by the user, e.g. the following code: elem.css( "msTransform", "translate(5px, 2px)" ); should not prevent one from from later setting the transition directly: elem.css( "transform", "translate(5px, 2px)" ); on a browser not understanding the unprefixed version which is the case for Safari 8 & transform. Fixes jquerygh-2015
This prevents jQuery from caching a prefixed property name if provided directly by the user, e.g. the following code: elem.css( "msTransform", "translate(5px, 2px)" ); should not prevent one from from later setting the transition directly: elem.css( "transform", "translate(5px, 2px)" ); on a browser not understanding the unprefixed version which is the case for Safari 8 & transform. Fixes jquerygh-2015
|
PR: #2298 |
This prevents jQuery from caching a prefixed property name if provided directly by the user, e.g. the following code: elem.css( "msTransform", "translate(5px, 2px)" ); should not prevent one from from later setting the transition directly: elem.css( "transform", "translate(5px, 2px)" ); on a browser not understanding the unprefixed version which is the case for Safari 8 & transform. Fixes jquerygh-2015
This prevents jQuery from caching a prefixed property name if provided directly by the user, e.g. the following code: elem.css( "msTransform", "translate(5px, 2px)" ); should not prevent one from from later setting the transition directly: elem.css( "transform", "translate(5px, 2px)" ); on a browser not understanding the unprefixed version which is the case for Safari 8 & transform. Fixes jquerygh-2015
This prevents jQuery from caching a prefixed property name if provided directly by the user, e.g. the following code: elem.css( "msTransform", "translate(5px, 2px)" ); should not prevent one from from later setting the transition directly: elem.css( "transform", "translate(5px, 2px)" ); on a browser not understanding the unprefixed version which is the case for Safari 8 & transform. Fixes jquerygh-2015
This prevents jQuery from caching a prefixed property name if provided directly by the user, e.g. the following code: elem.css( "msTransform", "translate(5px, 2px)" ); should not prevent one from from later setting the transition directly: elem.css( "transform", "translate(5px, 2px)" ); on a browser not understanding the unprefixed version which is the case for Safari 8 & transform. (cherry-picked from d471842) Fixes gh-2015 Closes gh-2298
This prevents jQuery from caching a prefixed property name if provided directly by the user, e.g. the following code: elem.css( "msTransform", "translate(5px, 2px)" ); should not prevent one from from later setting the transition directly: elem.css( "transform", "translate(5px, 2px)" ); on a browser not understanding the unprefixed version which is the case for Safari 8 & transform. Fixes gh-2015 Closes gh-2298
$().css automaticly add vendor prefixes, but if firstly call "$().css" function with prefixes styles, auto-adding break. Run example in Safari
http://jsfiddle.net/8cf0hyhj/
The text was updated successfully, but these errors were encountered: