Support for Drupal 7 is ending on 5 January 2025—it’s time to migrate to Drupal 10! Learn about the many benefits of Drupal 10 and find migration tools in our resource center.
Problem/Motivation
Vendor prefixes @-webkit-keyframes
and @-ms-keyframes
are no longer required.
Steps to reproduce
Proposed resolution
Remove them, and enable the at-rule-no-vendor-prefix
rule in Stylelint.
Remaining tasks
User interface changes
API changes
Data model changes
Release notes snippet
Comment | File | Size | Author |
---|---|---|---|
#4 | remove-vendor-specific-prefix-patch-diff.png | 40.39 KB | gaurav-mathur |
#4 | after-patch-remove-vendor-specific-prefix.png | 5.9 KB | gaurav-mathur |
#4 | before-patch-remove-vendor-specific-prefix.png | 14.48 KB | gaurav-mathur |
#2 | 3319173-2.patch | 1.88 KB | longwave |
|
Comments
Comment #2
longwaveComment #3
gaurav-mathur CreditAttribution: gaurav-mathur at Dotsquares Ltd. commentedComment #4
gaurav-mathur CreditAttribution: gaurav-mathur at Dotsquares Ltd. commentedApplied patch #2 on Drupal 10.0.x-dev
The patch worked perfectly issue got fixed
Refer to the screenshot
Comment #5
Spokje- CSS changes make sense.
- Enabling stylelint rule at-rule-no-vendor-prefix makes sense.
- Green TestBot.
RTBC for me.
Comment #6
alexpott@gaurav-mathur Thank you for looking into this issue.
Posting screenshots of your codebase or command-line interface does not advance the issue, since the automated testing infrastructure tells us whether the change set still applies correctly.
So, I've not given issue credit for that screenshot. In the future, you can get credit for issues by reading the issue to understand its purpose, and posting your review or testing of that purpose. Thank you!
Comment #7
alexpottLooking at the browser compatibility chart on https://developer.mozilla.org/en-US/docs/Web/CSS/@keyframes we're all good here.
Committed and pushed 63a8a2656e to 10.1.x and ba61f32af2 to 10.0.x. Thanks!