When populating the per-permission view of exceptions (e.g. Site Settings > Microphone) the wrong values may show up for patterns that are listed in this view. This is because it is currently querying the PermissionManager::GetPermissionStatus to determine these values, but this API only accepts origins and not patterns.
Most permissions on Android can't generally be set for patterns (e.g. there is no way to enter patterns for microphone, no enterprise policy, etc.) but there are odd cases where it can happen (see, e.g. issue 738377). And it's extremely error-prone.
Android site-settings code would benefit from some refactoring.
Comment 1 by raymes@chromium.org
, Jul 3 2017