Hey there,
I have been really struggling with reviews on addon.mozilla.org. We submit our source code for review, and that has been the process for a long time. We have not had many issues with the Firefox review process, but recently we have got stuck on quite a few issues. Some of the stuff is minor, like us updating the instructions to make sure the reviewer does not go through internal developer steps for building the addon. But there is some stuff that we have been recently getting that has been causing lots of additional work, and TBH most of the stuff mentioned is nowhere in the guidelines and policies around building and addon.
Internally hosted data consent pages.
This was something that essentially we have been doing for years now, and this allowed us to create a great onboarding experience for our users on our website. We communicate back and forth with our website via a content script to allow different controls to be initially set on these pages. I feel like it’s nothing super uncommon. Even large companies like Honey do this same thing.
We have recently got feedback we can’t do that, and we need to host this page inside of the extension. We went back and forth on the review, and we ended up having to implement some additional data consent settings. Felt like things were moving forward, but now we are stuck back at square one again. It seems like we are being rejected for this again, even though I have not been given any documentation around this requirement. Has anyone experienced this before, and if so, is there any resources or documentation around these requirements? I hate going back to the product manager with these types of changes without having a good reason for them.
A little bit more about the implementation:
- Website communicates with addon via content script and
postMessage
. - The value that sets the users data consent is stored in the extension local storage.