Issue metadata
Sign in to add a comment
|
Permissions Layer/Content Settings Refactor |
||||||||||||||||||||||
Issue descriptionCurrently code in chrome/ accesses permissions through both Content Setting and the Permissions layer code. Depending on which layer is used, different results will be observed, leading to potential bugs. It also leads to difficulty when attempting to access permissions data. Some pieces of code need the PermissionType but only have the ContentSettingsType (or vice-versa).
,
Dec 4 2016
,
Dec 11 2017
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. If you change it back, also remove the "Hotlist-Recharge-Cold" label. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 11 2017
,
Dec 12
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Dec 21
Passing to engedy to decide if this should remain available. |
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by mlamouri@chromium.org
, Apr 21 2016