-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Support new (as well as old) WebKit gradient format #8
Comments
hey! thanks for the feedback :-) |
i think you should include the updated -webkit and -o versions in the code presented to people in the app. lots of people will just copy and paste that code. but i dont think it is worth adding -ms or the unprefixed versions yet because the angle definition of CSS gradients might be changing, last I heard. so no guarantee that the -ms or unprefixed code would work as intended by the time browsers (like IE10 or future Gecko/WebKit) are released that use those declarations. |
interesting news on the (predicted) future of gradient declarations - thanks for sharing it! I'm not sure about adding the prefixes... people should know what they're doing. |
I think a tool like this is particular useful for developers with less experience. Not everyone is going to be aware of Opera support, updated WebKit syntax, or negative values for spread distance. They'd be worthy additions :) |
“people should know what their doing” — ummm, you’re making a GUI app to make these things easy to do, and expecting it not to be used by people who don’t know what they’re doing? <_< Adding appropriate prefixes will help people to learn, and actually make the CSS work in all supporting browsers. seems like a win-win to me… |
WebKit has now adopted Mozilla's gradient format: http://www.webkit.org/blog/1424/css3-gradients/
I think Chrome uses the new ones but Safari 5 uses the old ones.
The text was updated successfully, but these errors were encountered: