1340402 - Add-on documentation for how to access external data sources

Status: RESOLVED WONTFIX

(Developer Documentation Graveyard :: Add-ons, defect)

Description

[Amy Tsay [:amyt]]

I'll need @jorgev to provide more details, but the gist is we need to have an MDN page to point developers to when they've written a content script add-on that needs to access an external data source. This is so they can keep the add-on updated without having to re-submit for review with every data refresh (since they are updating the data and not the code).

It would be good to provide some best practices guidance, like not inadvertently including script that will automatically trigger a rejection, especially if the script is not needed for the add-on to function.

I know this is kind of vague, which is why @jorgev will need to chime in.

Comment 1

[Jorge Villalobos [:jorgev] (he/him)]

This would apply to all WebExtensions and essentially comes down to "don't run code obtained from a remote source". So, the guide would just make it clear to developers that they should interact with data-only APIs instead of injecting remote scripts or using eval or innerHTML to evaluate downloaded code.

Comment 2

[BMO Automation]

MDN Web Docs' bug reporting has now moved to GitHub. From now on, please file content bugs at https://github.com/mdn/sprints/issues/ and platform bugs at https://github.com/mdn/kuma/issues/.