![\"Kerri](\"https:\/\/miro.medium.com\/v2\/resize:fill:88:88\/1*wIN2UJ15mEdnIYTTVG-r3w.jpeg\")
<\/div>\n<\/div>\n<\/a><\/div>\n<\/div>\n
![\"Adobe](\"https:\/\/miro.medium.com\/v2\/resize:fill:48:48\/1*riyFijvwTfGcWNf1guRNtg.png\")
<\/div>\n<\/div>\n<\/a><\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n<\/div>\n Adobe Express will soon enforce cross-origin isolation for Chromium-based browsers<\/strong> (including Chrome, Microsoft Edge, Opera, and others). This change may negatively impact your add-on\u2019s functionality due to stricter rules enforced by the browser. You\u2019ll want to ensure that any add-ons you\u2019ve developed or are building now work in this new environment.<\/p>\n Note: <\/strong>We expect the enforcement of cross-origin isolation headers to begin around the end of 2024. We\u2019ll provide an update here and in our documentation the moment we have a more certain date.<\/p>\n This change may impact your add-on\u2019s access to external resources, especially if your add-on relies on iframes to display content or support payment flows. This could also impact add-ons that make Currently, this change only impacts Chromium-based browsers (e.g., Chrome, Edge, Opera, etc.). This change also applies to add-ons running on Android devices if you\u2019ve developed a mobile add-on. Firefox and Safari browsers are not impacted.<\/p>\n Note:<\/strong> This affects all<\/em> add-ons even if they aren\u2019t published in the add-on marketplace. This includes both private and internally distributed add-ons.<\/p>\n Some failures will be more obvious than others, but all can negatively impact the user experience of your add-on.<\/p>\n Until Adobe Express enables these headers by default, you can verify that your add-on will function correctly by applying local header overrides. We\u2019ve provided full instructions on simulating these headers in our developer documentation<\/a>.<\/p>\n While most add-ons are likely to be unaffected by this change, you should double-check any flows that access external content or embed resources from other domains in your add-on\u2019s user interface. This includes purchase flows, loading external content in iframes, displaying assets from external domains, and adding content to the user\u2019s document that originates from an external domain.<\/p>\n Check out the documentation for more detail.<\/a><\/p>\n If you do encounter issues in your add-on related to cross-origin isolation, these are generally easy to address. You should check your add-on as soon as possible however\u2014if you rely on a third-party service, you may have to do more work to address any cross-origin isolation issues.<\/p>\n Read our documentation for more detail on fixing issues.<\/a><\/p>\n You should review the documentation<\/a> for complete details about cross-origin isolation which includes steps on setting up your local environment for testing. You should also keep an eye on the changelog<\/a> as the documentation will be updated over time.<\/p>\n While we expect that the majority of add-ons are not <\/em>impacted or affected, we are performing smoke tests for currently published add-ons to double-check. If we encounter any add-ons with failures, we\u2019ll reach out to the developers of the affected add-ons. However, it is wise for all add-on developers to test their add-ons since they know their add-on inside and out.<\/em><\/strong><\/p>\n All new add-ons published to the marketplace will be reviewed with these headers in place. If the reviewer finds a problem with your submission related to cross-origin isolation that impacts the usability of your add-on, the reviewer will reject your add-on.<\/p>\n If you have issues testing your add-on or addressing any issues relating to this change, don\u2019t hesitate to let us know<\/a>.<\/p>\n<\/div>\n![\"\"](\"https:\/\/miro.medium.com\/v2\/resize:fit:640\/format:webp\/1*PsAIksivYIiDbRyisLx3yg.jpeg)
fetch<\/code> calls or display images from external sources. If your external source is not properly configured, users may see missing content or may encounter silent failures if your add-on can\u2019t load a remote resource. Since this results in a poor experience, developers must ensure that their add-ons work in this new environment.<\/p>\nTypes of Failures<\/h2>\n
\n
What should you test?<\/h2>\n