SameSite cookies, CORP) and privacy features of Firefox (e.g.
This feature will be gradually enabled by default on Firefox Beta in the upcoming months and will start rolling out a small percentage of release users in Q3 2021.Ĭross-origin requests in content scripts already encounter restrictions by advances of the web platform (e.g. You can test how your extension performs in site isolation on the Nightly pre-release channel by going to about:preferences#experimental and enabling Fission (Site Isolation). Some of this work is underway as part of Site Isolation, a larger reworking of Firefox’s architecture to isolate sites from each other. In our initial response to the Manifest v3 proposal, we committed to implementing cross-origin protections. The following is an overview of our plan to move forward, which is based on those conversations. However, we will diverge from Chrome’s implementation where we think it matters and our values point to a different solution.įor the last few months, we have consulted with extension developers and Firefox’s engineering leadership about our approach to Manifest v3. We will introduce Manifest v3 support for Firefox extensions.
As we previously wrote, we want to maintain a high degree of compatibility to support cross-browser development.
Many of these changes introduce new incompatibilities between Firefox and Chrome. Two years ago, Google proposed Manifest v3, a number of foundational changes to the Chrome extension framework.
0 kommentar(er)
