Closed Bug 2045087 Opened 2 months ago Closed 2 months ago

sfgate article causes tab to hang

Categories

(Web Compatibility :: Site Reports, defect, P1)

Product:
Web Compatibility
Component:
Site Reports
Type:
defect

Tracking

(Webcompat Priority:P1, Webcompat Score:9, firefox-esr140 unaffected, firefox151 unaffected, firefox152 disabled, firefox153 fixed)

Status:
VERIFIED FIXED
Project Flags:
Webcompat Priority P1
Webcompat Score 9
Tracking Flags:
Tracking Status
firefox-esr140 --- unaffected
firefox151 --- unaffected
firefox152 --- disabled
firefox153 --- fixed

People

(Reporter: bradwerth, Unassigned)

References

(Regression,
URL
)

Details

(Keywords: regression, webcompat:needs-diagnosis, webcompat:site-report, Whiteboard: [webcompat:sightline][webcompat:core])

User Story

user-impact-score:2000
platform:windows,mac,linux,android
impact:site-broken
configuration:general
affects:all
branch:release
diagnosis-team:performance

https://www.sfgate.com/bayarea/article/siskiyou-wildlife-crossing-22290254.php

Tab never finishes loading, page content missing, tab becomes unresponsive.

Profile: https://share.firefox.dev/4xeC3ZO

User Story: (updated)
Webcompat Priority: --- → P3
Webcompat Score: --- → 1

Even the front page is janking for me. The profile is very purple, so let's have the layout team take a look.

URL: https://www.sfgate.com/bayarea/articl...
Severity: -- → S2
User Story: (updated)
Webcompat Priority: P3 → P1
Webcompat Score: 1 → 9
Keywords: webcompat:needs-diagnosis, webcompat:site-report
Priority: -- → P1
Whiteboard: [webcompat:sightline][webcompat:core]
User Story: (updated)

Looks like a regression. I'm getting a regression window

User Story: (updated)

I confirmed that running with dom.script_loader.experimental.navigation_cache = false fixes the problem.

Flags: needinfo?(arai.unmht)

Set release status flags based on info from the regressing bug 2027803

status-firefox151: --- → unaffected
status-firefox152: --- → affected
status-firefox153: --- → affected
status-firefox-esr140: --- → unaffected

Thank you for reporting.
Looks like a dupe of bug 2042605, but I'll leave this opened given this bug is filed under different component.

I've asked for the backout for bug 2027803 patch.

Flags: needinfo?(arai.unmht)

posted the details in bug 2042605 comment #18.

It's a bug in linkedin's google tag manager template, which is already solved upstream.
https://github.com/linkedin/linkedin-gtm-community-template/blob/b27413acdce0edfd21b46e45f79b147f46c78cea/template.tpl#L210-L216
https://github.com/linkedin/linkedin-gtm-community-template/commit/d6d31ee6f8880ffd8037e4aea7146ccd7cbba27b

The website's gtm.js contains outdated version of the template.
Updating the code in the website's side will solve the issue.

We'll also look into applying some workaround in the ScriptLoader's side, given the outdated version could to be widely used.
At least there are already 2 websites confirmed (this bug, and bug 2044629)

See Also: → 2042605

This was fixed by backing out bug 2027803

Status: NEW → RESOLVED
Closed: 2 months ago
Resolution: --- → FIXED

Verified, the issue no longer reproduces.

Tested with:

  • Browser / Version: Firefox 152.0-candidate build 1
  • Operating System: Windows 10
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.