-
Notifications
You must be signed in to change notification settings - Fork 3.2k
Alternative: extra changes to Genericons #10427
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
Conversation
If these are retained, they should be wrapped in quotes: Automattic/Genericons#83
…or each `genericon-` class
…or each `genericon-` class
…ass" This reverts commit 6e452a6.
…bernhardt/wordpress-develop into Genericons-additional" This reverts commit a640cde, reversing changes made to 3d3181c.
|
The following accounts have interacted with this PR and/or linked issues. I will continue to update these lists as activity occurs. You can also manually ask me to refresh this list by adding the Core Committers: Use this line as a base for the props when committing in SVN: To understand the WordPress project's expectations around crediting contributors, please review the Contributor Attribution page in the Core Handbook. |
Test using WordPress PlaygroundThe changes in this pull request can previewed and tested using a WordPress Playground instance. WordPress Playground is an experimental project that creates a full WordPress instance entirely within the browser. Some things to be aware of
For more details about these limitations and more, check out the Limitations page in the WordPress Playground documentation. |
|
|
||
|
|
||
| /** | ||
| * The font was graciously generated by Font Squirrel (http://www.fontsquirrel.com). We love those guys. |
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.
No more love? 🫶
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.
💔😢
I removed that sentence for WordPress guidelines, but Genericons is from Automattic. I'll leave it out for now because "graciously" should be enough.
| src: url('Genericons.eot'); | ||
| } | ||
|
|
||
| /* When the font is base64 encoded, cross-site embedding works in Firefox */ |
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.
Maybe this comment should just be removed now? It seems it was specifically here because of the previous four lines. It seems unnecessary now, since it's not contrasting with anything.
| /* When the font is base64 encoded, cross-site embedding works in Firefox */ |
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.
The way I read the full comment block, both IE9 and Firefox (at that time) required encoding the WOFF. It gave me a reason not to suggest replacing it with the external src URL.
That said, I do not mind removing the entire comment.
| IE9 uses WOFF which is base64 encoded to allow cross-site embedding. | ||
| So unfortunately, IE9 will throw a console error, but it'll still work. | ||
| When the font is base64 encoded, cross-site embedding works in Firefox */ | ||
| /* When the font is base64 encoded, cross-site embedding works in Firefox */ |
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.
| /* When the font is base64 encoded, cross-site embedding works in Firefox */ |
Co-authored-by: Weston Ruter <[email protected]>
Co-authored-by: Weston Ruter <[email protected]>
|
|
||
| @font-face { | ||
| font-family: 'Genericons'; | ||
| src: url('Genericons.eot'); |
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.
Remove the Genericons.eot file if we don't need it.
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.
Is there any way we can check how many sites use child themes?
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.
I'm not aware of a way to count the sites.
I have built a number of sites using child themes of three of these four. I also have dequeued the Genericons stylesheet more than once, but then the site was not using a font for its icons. Someone else could have taken another step and created their own version of the Genericons stylesheet.
|
Would these changes be proposed upstream at https://github.com/Automattic/Genericons also? |
sabernhardt
left a comment
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.
Automattic/Genericons#109 and Trac 43195 note that the zero-second transition-delay value is default anyway.
Props: manuel_84, GaryJ, SergeyBiryukov
Props: manuel_84, GaryJ, SergeyBiryukov
The Additional changes could be suggested upstream, but I doubt it will be updated anymore. Automattic/Genericons#105 and Automattic/Genericons#106 encouraged using Genericons Neue or Social Logos instead in 2016, and the last update to this project's repository was five years ago. |
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 for working on this, I've confirmed it prevents the font from loading twice in Firefox.
As noted by @mukeshpanchal27, the font files can be removed with the change to only include the encoded woff font. (eot, svg and ttf)
I might be having a silly but I can't actually see where the icons are used in 2016. Can I get a logic check on that?
In the other themes, the font is always been used when the stylesheet is included so I think leaving the file base64 encoded inline is good, it avoids an HTTP request.
I prefer not to delete any files.
T16 uses the icons in several places, anywhere the |
OK, I'm happy to follow your advice on this as you work on the bundled themes heaps more than I do. |
westonruter
left a comment
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.
@sabernhardt I'm happy to commit this for you if you like.
Thanks! |
This updates Twenty Thirteen, Twenty Fourteen, Twenty Fifteen, and Twenty Sixteen as follows: * Remove legacy Internet Explorer support by deleting EOT file rules from CSS. * Remove IE hacks from the version included in Twenty Thirteen and Twenty Fourteen. * Remove `filter` rules from the CSS included in Twenty Sixteen. * Remove the TTF and SVG `src` references for all four themes. * Remove all prefixes from transform in the rotate and flip classes available in Twenty Sixteen. * Edit the values for prefixed transition properties in Twenty Fifteen and Twenty Sixteen. * Update CSS comments. Developed in #10427 Props sabernhardt, metodiew, peterwilsoncc, mukesh27, westonruter. See #56699, #58836. Fixes #62128. git-svn-id: https://develop.svn.wordpress.org/trunk@61109 602fd350-edb4-49c9-b593-d223f7449a82
|
Committed in r61109. |
This updates Twenty Thirteen, Twenty Fourteen, Twenty Fifteen, and Twenty Sixteen as follows: * Remove legacy Internet Explorer support by deleting EOT file rules from CSS. * Remove IE hacks from the version included in Twenty Thirteen and Twenty Fourteen. * Remove `filter` rules from the CSS included in Twenty Sixteen. * Remove the TTF and SVG `src` references for all four themes. * Remove all prefixes from transform in the rotate and flip classes available in Twenty Sixteen. * Edit the values for prefixed transition properties in Twenty Fifteen and Twenty Sixteen. * Update CSS comments. Developed in WordPress/wordpress-develop#10427 Props sabernhardt, metodiew, peterwilsoncc, mukesh27, westonruter. See #56699, #58836. Fixes #62128. Built from https://develop.svn.wordpress.org/trunk@61109 git-svn-id: http://core.svn.wordpress.org/trunk@60445 1a063a9b-81f0-0310-95a4-ce76da25c4cd
This updates Twenty Thirteen, Twenty Fourteen, Twenty Fifteen, and Twenty Sixteen as follows: * Remove legacy Internet Explorer support by deleting EOT file rules from CSS. * Remove IE hacks from the version included in Twenty Thirteen and Twenty Fourteen. * Remove `filter` rules from the CSS included in Twenty Sixteen. * Remove the TTF and SVG `src` references for all four themes. * Remove all prefixes from transform in the rotate and flip classes available in Twenty Sixteen. * Edit the values for prefixed transition properties in Twenty Fifteen and Twenty Sixteen. * Update CSS comments. Developed in WordPress/wordpress-develop#10427 Props sabernhardt, metodiew, peterwilsoncc, mukesh27, westonruter. See #56699, #58836. Fixes #62128. Built from https://develop.svn.wordpress.org/trunk@61109 git-svn-id: https://core.svn.wordpress.org/trunk@60445 1a063a9b-81f0-0310-95a4-ce76da25c4cd
This is a superset of #7452
Alternative:
In addition to removing the EOT,
filter, and various hacks, this includes three extra changes to consider.srcreferences for all four themes.transformin the rotate and flip classes available in Twenty Sixteen.Props: metodiew
Trac 62128
This Pull Request is for code review only. Please keep all other discussion in the Trac ticket. Do not merge this Pull Request. See GitHub Pull Requests for Code Review in the Core Handbook for more details.