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 ahem.css to many more tests #17292
Conversation
Looks like the only new failures in this PR are the following:
All of these are non-reftests, and they probably need The remainder of the failures in this PR are already covered in #17205. |
53e692f added that to those tests, but it seems like that didn't suffice, bleh. |
OK, I've removed all the tests changed in #17205 from this PR now, and hopefully fixed the rest. |
This was: LANG=C grep -R -l -i 'font.*:.*ahem' css | xargs grep -L ahem\\.css | xargs gsed -i 's/\(^.*\)<style/\1<link rel=\"stylesheet\" type=\"text\/css\" href=\"\/fonts\/ahem.css\" \/>\n\1<style/g' Then edited to wait for document.fonts.ready in testharness.js tests
This is: rg --files-with-matches 'grid-descendants.css' css/css-grid/abspos/ | xargs grep -L ahem.css | xargs gsed -i'' -e 's/\(^.*\)\(<.*grid-descendants.css\)/\1<link rel=\"stylesheet\" href=\"\/fonts\/ahem.css\">\n\1\2/g'
Okay, no regressions in Safari/Firefox/Chrome, so rebased and cleaned up history so we can land this! |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thanks!
Add ahem.css to many more tests
In addition to #17291, and following on from #17173. Will probably need regressions split out, as in #17205.
cc/ @LukeZielinski