New issue
Advanced search Search tips

Issue 654214 link

Starred by 1 user

Issue metadata

Status: Archived
Owner: ----
Closed: Feb 2018
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Windows
Pri: 2
Type: Bug



Sign in to add a comment

Dialog box is invisible

Reported by dylankey...@gmail.com, Oct 8 2016

Issue description

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

Steps to reproduce the problem:
1. Go to http://www.w3schools.com/js/tryit.asp?filename=tryjs_alert (or any site that has a JS pop up) & click 'Try it'.

What is the expected behavior?
That you're able to see the dialog box and dismiss it - by confirming or denying it.

What went wrong?
While the box appears - it's invisible. This blocks all the content behind it and makes it unable to continue browsing the website and anything on the Chrome toolbar. Clicking Space or ESC closes the box, and you're able to continue.

Did this work before? Yes 52

Chrome version: 53.0.2785.143  Channel: stable
OS Version: 10.0
Flash Version: Shockwave Flash 23.0 r0
 
Cc: kkaluri@chromium.org
Labels: Needs-Feedback
Unable to reproduce this issue, we tested this issue on windows 10 machine with chrome version stable 53.0.2785.143. Observed that alert box is displaying properly 

please look into screencast
Could you please try this scenario with clean profile without using any apps or extensions in your browser.

Issue-654214.mp4
464 KB View Download
Thanks for looking into it, kklarui.

After testing - new user profile, no extensions/apps, Vivaldi (which runs on the source code) - it appears to be a W10 related issue. What I find strange is that after resetting W10 completely, the issue still persists. 

After searching around on Google, I couldn't find any related issues. Since it's not related to Chromium (directly), you can probably close this issue.

I couldn't see a way to edit my post, so sorry for the double comment.

I figured that I should give running W10 in safe mode a try (can't believe I didn't try this before...) and it works fine.

Any ideas what could cause this behavior? 
Project Member

Comment 4 by sheriffbot@chromium.org, Oct 20 2016

Labels: -Needs-Feedback Needs-Review
Owner: kkaluri@chromium.org
Thank you for providing more feedback. Adding requester "kkaluri@chromium.org" for another review and adding "Needs-Review" label for tracking.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
Labels: -Needs-Review Needs-Feedback
Owner: ----
dylankeylogger1@ Could you please try this scenario on latest stable version #55.0.2883.87 and let us know your observations.
Project Member

Comment 6 by sheriffbot@chromium.org, Feb 14 2018

Status: Archived (was: Unconfirmed)
Issue has not been modified or commented on in the last 365 days, please re-open or file a new bug if this is still an issue.

For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot

Sign in to add a comment