[fabrice_d]

"appeasing Mozilla" is not the reason that trigger these warning or errors. Privileged apps have access to more powerful apis but are also subject to a more stringent CSP (content security policy) to prevent running malicious code that would potentially hurt the user.

If jQuery's build system has options to create a version that is compliant with our CSP, I don't see any reason to be up in arms.

[jeena]

It doesn't, or at least it is not obvious from the documentation how to do it (yet).

As the one person on the list mentioned, the warnings should not be the reason for the rejection because they were kind of false positives, the only problematic thing is that they were.

They are still working out the issues I assume, it is a really young platform yet so it kind of could have been expected. I just wish there was a possibility to talk to the reviewer and ask them more questions.