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

Issue 892953 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Last visit > 30 days ago
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Update MDN to say that dialogs don't necessarily wait or aren't even necessarily shown

Reported by goldingd...@gmail.com, Oct 7

Issue description

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

Steps to reproduce the problem:
1. Create a page which does: window.prompt(); location.reload();
2. Open the page.
3. View another tab.

What is the expected behavior?
The prompt I assume should be a blocking script, so the prompt should wait even in the background.

What went wrong?
The script does not seem to block in the background. This can be seen by the endless refreshing shown on the background tab.

Did this work before? No 

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

In normal development this kind of scenario would usually be avoided, but any kind of function that repeats such as reloading the page or sending data somewhere based on the prompt value would be affected.

*I am not sure how much this is expected behaviour.
 
This is intended, see  issue 629964 .
Labels: Needs-Triage-M69
I would just like to note that I fully understand why alerts would want to be dismissed in the background, but when reading sites such as MDN, they say that prompt, etc. are blocking.

The problem could also be quite extreme. For example, it is possible that a site has set to send data from the prompt and retry if empty leading to endless sending in the background and the user might not notice because that tab is not visible.
Cc: viswa.karala@chromium.org
Labels: Triaged-ET Needs-Feedback
Thanks for filing the issue!

@Reporter: Could you please provide sample Test File/URL that reproduces the issue which helps in further triaging it and if possible please provide screencast of the issue which help in better understanding it.

Thanks!
Try out the attachment to get an idea of what could happen if opened in a background tab.
index.html
1.5 KB View Download
Project Member

Comment 6 by sheriffbot@chromium.org, Oct 9

Labels: -Needs-Feedback
Thank you for providing more feedback. Adding the requester to the cc list.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Cc: jmedley@chromium.org a...@chromium.org
Components: Blink>WindowDialog
I think this is WAI. But the item here is that MDN text should be updated. Since this was done a while ago I'm not sure who should update MDN. Adding avi@ who did the work, and jmedley@ who helps contribute to MDN.
This is WAI.

jmedley@: Can we update MDN to say that confirm (and prompt and alert) will not necessarily wait or necessarily even be shown?
Owner: jmedley@chromium.org
Status: Assigned (was: Unconfirmed)
Summary: Update MDN to say that dialogs don't necessarily wait or aren't even necessarily shown (was: window.prompt in background doesn't wait)

Sign in to add a comment