Skip to content
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

Use SSL on fonts.googleapis.com scss import #4209

Conversation

RyanofWoods
Copy link
Contributor

@RyanofWoods RyanofWoods commented Nov 24, 2021

Since 23/11/2021, @import url(//fonts.googleapis.com/css...) began to
cause errors; Breaking Solidus and all extensions that depend on
solidus_frontend. Explicitly using https protocol fixed this.

Error example:
https://app.circleci.com/pipelines/github/solidusio/solidus/2791/workflows/e62ff646-9ae6-4e65-b20f-e1f7a109d3a1/jobs/26572

Blocking of this URL in testing_support was updated to keep performance
improvement.

Checklist:

@RyanofWoods RyanofWoods marked this pull request as ready for review November 24, 2021 09:34
@RyanofWoods
Copy link
Contributor Author

I am not really sure why this line suddenly started causing issues. Would be interested to know if anyone has any insight.

Copy link
Contributor

@waiting-for-dev waiting-for-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Many thanks for looking into it @RyanofWoods! ❤️

I haven't found anything out there, but I guess that since that date, fonts.googleapis.com doesn't support non-SSL connections anymore. Anyway, it's good from our side to request through HTTPS.

I think we also need to update the URL here:

browser.url_blacklist = ['http:https://fonts.googleapis.com']

I'd also take the occasion to remove the duplication from this line:

page.driver.browser.url_blacklist = ['http:https://fonts.googleapis.com']

And instead require spree/testing_support/blacklsit_urls as is done from the frontend engine:

require 'spree/testing_support/blacklist_urls'

@RyanofWoods RyanofWoods force-pushed the fix/frontend-scss-font-url-import branch from 1ddb10a to 63abd1d Compare November 24, 2021 11:22
@RyanofWoods RyanofWoods changed the title Fix Frontend scss font url import Use SSL on fonts.googleapis.com scss import Nov 24, 2021
Since 23/11/2021, `@import url(//fonts.googleapis.com/css...)` began to
cause errors; Breaking Solidus and all extensions that depend on
solidus_frontend. Explicitly using https protocol fixed this.

Error example:
https://app.circleci.com/pipelines/github/solidusio/solidus/2791/workflows/e62ff646-9ae6-4e65-b20f-e1f7a109d3a1/jobs/26572

Blocking of this URL in testing_support was updated to keep performance
improvement.
@RyanofWoods RyanofWoods force-pushed the fix/frontend-scss-font-url-import branch from 63abd1d to abd374e Compare November 24, 2021 12:02
Copy link
Contributor

@waiting-for-dev waiting-for-dev left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thanks @RyanofWoods 🙌 🙌

@RyanofWoods
Copy link
Contributor Author

Thanks @RyanofWoods 🙌 🙌

Thank you for your help @waiting-for-dev! Amazing spot with the testing_support 🙌

Copy link
Member

@kennyadsl kennyadsl left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

👍

Copy link
Member

@spaghetticode spaghetticode left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

@RyanofWoods thank you 👍

@waiting-for-dev waiting-for-dev merged commit 76e2875 into solidusio:master Nov 25, 2021
@kennyadsl
Copy link
Member

@RyanofWoods thanks! I think we need to release this in all the supported Solidus versions as well. Can you make the same PR against v3.1, v3.0 and v2.11, please?

@RyanofWoods
Copy link
Contributor Author

@RyanofWoods thanks! I think we need to release this in all the supported Solidus versions as well. Can you make the same PR against v3.1, v3.0 and v2.11, please?

Done @kennyadsl 👍 Let me know if I could have done it in a more helpful way 🙂

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

6 participants