Issue metadata
Sign in to add a comment
|
Extension IMEs unavailable in MD Settings |
||||||||||||||||||||||
Issue descriptionIf chrome://settings points to MD Settings, we break a extension permissions for inputMethodPrivate and quickUnlockPrivate. https://cs.chromium.org/chromium/src/chrome/common/extensions/api/_api_features.json?q=file:chrome/common/extensions/api/_api_features.json+md-settings.*%5C%22$&sq=package:chromium&l=702&dr=C
,
Jul 13 2016
The following revision refers to this bug: https://chromium.googlesource.com/chromium/src.git/+/e88ced52cb6cfc584882b726f142b13db97d2f1c commit e88ced52cb6cfc584882b726f142b13db97d2f1c Author: michaelpg <michaelpg@chromium.org> Date: Wed Jul 13 22:56:08 2016 Whitelist extension APIs from md-settings in settings If the MaterialDesignSettings feature is enabled, chrome://settings loads MD settings, so whitelist extension APIs there too. The test will involve adding the MaterialDesignSettings feature and checking for console errors. Looking into the best way to do that. BUG= 627932 R=dbeam@chromium.org Review-Url: https://codereview.chromium.org/2148043002 Cr-Commit-Position: refs/heads/master@{#405332} [modify] https://crrev.com/e88ced52cb6cfc584882b726f142b13db97d2f1c/chrome/common/extensions/api/_api_features.json
,
Jul 14 2016
,
Jul 14 2016
,
Aug 29 2016
,
Oct 7 2016
,
Oct 21 2016
Verified on ChromeOS 8872.18.0, 55.0.2883.20 No console errors are seen. Also languages section is present(from the duplicate bug) |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by michae...@chromium.org
, Jul 13 2016