@gorhill gave you investigated using a PAC script in a browser extension to modify network requests? If so, I'd love to get your thoughts on that approach
@WebReflection@mozamo I created a PR to get the extension working in Firefox and Safari. LMK if any changes are unclear or if you can't get it to run as expected https://t.co/CZoUBHsXJK
@WebReflection@mozamo Sorry I disappeared for a bit
Depends on what you mean by 'there with MV3.' Firefox and Safari don't have 1:1 parity with Chrome and probably never will for boring technical reasons. For example, neither currently plan to implement offscreen docs 'cause they still have bg pages
@WebReflection Thanks for the feedback
FWIW Firefox uses the `js` or `page` fields rather than `service_worker`. The "Demo of service worker + event page" example shows how to you can configure a single manifest.json file that works in Chrome and Firefox/Safari
https://t.co/zI4kL0xbT4
@WebReflection If you have any other feedback on how we can improve Web Extensions docs on MDN or the add-on developer experience in Firefox, you're welcome to tag me or @mozamo
@WebReflection The last item in the screenshot is a non-blocking warning. The page it links shows a few different examples of how an extension dev can configure their data collection disclosures
@MSEdgeDev Also there's no way to report this error in Partner Center. If you follow the Contact support link, the contact from requires you to pick a Workspace which I can't do because I can't add the Edge program in the first place
@MSEdgeDev looks like the Partner Center site won't allow you to register for the Microsoft Edge program. Visiting https://t.co/cjnr7xymra returns an HTTP 500 response with no error information