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
autofill not being prefixed #626
Comments
Do we have any W3C spec about |
Seems like it's something in CSS4 |
Could you help me and make PR to Can I Use with |
This is not in the CSSWG draft. https://drafts.csswg.org/css-ui/ |
@alan-agius4 sorry, there is no |
It looks like
Should this issue be reopened @ai? |
Cool! Seems like we have a support chart on MDN (which we can use at Can I Use). Can somebody send PR? |
The same as for #1374. The data is available in |
Is this sufficient to add support? https://caniuse.com/mdn-css_selectors_autofill |
@roypearce nope, this data is not available in |
Potentially worth hardcoding data in like we did for file-selector-button and updating it as and when stable support is added. In the meantime it could even be worth adding in a blanket prefix rule that automatically generates the WebKit prefixed version. That way you get the prefix, ensuring your code works in all modern browsers. This will be supported in: Chrome 96: https://www.chromestatus.com/feature/5592445322526720 And is already supported in: Firefox 86: https://developer.mozilla.org/en-US/docs/Web/CSS/:autofill Safari TP 129: https://webkit.org/blog/11951/release-notes-for-safari-technology-preview-129/ - presumably will come in Safari 15.1 or 15.2 |
@lukewarlow maybe we can improve Send PR to https://github.com/browserslist/caniuse-lite with a script (somewhere in |
@ai made a start on it browserslist/caniuse-lite#86 |
Fixed by #1430 |
|
autofill are not being autoprefixed.
browsers: "last 2 versions"
The text was updated successfully, but these errors were encountered: