New issue
Advanced search Search tips

Issue 698535 link

Starred by 3 users

Issue metadata

Status: Archived
Owner: ----
Closed: Mar 2018
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 2
Type: Bug



Sign in to add a comment

extension manifest permissions - hostname wildcard should include domain without hostname

Reported by jeffgem...@gmail.com, Mar 4 2017

Issue description

UserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_3) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/57.0.2987.88 Safari/537.36

It seems odd that specifying the permissions of a domain as such:
"*://*.domain.com/" does not cover the instance of where the domain allows for no hostname "*://domain.com/".  Both have to be specified in the permissions.  It seems a wildcard for the domain should include any host to include none.  It's usually the same host as www.

Steps to reproduce the problem:
1. "*://*.familysearch.org/"
2. Go to https://familysearch.org/
3. Lack permission

What is the expected behavior?
"*://*.familysearch.org/" would provide sufficient permission for https://familysearch.org/ without also having to specify "*://familysearch.org/" in the manifest file.

What went wrong?
Not a big deal once you know, but not intuitive and makes it appear like you're requesting more sites / permissions than you are.

WebStore page: https://chrome.google.com/webstore/detail/smartcopy/ofikakkdpjlipbnhbfloclbkcabdhjah?hl=en

Did this work before? No 

Chrome version: 57.0.2987.88  Channel: n/a
OS Version: OS X 10.12.3
Flash Version: Shockwave Flash 25.0 r0

 
Project Member

Comment 1 by sheriffbot@chromium.org, Mar 5 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment