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

Issue 721138 link

Starred by 10 users

Issue metadata

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



Sign in to add a comment

Repeated alert()/confirm()/prompt() does not give option to "prevent additional dialogs"

Reported by loorong...@gmail.com, May 11 2017

Issue description

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

Example URL:

Steps to reproduce the problem:
1. Open developer tools
2. Type for (var i = 0; i < 10; i++) alert() and run
3. Keep clicking [OK]
4. Repeat step 2 and 3 with confirm() and prompt()

What is the expected behavior?
After 3rd dialog appears, an option to "prevent additional dialogs" should be given.

What went wrong?
No option to "prevent additional dialogs"

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? Yes 

Does this work in other browsers? Yes

Chrome version: 58.0.3029.96  Channel: stable
OS Version: 10.0
Flash Version: 

Chrome Forum thread: https://productforums.google.com/forum/#!topic/chrome/drS39waj6ik
 
> What is the expected behavior?
> After 3rd dialog appears, an option to "prevent additional dialogs" should be given.

I think the checkbox appeared on a 2nd dialog box already, not 3rd.
Labels: Needs-Triage-M58

Comment 3 by hdodda@chromium.org, May 12 2017

Cc: hdodda@chromium.org
Labels: -Needs-Triage-M58 M-60 OS-Linux OS-Mac
Status: Untriaged (was: Unconfirmed)
Tested the issue on Windows 7 , Mac os 10.12.3 and ubuntu 14.04 using chrome M58 #58.0.3029.110 and M60 #60.0.3097.0 and issuw is reproduced.

Issue is broken in M57 and is a regression issue.

Good Build : 57.0.2986.0 
Bad Build : 57.0.2987.0 

Unable to find suspect using per-revision bisect , as all the builds invoked are good builds and hence providing the manual changelog.

Manual ChangeLog :

https://chromium.googlesource.com/chromium/src/+log/57.0.2986.0..57.0.2987.0?pretty=fuller&n=10000

@Could someone help us in finding the suspect from the above changelog and assigning it to the concern owner.

Thanks!

Comment 4 by bokan@chromium.org, May 16 2017

Components: -Blink Blink>WindowDialog

Comment 5 by a...@chromium.org, Jun 27 2017

Labels: alert-activation
Status: WontFix (was: Untriaged)
This is intentional.

If a page is abusing alerts by spamming the user with them, just click the close button on the tab.
I am against closing this as WontFix. That is bad intention. A feature was removed. What if I want to continue read the page?
I agree that this IS an issue.

How is it intentional to ALLOW the spamming to occur?
This bug makes it possible for a page to spam dialogs with no way for the user to stop them without closing the tab.

If the user wants to view this page then it's impossible in Chrome with this bug intact.
Btw I was using this "feature" for development of hybrid mobile applications -
 to get rid of repeated Apache Cordova JavaScript alerts when debugging JavaScript in regular desktop Chrome browser. This way is mostly more convenient than debugging via mobile Chromium (actually native Android WebView that works with chrome://inspect/#devices).

Sign in to add a comment