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

Issue 758085 link

Starred by 2 users

Issue metadata

Status: Assigned
Owner:
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Linux , Windows , Mac
Pri: 3
Type: Bug-Regression



Sign in to add a comment

Regression: about:blank page is seen when trying to reload the blocked extension page in guest mode

Project Member Reported by keerthan...@techmahindra.com, Aug 23 2017

Issue description

Chrome Version:62.0.3194.0
OS:Ubuntu 14.04, Windows

Test-URL: chrome-extension://pkedcjkdefgpdelpbcmbmeomcjbeemfm/feedback.html

What steps will reproduce the problem?
(1)Launch chrome and navigate to guest mode
(2)Navigate to the above URL and try to reload

Expected:The page should get reloaded
Actual: Instead, about:blank page is seen

This is a Regression issue broken in M-62
Manual Bisect Info:
===================
Good Build:62.0.3190.0
Bad Build: 62.0.3191.0

 
URLActual.ogv
422 KB View Download
URLExpected.ogv
565 KB View Download
Labels: OS-Mac
Status: Untriaged (was: Unconfirmed)
Able to reproduce this issue on Mac OS 10.12.6 using chrome latest dev #62.0.3194.0.
Components: UI>Browser>Navigation
Labels: -Needs-Bisect hasbisect-per-revision
Owner: rdevlin....@chromium.org
Status: Assigned (was: Untriaged)
Bisect Information:
-------------------
You are probably looking for a change made after 495778 (known good), but no later than 495779 (first known bad).

CHANGELOG URL:
--------------
https://chromium.googlesource.com/chromium/src/+log/a9c2e448a2a2f48d9d2b0ec28185ffa4ea263eb3..f1afce25b3f94d8bddec69b08ffbc29b989ad844

@rdevlin.cronin: Could you please check whether this is caused with respect to your change, if not please help us in assigning it to the right owner.

Thanks!!
Cc: alex...@chromium.org nasko@chromium.org
Labels: -Pri-1 -M-62 Pri-3
I don't know if I'd quite call this a regression - both situations are pretty broken.  This just happens because we go through different code paths depending on whether we fork in the renderer, I believe.

Given this happens when trying to visit a nonexistent extension page, I don't think this is super high priority.  I think the real fix here is "coalesce our extension navigation handling and make it more sane."

Sign in to add a comment