Steps to reproduce the problem:
1. Trigger a Web Push Notification
2. See the Notification has a "Site Settings", or "Settings" or a gear icon action (depending on Chrome or OS UI, and kind of notification sent
3. Tap on this settings action, the common site settings view opens instead of Notification Settings directly

What is the expected behavior?
The notification's action (settings call-to-action) should take the user directly to notification settings

What went wrong?
Web Push Notifications on Chrome for Android have a default action that opens up the "Site Settings" panel that then has sections for "Notifications", "Sound" and so on, with a "CLEAR & RESET" button below which is the primary call-to-action on the page and immediately catches a user's attention.

Why does the notification action take the user to Site Settings and not the Notification Settings directly, since that whole option exists in itself? 

* If someone wanted to change a website's notification settings, they should be expected to be taken to this option instead rather than having to make one more click.

* On the other side, the current behaviour may be quite dangerous. Users who are not very tech savvy may not understand that tapping on the "CLEAR & RESET" button (first thing they notice) would remove *every* preference they have put on the website that includes cookies (their logged in state), local storage data, permissions, audio/video preferences, and so on. They will mistakenly lose everything. Not to mention the pain this causes for a website owner since all the recognition context or trust/permissions they have worked hard to establish with that user over some time will be eradicated in a second. 

Did this work before? N/A 

Chrome version: 68.0.3440.91  Channel: stable
OS Version: 
Flash Version: 

We should be more careful to not expose all the general & powerful site/browser preferences eradication settings all together at once this openly. I know that a confirmation is asked that all data including cookies would be reset, but I don't think most people who are not very tech savvy users, either read it or understand it properly; or are even looking to do when they tapped on the "settings" action from the web notification... A lot of people who are general web users don't even understand what a cookie means, neither should we have to expect them to - they could be people who have been introduced to the web relatively recently (...imagine all the new people coming to internet every day in countries like India who are still learning to properly use their smartphones and the browser...) They may have subscribed to web push, didn't like it, and just wanted to turn that particular thing off, but instead the browser cleared off all data, including cookies, so now they have to log in again and be asked for preferences again. That's a lot of website usage friction that could be caused by a mistake!