bc782f1740
Extensions can inject in multiple user script worlds, which are
specified by different user script world (string) IDs. If an ID isn't
specified, the extension injects in the default user script world ID.
However, this creates an issue with trying to update a registered
script to inject in the default world after initially registered with
a non-default world:
* Specifying any non-null value indicates a non-default world
* Specifying a null value will be dropped by the extension bindings
To enable this, allow extensions to use the empty string ('') as an
indicator that a script should use the default world. The API layer
converts the empty string to nullopt for use elsewhere in the
extensions system.
Bug: 331680187
Change-Id: I4b0ef064884dc5fac814c0680134c278d0b28fcc
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/6036255
Reviewed-by: Kelvin Jiang <kelvinjiang@chromium.org>
Commit-Queue: Devlin Cronin <rdevlin.cronin@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1387164}
This will become a reusable extensions module. It implements the core parts of Chrome's extension system, and can be used with any host of the content module.
Some extensions code that is not Chrome-specific still lives in //chrome/browser/extensions and will be moved here.
Technical Documentation: