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

Issue 773962 link

Starred by 1 user

Issue metadata

Status: WontFix
Owner: ----
Closed: Oct 27
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 2
Type: Bug



Sign in to add a comment

Adding sites with wild characters not allowed in Block Notification

Reported by angc...@gmail.com, Oct 12 2017

Issue description

UserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/61.0.3163.100 Safari/537.36

Steps to reproduce the problem:
1. Open chrome://settings/content/notifications
2. Click Add (to Block section) 
3. In the "Add a site" input box, wild characters [*] is not accepted. Shows error "Not a valid web address"

What is the expected behavior?
*.domainName.com should be acceptable

What went wrong?
Not accepting wild characters

Did this work before? N/A 

Chrome version: 61.0.3163.100  Channel: stable
OS Version: 10.0
Flash Version:
 
Cc: susanjuniab@chromium.org
Components: UI>Settings
Labels: Needs-Feedback Needs-Triage-M61
angchuk@ thanks for the issue.

Tested this issue on the latest Stable and Canary on Windows 7 and Mac OS by following the below steps.

1. Launched Chrome and navigated to chrome://settings/content/notifications
2. Clicked on Add under Block and to add sites with wild characters, we should enter [*]domain.com. Eg. [*.]yahoo.com and no issue is observed.
Attached is the screen cast for reference.

Below is the link for Google Chrome Help for 'Allowing or blocking content settings for certain sites'.
https://support.google.com/chrome/answer/3123708?visit_id=0-636434699580522258-922341743&p=settings_manage_exceptions&rd=1

Request you to please retry the issue and update the thread if there are any issues.

Thanks..
773962.png
32.6 KB View Download

Comment 2 by angc...@gmail.com, Oct 13 2017

Thanks, Did not realise that [*.]
means that the Square brackets is a Part of the optional parameter of wild
characters.

Usually we represent optional parameters in command line arguments is
enclosed in square bracket,
I feel that better thing would be to accept "*.domain.com" as a valid entry
in addition to "[*.]domain.com"

regards
Angchuk
Project Member

Comment 3 by sheriffbot@chromium.org, Oct 13 2017

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding requester "susanjuniab@chromium.org" to the cc list and removing "Needs-Feedback" label.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: M-63 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome reported version #61.0.3163.100 and latest canary #63.0.3239.6.
This is a non-regression issue as it is observed from M50 old builds. 

Hence, marking it as untriaged to get more inputs from dev team.

Thanks...!!
Status: WontFix (was: Untriaged)
Working as expected per comment #1.

Sign in to add a comment