Web page title not always updated on same-site navigation
Categories
(Firefox :: Untriaged, defect)
Tracking
()
People
(Reporter: mccr8, Unassigned)
References
Details
(Keywords: regression)
For maybe 5 days now on Nightly, I've noticed that if I navigate from one page to another on a site that the title does not always update properly. I've seen this on Slack, Twitch and Twitter. For instance, on Slack if I am in channel #Foo, and then I click on the channel #Bar, the title sometimes still says #Foo. Same thing on Twitch. For Twitter, it happens when I go from one page to another. I've noticed this on both Windows and OSX.
This might be a variation of bug 1595925, but I figured I'd file it in case it wasn't.
|
Reporter | |
Comment 1•5 years ago
|
||
I'll also note that if you search for open bugs where the summary contains "title", and sort in decreasing bug order, there are around 10 different new intermittent failures that look like they are title related.
|
||
Comment 2•5 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #1)
I'll also note that if you search for open bugs where the summary contains "title", and sort in decreasing bug order, there are around 10 different new intermittent failures that look like they are title related.
Can you link? I see more than the bug limit (500) for a quicksearch of summary:title and so I can't see these.
Solid STR and/or a regression range here would also really help, if it doesn't go away as soon as 1595925 lands.
|
|
Reporter | |
Comment 3•5 years ago
•
|
||
(In reply to :Gijs (he/him) from comment #2)
Can you link? I see more than the bug limit (500) for a quicksearch of
summary:titleand so I can't see these.
I don't remember exactly what my search was before, but adding the keyword "intermittent-failure" seems to turn up the set of bugs I remember: https://bugzilla.mozilla.org/buglist.cgi?keywords= intermittent-failure&keywords_type=allwords&list_id=14993709&short_desc=title&resolution=---&classification=Client Software&classification=Developer Infrastructure&classification=Components&classification=Server Software&classification=Other&query_format=advanced&short_desc_type=allwordssubstr
You'll have to cut and paste that because it seems to confuse Markdown. Also, be sure to sort in decreasing order so the recent bugs are at the top.
Solid STR and/or a regression range here would also really help, if it doesn't go away as soon as 1595925 lands.
Yeah, I'll try to pin it down a bit if it doesn't go away. Switching to another tab for a bit seems to help make it show up, but maybe not always? (I can also reproduce the issue on Discord and Gmail, FWIW.)
|
|
||
Comment 4•5 years ago
|
||
OK, I could reproduce the original issue using youtube (which unlike the other examples doesn't require sign-in). On current m-c (with the fix from bug 1595925), I no longer see this. It'd be cool if you can confirm on today's nightly once that's out. :-)
|
|
||
Comment 5•5 years ago
|
||
(In reply to Andrew McCreight [:mccr8] from comment #3)
(In reply to :Gijs (he/him) from comment #2)
Can you link? I see more than the bug limit (500) for a quicksearch of
summary:titleand so I can't see these.I don't remember exactly what my search was before, but adding the keyword "intermittent-failure" seems to turn up the set of bugs I remember:
https://bugzilla.mozilla.org/buglist.cgi?keywords= intermittent-failure&keywords_type=allwords&list_id=14993709&short_desc=title&resolution=---&classification=Client Software&classification=Developer Infrastructure&classification=Components&classification=Server Software&classification=Other&query_format=advanced&short_desc_type=allwordssubstrYou'll have to cut and paste that because it seems to confuse Markdown. Also, be sure to sort in decreasing order so the recent bugs are at the top.
Thanks. I went through these and marked them as deps where that seemed appropriate. I've closed the ones where it's obvious this is fixed, but most were lower-frequency intermittents than the one I fixed, and there was a tree outage this morning, so I'm gonna wait 24-48 hours for most of them to make sure they're really fixed.
|
|
Reporter | |
Comment 6•5 years ago
|
||
Seems to be working fine for me now. Thanks.
Description
•