
This content/public method shouldn't be used, because this bypass most of the navigation code and will inherit the wrong security properties. It might be good enough for testing, and is currently used only as such. Appending ForTesting to make it clear. Context: I would like to push the sandbox flags from the browser process. There are some unit test running without a browser process and dummy flags will be provided. I need to convince this would be for testing only. Bug: 1151340,1041376 Change-Id: I4004711692713360a3f4517db9f4f3a2962e9c12 Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/2631271 Commit-Queue: Istiaque Ahmed <lazyboy@chromium.org> Reviewed-by: Istiaque Ahmed <lazyboy@chromium.org> Reviewed-by: Camille Lamy <clamy@chromium.org> Auto-Submit: Arthur Sonzogni <arthursonzogni@chromium.org> Cr-Commit-Position: refs/heads/master@{#844253}
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: