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

Issue 682855 link

Starred by 1 user
Status: Duplicate
Merged: issue 629964
Owner: ----
Closed: Jan 2017
Cc:
a...@chromium.org
pinkerton@chromium.org
█ rpop@chromium.org
Components:
EstimatedDays: ----
NextAction: ----
OS: Mac
Pri: 3
Type: Bug



Sign in to add a comment

Web page hijacks Chrome and won't allow normal quit

Project Member Reported by mdw@chromium.org, Jan 19 2017 
Chrome Version: 55.0.2883.95
OS: Mac OS X

While browsing the web, a friend visited a site that redirected them to a page on
http://mithai.ga. This caused several bad things to happen:
  - A JS alert dialog popped up claiming the computer was infected with viruses
  - The tab could not be closed (presumably because of the JS alert window?)
  - The user could not quit Chrome -- see second attached screenshot. The Quit menu item is grayed out and "Warn before quitting" is shown.
  
What steps will reproduce the problem?
(1) Visit http://mergeboutique.com
(2) Get redirected to http://mithai.ga/5764/c/your-computer-is-locked-call-us-at-tollfreenow--1-888-403-6867-your-computer-is-locked-call-us-at-tollfreenow--1-888-403-6867

(note - this does not always happen, probably depends on a specific ad being shown on the original page).

The bug is simply that a web page should never be able to hijack Chrome in this way.
2017-01-19 (2).jpg
990 KB View Download
2017-01-19.jpg
611 KB View Download

Comment 1 by rpop@chromium.org, Jan 20 2017

Cc: a...@chromium.org
Avi, thoughts?

Comment 2 by a...@chromium.org, Jan 20 2017

Status: WontFix (was: Untriaged)
"Quit" is disabled because an alert is on the screen.

This will be improved with my dialogs work, but this unfortunately works as designed for now.

Comment 3 by mdw@chromium.org, Jan 31 2017

Status: Assigned (was: WontFix)
I'm unsatisfied with the resolution here. If there is work that is underway to address this issue, even partially, this bug should be duped against that one so we can track progress on it. If we are not actively working on fixing this problem, I'd argue that we should be.

Comment 4 by a...@chromium.org, Jan 31 2017

Mergedinto: 629964
Status: Duplicate (was: Assigned)
►

Sign in to add a comment