Open swissspidy opened 3 years ago
For the Web Stories WordPress plugin we set cross-origin isolation on some admin pages, which requires loading 3P resources with the crossorigin attribute.
crossorigin
If not done, loading these resources will fail with console errors. This is the case for the Notifications module. And potentially others as well.
The tracking pixel should be loading just fine, no console errors.
For this, the <img> needs to be loaded with the crossorigin attribute.
<img>
The image itself should have a Access-Control-Allow-Origin: * response header.
Access-Control-Allow-Origin: *
See console error because tracking pixel is not loaded with crossorigin attribute
Screenshots If applicable, add screenshots to help explain your problem.
Internal reference: pMz3w-e4p-p2
Steps to reproduce the issue
For the Web Stories WordPress plugin we set cross-origin isolation on some admin pages, which requires loading 3P resources with the
crossorigin
attribute.If not done, loading these resources will fail with console errors. This is the case for the Notifications module. And potentially others as well.
What I expected
The tracking pixel should be loading just fine, no console errors.
For this, the
<img>
needs to be loaded with thecrossorigin
attribute.The image itself should have a
Access-Control-Allow-Origin: *
response header.What happened instead
See console error because tracking pixel is not loaded with
crossorigin
attributeScreenshots If applicable, add screenshots to help explain your problem.