New issue
Advanced search Search tips

Issue 873096 link

Starred by 7 users

Issue metadata

Status: Untriaged
Owner: ----
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows
Pri: 2
Type: Bug



Sign in to add a comment

If you refresh with a JavaScript alert on screen, it causes you not to be able to type in any text input area.

Reported by skyeever...@gmail.com, Aug 10

Issue description

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

Example URL:
https://www.google.ca/

Steps to reproduce the problem:
1. Navigate to any web page with a text input.
2. Type "javascript:alert();" into the URL bar.
3. Immediately click refresh.
4. Try typing into an input on the page.

What is the expected behavior?
You should be able to refresh the page and type in any place that allows text input.

What went wrong?
JavaScript alert is doing funky stuff and not allowing you to be able to focus on a text input/type after refreshing the page.

Does it occur on multiple sites: Yes

Is it a problem with a plugin? No 

Did this work before? No 

Does this work in other browsers? Yes

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

In previous versions of chrome you weren't even allowed to refresh the page with a JavaScript alert displayed.
 
javascript:alert(); needs to be typed without quotes, in case that wasn't implied.
It won't let you type in an input after refreshing with the alert on the page.
Labels: Needs-Triage-M68
Components: -Blink Blink>WindowDialog
Cc: susan.boorgula@chromium.org
Labels: Triaged-ET Needs-Feedback
skyeeverestpawpatrol@ Thanks for the issue.

Tested this issue on Windows 10 on the reported version 68.0.3440.106 and the latest Canary 70.0.3522.0 and unable to reproduce the issue by following the below steps.

1. launched Chrome and entered javascript:alert(); in the omnibox.
2. Can see the javascript alert on the screen.
3. Hit the refresh button and clicked on the omnibox and could enter input in to the omnibox without any issues.
Attached is the screen cast for reference.

Request you to check and confirm if anything is missed from our end in triaging the issue.

Also request you to retry the issue on a new chrome profile without any flags/extensions and update the thread with the observations.

Thanks..
873096.mp4
506 KB View Download
You did it wrong. It is not the URL bar that is the problem
Google - Google Chrome 8_14_2018 9_58_05 AM.mp4
18.2 MB Download
Project Member

Comment 7 by sheriffbot@chromium.org, Aug 14

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
Also tested in latest canary build and it works there as well.
Labels: Target-70 M-70 FoundIn-70 OS-Linux
Status: Untriaged (was: Unconfirmed)
skyeeverestpawpatrol@ Thanks for the update.

Able to reproduce this issue on Windows 10 and Ubuntu 17.10 on the reported version 68.0.3440.106 and the latest Canary 70.0.3524.0 as per comment #6.
Issue is not observed on Mac OS 10.13.3.

This is a Non-Regression issue as this behavior is observed from M-60 chrome builds.
Hence marking this as Untriaged for further updates from Dev.

Thanks..
Components: Blink>JavaScript
Adding javascript component.

(Yes, I too would hope that reload would clobber all state about modal dialogs.  I guess it doesn't.)
Components: -Blink>JavaScript
That is not really JS VM related. I guess Blink>WindowDialog seems to be about right.

Sign in to add a comment