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

Issue 714700 link

Starred by 2 users

Issue metadata

Status: WontFix
Owner:
Closed: Sep 2017
Cc:
Components:
EstimatedDays: ----
NextAction: ----
OS: Android , Mac
Pri: 3
Type: Bug



Sign in to add a comment

omnibox shows about:blank for a long time after new tab opened via target=_blank

Project Member Reported by owe...@chromium.org, Apr 24 2017

Issue description

I've noticed on my Android and OSX device that clicking a link (e.g. an article on FB) that opens a tab results in a tab opening that says about:blank in the omnibox for a number of seconds before the URL appears.

This looks very broken and often on Android I've hit back assuming it's some kind of a bug, but now think it's just a delay.

Looks to me like there's been some regression here, but this begs the question - is there any way we can get the actual URL to show immediately? Why does it sit on about:blank for a while?

(noticed on OSX running 57.0.2987.133)
 

Comment 1 by owe...@chromium.org, Apr 24 2017

Note that this doesn't happen for all links for me, but I've attached a video of it happening on Google Maps. Not sure what conditions trigger it.
lag.mov
1.7 MB Download
Cc: mea...@chromium.org
Components: UI>Browser>Omnibox
+omnibox, cc meacer to think about this

Comment 3 by mea...@chromium.org, Apr 24 2017

Components: UI>Browser>Navigation
Cc: creis@chromium.org
Status: Assigned (was: Untriaged)

Comment 6 by creis@chromium.org, Apr 27 2017

Labels: Needs-Feedback
We started showing the pending URL for cases like this quite a while ago in  issue 9682 .  We have to revert to showing about:blank if the opener window tries to access the new window via script code, since at that point a URL spoof becomes possible (e.g., put fake content under the pending URL).

I don't know if that's what Maps is doing in the video in comment 1, but it's possible.  Oddly, I'm able to repro it in 58.0.3029.68 but not in 60.0.3082.0.  That suggests something recent may have changed to fix it, so maybe it was for a different reason.

owencm@, can you repro in 60.0.3082.0 or newer?
Ping, owencm@, can you repro in 60.0.3082.0 or newer?
Cc: owe...@chromium.org
Ping, owencm@, can you repro in Chrome 60 or later?

Comment 9 by owe...@chromium.org, Sep 24 2017

Status: WontFix (was: Assigned)
Just tried and haven't been able to repro. Will re-open if I see this again.

Thanks!

Sign in to add a comment