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 gecko's css gradient proposal #1

Closed
Modernizr opened this issue Sep 25, 2009 · 1 comment
Closed

Support gecko's css gradient proposal #1

Modernizr opened this issue Sep 25, 2009 · 1 comment

Comments

@Modernizr
Copy link
Collaborator

Reported here: http://twitter.com/atwork8_/statuses/3895252369

Per Faruk:
"Right now, the two CSS gradient specs are both mere proposals and both are under heavy scrutiny for changing and synchronizing. I want us to adjust the gradient check in the next release to support both WebKit and Mozilla's proposals, e.g. check for both types. Since Firefox only supports it as of 3.6a and later, but WebKit has had it since Safari 3.1, we'll do the Firefox check second."

@paulirish
Copy link
Member

support mozilla css gradients proposal. closed by 118bf76

paulirish pushed a commit that referenced this issue Oct 15, 2012
test new detects locally
stucox pushed a commit that referenced this issue Mar 12, 2013
stucox pushed a commit that referenced this issue Jul 1, 2013
anenviousguest added a commit to anenviousguest/Modernizr that referenced this issue Sep 24, 2014
Fix: handling edge cases in tests code for partial support. JSONP from 'caniuse' could contain values like 'a Modernizr#2' or 'y Modernizr#1', whereas code was expecting just 'a' or 'y'.
This issue was closed.
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

1 participant