Skip to content
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

Open
dave1010 opened this issue May 11, 2011 · 5 comments
Open

Support new (as well as old) WebKit gradient format #8

dave1010 opened this issue May 11, 2011 · 5 comments

Comments

@dave1010
Copy link

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.

@mrflix
Copy link
Owner

mrflix commented May 11, 2011

hey! thanks for the feedback :-)
i know about the adoption - it's great isn't it? i was about to drop the old format, but sadly safari doesn't support it yet (chrome does). and because the new webkit format is basically the same as the mozilla format i didn't add it. you only have to copy that line and change the prefix. also - to support every new browser you have to copy that line 4 times for all prefixes: -webkit-, -o-, -ms- and no prefix for future support

@necolas
Copy link

necolas commented May 11, 2011

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.

@mrflix
Copy link
Owner

mrflix commented May 11, 2011

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.

@necolas
Copy link

necolas commented May 11, 2011

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 :)

@oli
Copy link

oli commented May 12, 2011

“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…

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

No branches or pull requests

4 participants