-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
🖍 Add min--moz-device-pixel-ratio
and max--moz-device-pixel-ratio
media features to CSS validator spec
#34553
🖍 Add min--moz-device-pixel-ratio
and max--moz-device-pixel-ratio
media features to CSS validator spec
#34553
Conversation
Hey @ampproject/wg-caching! These files were changed:
|
@Gregable Will this change be live for Search Console in the next week or so? |
I would guess yes. @honeybadgerdontcare is the current release owner. |
@westonruter this appears to be in prod for both internal and external validator interfaces. |
I don't see it live when testing this URL: https://wrestling.sportsjagran.com/wwe/3-wwe-superstars-who-may-join-aew/?amp I'm checking via https://search.google.com/test/amp and also https://playground.amp.dev/ In both cases I still see:
|
I was testing with the code snippet in comment #1 and adding
validator.amp.dev shows both that code snippet and that URL pass. Also our internal tool also shows it passing (go/ampvalidator). Update: I see the issue was to remove the warning. The internal tool does still return the warning. |
Another release is happening tomorrow, I'll verify then that the warning has been removed (apologies, thought it was an error being removed). |
@sebastianbenz this change is now live. However it still reports this as a warning. I've confirmed this is true for both internal and external. You can confirm by adding a test file for it and updating the corresponding .out file. I'm unsure of why it's not accepting it and I haven't looked at the css validation code in a long time. |
In the past few days the WordPress AMP plugin has been getting topics about Search Console reporting a warning for a CSS syntax error:
For example:
The offending CSS code looks like this:
Both the JS and C++ validators are reporting:
The fix appears to simply be to add both
min--moz-device-pixel-ratio
andmax--moz-device-pixel-ratio
to the list of non-standard media types and features commonly seen. These two features were used in Firefox 16 and older according to MDN.