New issue
Advanced search Search tips
Note: Color blocks (like █ or █) mean that a user may not be available. Tooltip shows the reason.

Issue 759303 link

Starred by 1 user
Status: WontFix
Owner: ----
Closed: Oct 2017
Cc:
█ hdodda@chromium.org
kebalaji@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

Chrome extension context menus' documentUrlPatterns, there is no way to match a URL like https://hannibal-1.openstacklocal:8443/#/login

Reported by pulki...@gmail.com, Aug 26 2017 
UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.101 Safari/537.36

Steps to reproduce the problem:
1. Just create a very simple extension which simply adds a context menu item on a webpage with a URL like
scheme://<host>/#/login
2. I have tried documentUrlPatterns like 
https://*/*/login
https://*/#/login
https://*/./login"
3. Not of these would work

What is the expected behavior?
I should be able to match a URL like
scheme://<host>/#/login
I am writing a plugin for Apache Ambari, all the URL patterns in Ambari are like that.

What went wrong?
documentUrlPatterns not working for 
scheme://<host>/#/login

Did this work before? No 

Chrome version: 60.0.3112.101  Channel: n/a
OS Version: OS X 10.12.6
Flash Version: Shockwave Flash 26.0 r0

Comment 1 by woxxom@gmail.com, Aug 26 2017 

The only URL matching mechanism that handles #fragment is "include_globs" and "exclude_globs" in manifest.json.
The rest of URL matching mechanisms in extensions API don't handle the #fragment part.

Currently, the documentation [1] only implicitly infers this by listing "scheme", "host", "path",
which are precise technical terms in URL specification [2] where "path" does not include "fragment".

I don't know why it's not documented explicitly.
Many developers don't know the URL standard and its terms.

  [1]: https://developer.chrome.com/extensions/match_patterns
  [2]: https://url.spec.whatwg.org/#concept-url-path

Comment 2 by schenney@chromium.org, Aug 28 2017

Components: -Blink Platform>Extensions>API

Comment 3 by hdodda@chromium.org, Aug 29 2017

Cc: hdodda@chromium.org
Labels: Needs-Triage-M60 Needs-Feedback
Thanks for reporting the issue.

@pulkitnt-- Could you please provide us the sample extension or test file to reproduce the issue and also help us with the screencast or screenshot of the expected result for better understanding.

Thanks!

Comment 4 by kebalaji@chromium.org, Oct 10 2017

Cc: kebalaji@chromium.org
Labels: Needs-Milestone
Status: WontFix (was: Unconfirmed)
Due to lack of user feedback closing this issue.
Please feel free to raise a new issue if you face any issue on chrome further.

Thanks..!!
►

Sign in to add a comment