New issue
Advanced search Search tips

Issue 842766 link

Starred by 3 users

Issue metadata

Status: Assigned
Owner:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Android , Windows , Chrome , Mac , Fuchsia
Pri: 3
Type: Feature
Team-Security-UX



Sign in to add a comment

[User Feedback - Stable/Beta] Back to safety button can land on about:blank page

Project Member Reported by craigtumblison@chromium.org, May 14 2018

Issue description

Chrome Version: 66.0.3359.170, 67.0.3396.30
OS Version: OS X 10.13.4

What steps will reproduce the problem?
1. Find a site that throws a safe browsing page (ex. flycapetown.co.za)
2. Navigate to the site from another window, using the "Open Link in New tab" function
3. Click the "Back to safety" button
4. Land on about:blank

What is the expected result?
User is directed to their new tab page, or the tab is auto-closed.


This may be a feature request instead of a bug, but our community experts flagged it as a poor user experience.

It looks like there are three common behaviors for the back to safety button:

Behavior #1: If you open a new tab and paste that site directly, then click "back to safety", you're reverted to the new tab page.

Behavior #2: If you open that site from another site (example: do a Google search for that site and click through, opening in the same tab) and then click "back to safety", you're reverted back to the previous page.

Behavior #3: If you open that site in a new tab from another site (example: do a Google Search for that site, then right-click "open in a new tab" from the result page) and then click "back to safety", you're shown the "about:blank" page in Chrome, as there is no previous history in that tab.

This request is to change the behavior on the third item to either also redirect to the new tab page, or to close the tab (jumping the user back to the tab they were on previously).

Thanks!
 

Comment 1 by vakh@chromium.org, May 14 2018

Cc: carlosil@chromium.org
Components: UI>Browser>Interstitials
Cc: -carlosil@chromium.org
Labels: -Type-Bug OS-Android OS-Chrome OS-Fuchsia OS-Linux OS-Windows Type-Feature
Owner: carlosil@chromium.org
Status: Assigned (was: Unconfirmed)
Looks like this is not SB specific since the same thing happens with SSL interstitials.

This will actually be fixed for free once committed interstitials launch (which should be soon, I'm currently working on giving SB interstitials the committed treatment) as the back navigation in this case will send the user back to the NTP. I'll take this bug in the meantime.
Oh perfect, that sounds like a plan then :)

Appreciate the quick triage and answer!
Labels: SafeBrowsing-Triaged

Sign in to add a comment