SetCurrentChannel/SetCurrentFeatureSessionType not called in the utility process. |
||
Issue descriptionWe don't call SetCurrentChannel/SetCurrentFeatureSessionType in the utility process. However these are used in the utility process. See extensions/utility/unpacker.cc, which calls Extension::Create, which would parse the manifest. This can lead to invalid checks. (For e.g., a feature which is available on trunk only, would be shown as not available in the utility process when on trunk, since the default channel is stable).
,
Jun 29 2017
|
||
►
Sign in to add a comment |
||
Comment 1 by bugdroid1@chromium.org
, Jun 29 2017