1570505 - tab and location bar get out of sync when a redirect times out

Status: RESOLVED INVALID

(Firefox :: Tabbed Browser, defect, P3)

Description

[Dietrich Ayala (:dietrich)]

Attachment: Screen Shot 2019-07-31 at 3.03.20 PM.png

70.0a1 (2019-07-29) (64-bit) Mac OS X

I see this which clicking on Twitter short urls sometimes (t.co) that point to a URL that times out.

See screenshot. I clicked a link in Tweetdeck which opened the t.co URL in a new tab.

You can see that the tab title shows the redirected-to URL, while the location bar shows the redirect-from URL.

Comment 1

[Dietrich Ayala (:dietrich)]

Redirect from: https://t.co/WdfEKYNHkG

Redirect to: https://ipfs.io/ipfs/QmfTGcRKCumBU9LZ7caYoQKmxeLHv943q7V2FTg7R9fYTE/registry/

Comment 2

[BugBot [:suhaib / :marco/ :calixte]]

The priority flag is not set for this bug.
:dao, could you have a look please?

For more information, please visit auto_nag documentation.

Comment 3

[Dão Gottwald [:dao]]

P3 assuming this isn't a regression (which I'm not sure of yet).

Comment 4

[Cristian Baica [:cbaica], Release Desktop QA]

I've tried reproducing this on windows as well as on macOS but without any success. In all the attempts I didn't receive a timeout when accessing the short link that was provided.

@Dietrich, does this still occur on the latest nightly?

Comment 5

[Pablo]

Tested with: Firefox nightly 70.0a1 build: 20190729095501

I tried to reproduce the issue on windows 10 64bit and also on MacOs 10.14
When i access the short link it does not give me a timeout. It just stays loading with a white screen.

Can you please confirm that you still experience the issue in the latest Firefox Nightly version?

Thanks
Pablo

Comment 6

[Dietrich Ayala (:dietrich)]

I think you've not quite understood the bug - the issue is the disconnect between tab title and location bar.

I just clicked on the t.co link and saw the exact behavior as reported in comment #0.

The redirect clearly completed at the network layer, as demonstrated by the tab title updating correctly.

The location bar UI code isn't listening to or receiving the event, or isn't wired up to it correctly or something like that.

Dao understands what is happening here - there's no need to ask me for re-verification.

Comment 7

[Patrick (he/him)]

I'm getting the same behaviour in Chrome - is this possibly a site-specific issue? Also, this does not appear to be a regression - I am able to reproduce it as far back as 67 on Windows.

Comment 8

[BugBot [:suhaib / :marco/ :calixte]]

Bugbug thinks this bug is a regression, but please revert this change in case of error.

Comment 9

[Dietrich Ayala (:dietrich)]

YES! Good thinking @mpj.5!

This is not a regular HTTP redirect. The t.co URL is a page which sets the HTML title to the URL of the redirect target.

So when the target takes a long time, it looks like the tab title and url bar are disconnected.

-> INVALID