You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
We could potentially delay the loading of pay.js on Drop-in , if GooglePay is available within the list of payment methods and it is not 'active'.
Another point to highlight is that Magento does not use Drop-in as far as I known, so if this change is required, they will need to update on their side as well and lazy-load the component.
We are checking this internally with the team and I will get back to you as soon as I find out more if we need to make these changes from our side.
An update from our side: our colleagues are in contact with Google, and GooglePay mentioned that they do not store the IP address and they are investigating this further.
I will keep you posted as soon as we find out more about this.
GooglePay team mentioned that they do not store any shopper related data when requesting the fonts. For more information regarding this, you can check the Google Font FAQ Privacy page.
Therefore we are going to close this ticket for now. Thanks for reaching out!
Copied from / follow up from Adyen/adyen-magento2#2281
Describe the bug
As long as Google Pay is provided in the Checkout, a connection to fonts.googleapis.com is made
To Reproduce
Steps to reproduce the behavior:
Expected behavior
Google fonts are only loaded if the user gives consent.
Magento version
2.4.5
Plugin version
8.10.0
Screenshots
Desktop (please complete the following information):
Additional context
In Germany there are was a wave of cease and desist letters to not use Google Fonts, so this is a quite important topic.
I guess it would be okay to load google fonts as soon as Google Pay is selected, but it is loading initially on opening the checkout.
Can this be optimized?
The text was updated successfully, but these errors were encountered: