Issue metadata
Sign in to add a comment
|
Permission requests disable hotkeys like ctrl+w
Reported by
josh.pru...@gmail.com,
Jan 31 2018
|
||||||||||||||||||||||||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.119 Safari/537.36 Steps to reproduce the problem: 1. Browse to a website. 2. Website immediately presents a request to show push notifications in a modal. 3. Tab or window cannot be closed using Ctrl+W because a modal is displayed over the window (the request to show push notifications). 3. Website begins playing an auto-play video. I've seen this sort of feature abuse on lots of websites, especially news websites that auto-play a video ad on page load. What is the expected behavior? The window or tab should close using Ctrl+w even if there's a modal displayed. What went wrong? Websites are intentionally causing the push notification dialog to be displayed on page load to increase engagement in video ads. The modal prevents the user from immediately closing the tab upon hearing or seeing the video start playing: The user can't avoid hearing or seeing the first ten seconds or so of the video because it takes additional time to close the tab or window; requiring the user to first close the notification dialog, then close the tab. Please don't say "oh well you can get extensions that block ads or videos" or "well you can globally disable sound in autoplay videos now" because that's not a fix it's a kludge. Did this work before? No Chrome version: 64.0.3282.119 Channel: stable OS Version: 10.0 Flash Version: Shockwave Flash 28.0 r0 I noticed that this specific website developer behavior began shortly after the push notification feature was introduced. It's always a combination of the push notification request and a web page that auto-plays a video.
,
Feb 1 2018
josh.pruitt@ Thanks for the issue. As per the original comment, this is a feature request to close a push notification in a modal using ctrl+w. Hence marking this as Untriaged for further updates from Dev. Thanks..
,
Feb 23 2018
I think it is a feature request to close the whole tab, including the push notification, with ctrl-W.
,
Feb 28 2018
This really annoys me too. I wish pressing ctrl+w still worked when permissions are up :( cc enamel folk
,
Feb 28 2018
This is not a feature request this is a bug report: Developers introduced new functionality which broke previously working hotkeys. So the previously working feature needs fixing to work with the new functionality. Please stop avoiding work and do what you are paid to do. If Google is going to pay to do your laundry for you and provide free meals prepared by an in-house chef the least you could do is to do the work they're paying you for and not just the work you've cherry picked because it's fun.
,
Feb 28 2018
I can reproduce on Linux but not Mac. I'll try a bisect. Re: #5, your tone isn't appropriate for the Chromium project; please take a look at https://chromium.googlesource.com/chromium/src/+/master/CODE_OF_CONDUCT.md
,
Feb 28 2018
Hmm, I thought this was a recent regression, but it doesn't look like it is; it reproduces as far back as Chrome 57. Just to confirm I'm looking at the right thing, these are the repro steps I'm following: 1.) Open https://permission.site in a fresh profile. 2.) Click "Location". 3.) Observe that Ctrl+w does not close the tab. Note that after clicking anywhere in the content area, Ctrl+w does work. Owen and OP, is that the behavior you're reporting?
,
Feb 28 2018
Owen: see #7
,
Feb 28 2018
Yes. That is the behavior I'm seeing. Have seen it for many releases, I don't think it's a regression. If I had to guess, I think it happened when we moved from infobars to bubbles and we just never fixed it...
,
Feb 28 2018
See also issue 319109. This isn't a new bug.
,
Feb 28 2018
,
Mar 1 2018
,
Jun 26 2018
I'm sad that it took a manager marking this bug as a duplicate of a newer report to convince you this is a bug and not a feature request. |
|||||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||||
Comment 1 by krajshree@chromium.org
, Jan 31 2018