Add window.chrome properties to webexposed tests |
||||||
Issue descriptionWe've got a bunch of legacy non-standard APIs exposed on the window.chrome object (eg. via RenderThread::RegisterExtension) that aren't covered by the webexposed tests because there is no interface object for them. Assuming arch team has no plans to move these to use the IDL bindings (haraken/esprehn?) then we should extend the webexposed tests to track the exposed properties explicitly.
,
Jan 3 2017
,
Sep 12 2017
,
Sep 27 2017
See https://bugs.chromium.org/p/chromium/issues/detail?id=768486#c3 for an example of how this matters. Installed-by-default extensions can effectively (accidentally or intentionally) augment Chrome's API surface area without going through any of our normal API launch process gates/validation. Perhaps we should add some sort of chrome-specific webexposed tests (with API_OWNERS review restrictions like other virtual/stable/webexposed results) to some testing target that has the full chrome build available?
,
Mar 29 2018
Paul, can you take this? You've done similar work recently on webexposed tests, I think.
,
Dec 14
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by esprehn@chromium.org
, Nov 15 2016