strip 'http:' from font URLs to improve HTTPS support - #86
Merged
Conversation
jazzsequence
approved these changes
Nov 29, 2017
Owner
|
Thanks! I'll try to get this updated on wp.org but it probably won't happen until after WordCamp US (maybe during, if I have time). |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
'http:' in the font URLs was creating problems with my newly implemented Content Security Policy which required HTTPS origins. Removing the explicit protocol reference will make the resources adopt whichever is in use in the parent page. Should correct any mixed content warnings as well.