Issue metadata
Sign in to add a comment
|
Chrome for Android does not support site settings exceptions with a non-leading glob: https://[*.], https://*
Reported by
neri...@gmail.com,
Mar 18 2016
|
||||||||||||||||||||||
Issue descriptionDevice name: Nexus 5X From "Settings > About Chrome" Application version: Chrome Dev 51.0.2681.4 OS: Android 6.0.1; Nexus 5X Build/MHC19J Behavior in Android Browser (if applicable): The same Site Settings exception matches that work in Chrome Dev on OSX (50.0.2661.37) are not accepted on Chrome Dev on Android, namely those with non-leading globs/wildcards, eg https://[*.] or https://*. Matches like [*.]google.com are accepted. Steps to reproduce: (1) Go to Settings > Site settings (2) Select 'JavaScript' (3) Set JavaScript to 'Blocked' (4) Select 'Add Site' (5) In Site URL field, enter "https://*" or "https://[*.]" Expected result: Input accepted as valid site exception match, JavaScript enabled for https: sites only, disabled on http: sites (assuming no other site exceptions). Actual result: Input is not accepted as a valid site exception match value.
,
Mar 26 2016
raymes, might this be WAI and/or related to your recent changes?
,
Mar 29 2016
It's probably been this way since it was implemented on Android. So sort of WAI. But consistency would be better. We're looking at improving exceptions UI on android so I'm happy to leave this assigned to me for now but it's low priority. If someone wanted to jump in and make a quick fix, that would be fine too.
,
Nov 30 2016
,
Nov 10 2017
,
Feb 18 2018
,
Aug 1
|
|||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||
Comment 1 by palmer@chromium.org
, Mar 18 2016Components: UI>Settings Security>UX
Status: Available (was: Unconfirmed)