Skip to content
This repository was archived by the owner on Oct 8, 2021. It is now read-only.

decide where to add other vendor extension properties for transitions, corners, etc #13

Closed
scottjehl opened this issue Sep 13, 2010 · 12 comments
Assignees
Milestone

Comments

@scottjehl
Copy link

decide where it makes sense to add -moz, -o, and w3c to css and js events.

@scottjehl
Copy link
Author

Also for gradients. For alpha, which vendor extensions should we include?? Just -webkit?

@scottjehl
Copy link
Author

So, for supported extensions...
For box shadow, we only need:
-webkit
-moz
w3c (opera, ie9)

Same for border radius:
-webkit
-moz
w3c (Opera 10.5, IE 9, Saf5, Chrome)

For background gradients:
-webkit
-moz

  • should we add filter (IE6,7) and/or -ms-filter: (IE8) ? Also, I'm not sure on IE9's support. Anyone?

As for transforms and transitions, we have the following vendors with support for transform:
-webkit-transform: /* Saf3.1+, Chrome
-moz-transform: /* FF3.5+
-o-transform: /* Opera 10.5
w3c (not supported yet?)

same for the transition property.

helpful resources: http://www.zachstronaut.com/posts/2009/02/17/animate-css-transforms-firefox-webkit.html

As for IE, we could get gradients for the latest version by using the -ms

What about -ms?

@localhero
Copy link

Hi,
Maybe I'm missing something, but the goal is mobile isn't it ?
Then I doubt there is any mobile in your target that would run a web app in IE6/IE7.
I won't go in the Filter way for gradient.
IMHO you should stay in the pure HTML5/CSS3 direction.

Let's hope these "-webkit", "-o" and "-moz" will disappear soon :-)
And that Opera will support CSS3 gradient soon too.

Another great link for CSS3 effects : http://www.impressivewebs.com/css3-click-chart/

@scottjehl
Copy link
Author

Mobile IE is still being considered for A support, and if we can support it, it's basically IE7. There are other prefixes to consider as well, depending on which non-webkit engines can be supported. That said, we'll probably drop the filters for performance anyway, but we're still working all this out.

@localhero
Copy link

Okay, wow no IE6 :-)
Where is Mobile IE as A in the Mobile Graded Browser Support on the website ?

@scottjehl
Copy link
Author

Currently, it's grouped with C Grade, but these things are evolving as we go.

@localhero
Copy link

I like when it's evolving so fast :-) Well done.

@toddparker
Copy link
Contributor

Closing, this is 6 months old and I think we've settled on vendor prefixes :)

@scottjehl scottjehl reopened this Apr 21, 2011
@scottjehl
Copy link
Author

reopening for consideration.

@ghost ghost assigned gseguin Jun 21, 2011
@miketaylr
Copy link

Happy to help out with Opera Mobile and Mini on this issue.

scottjehl pushed a commit that referenced this issue Jul 11, 2011
…er support for standard prefixed gradients, and b) remove -ms filter gradients due to a rendering issue in IE9 that conflicts with border radius. Gradient support is set for IE10, however. More info on this bug and decision can be found at issue #2046. Fixes #2046. Fixes #1933. Addresses a portion of #13 as well.
@LinusU
Copy link

LinusU commented Aug 6, 2011

@scottjehl: I saw that you manually updated the css to include support for all browsers. I recently wrote an ANT-task for doing this exact thing automatically https://github.com/LinusU/Fjant. Since you guys use Make instead of ANT it would require some small changes on my end so that it can run as a standalone app but I've been planning on doing that anyhow.

@toddparker
Copy link
Contributor

Already landed the gradient fix and there's another ticket for FF/Opera transitions so closing.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

No branches or pull requests

6 participants