Missing Font CSP Paylater Popup

[in-session]

Paylater Popup:
Refused to load the font 'https://www.paypalobjects.com/webstatic/mktg/2014design/font/PP-Sans/PayPalSansBig-Medium.woff' because it violates the following Content Security Policy directive

Update:
Refused to frame 'https://www.paypalobjects.com/' because it violates the following Content Security Policy directive:

Description (*)

Related Pull Requests

Fixed Issues (if relevant)

1. Fixes magento/magento2#<issue_number>

Manual testing scenarios (*)

1. ...
2. ...

Questions or comments

Contribution checklist (*)

• Pull request has a meaningful description of its purpose
• All commits are accompanied by meaningful commit messages
• All new or changed code is covered with unit/integration tests (if applicable)
• README.md files for modified modules are updated and included in the pull request if any README.md predefined sections require an update
• All automated tests passed successfully (all builds are green)

Resolved issues:

1. resolves [Issue] Missing Font CSP Paylater Popup #38624: Missing Font CSP Paylater Popup

[m2-assistant]

Hi @in-session. Thank you for your contribution!
Here are some useful tips on how you can test your changes using Magento test environment.

Add the comment under your pull request to deploy test or vanilla Magento instance:

• @magento give me test instance - deploy test instance based on PR changes
• @magento give me 2.4-develop instance - deploy vanilla Magento instance

❗ Automated tests can be triggered manually with an appropriate comment:

• @magento run all tests - run or re-run all required tests against the PR changes
• @magento run <test-build(s)> - run or re-run specific test build(s)
  For example: @magento run Unit Tests

<test-build(s)> is a comma-separated list of build names.

Allowed build names are:

1. Database Compare
2. Functional Tests CE
3. Functional Tests EE
4. Functional Tests B2B
5. Integration Tests
6. Magento Health Index
7. Sample Data Tests CE
8. Sample Data Tests EE
9. Sample Data Tests B2B
10. Static Tests
11. Unit Tests
12. WebAPI Tests
13. Semantic Version Checker

You can find more information about the builds here
ℹ️ Run only required test builds during development. Run all test builds before sending your pull request for review.

---

For more details, review the Code Contributions documentation.
Join Magento Community Engineering Slack and ask your questions in #github channel.

[mrtuvn]

Here is one example for speed-up improve merge process. When risk low and changes small i think we can have option merge for some maintainer can ability to merge immediately(Require at least two reviewer accept)

[engcom-Hotel]

@magento run all tests

[engcom-Hotel]

@magento create issue

[engcom-Charlie]

Hi @in-session,

Thank you for your contribution!

In order to proceed further on this PR, I have followed the below steps on 2.4-develop
1. Setup Paypal Express checkout in admin
2. Set Enable In-Context Checkout Experience to "Yes"
3. In Advertise PayPal Pay Later section select "Yes" for "Enable PayPal Pay Later". Enabled it on Home page, Catalog Product Page
4. Visit storefront
5. On home page we can see PayPal pay later button. Clicked on it.

✔️ QA Passed

Before: ✖️
Got errors in console about woff font because of violating CSP

After: ✔️
Not getting error about WOFF

Since the build is failing, currently moving it further in Extended Testing.

Thank you!

[engcom-Charlie]

@magento run all tests

[engcom-Charlie]

@magento run Functional Tests B2B, Functional Tests EE, WebAPI Tests

[engcom-Charlie]

@magento run WebAPI Tests

[engcom-Charlie]

The functional B2B and EE failures are different in recent 2 runs they seems to be flaky. Few failures are repetitive but they are known issues.

Repetitive failures in B2B with open issue is:

1. ACQE-6438 - StorefrontPropertiesOfAProductAttributeTest

Functional B2B: Run1:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37401/685d3ca21e4d3e195b993c9a4244c759/Functional/allure-report-b2b/index.html#categories

Run 2:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37401/f48291e355660b57a40b38dac9743e6c/Functional/allure-report-b2b/index.html#categories

Functional EE: Run1:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37401/dadd50cbf4d537b95cf5624d8ecd2c78/Functional/allure-report-ee/index.html#categories

Run 2:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37401/d488c56ff5b0e537b36fbb2be10fb1de/Functional/allure-report-ee/index.html#categories

Repetitive failures in EE with open issues are:

1. ACQE-6438 - StorefrontPropertiesOfAProductAttributeTest
2. ACQE-6331 - StorefrontCreateOrderAllQuantityGroupedProductOptionDefaultStockTest

[engcom-Charlie]

The WebAPI failure in recent 2 build is a known issue. It is not related to this PR. Hence moving the PR to Merge in Progress now.
AC-11750 - testGetCustomerDescendingSortedOrders

Run 1:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37401/fc7629b184bedd5d43176b82573b838b/WebApi/console-error-logs.html

Run 2:
https://public-results-storage-prod.magento-testing-service.engineering/reports/magento/magento2/pull/37401/00a2ee523d034ce33c850d2a9736b9b6/WebApi/console-error-logs.html