Open
Bug 1799980
Opened 3 years ago
Updated 3 months ago
Add an intervention for healow.com
Categories
(Web Compatibility :: Site Reports, defect, P2)
Web Compatibility
Site Reports
Tracking
(Webcompat Priority:P3, Webcompat Score:1)
REOPENED
People
(Reporter: twisniewski, Unassigned)
References
()
Details
(Keywords: webcompat:site-report, webcompat:sitepatch-applied)
User Story
platform:windows,mac,linux,android impact:site-broken configuration:general affects:all branch:release user-impact-score:0
Healow's i18n is a synchronous API, which waits for a synchronous XMLHttpRequest on its first call. But for subsequent calls, it waits in an infinite loop until the XHR has completed. This will never happen in Firefox, as it's stuck in the infinite loop, and the code after the XHR cannot run.
We can work around this by just making sure it doesn't get stuck in that loop, which may trigger the XHR to happen twice due to them disabling caching on those JSON files, but that's a better outcome than getting stuck in an infinite loop (the files are very small).
Comment 1•3 years ago
|
||
This is shipping in Firefox 108 via bug 1776677.
Status: NEW → RESOLVED
Closed: 3 years ago
Resolution: --- → FIXED
| Reporter | ||
Comment 2•1 year ago
|
||
Reopening this one, since we're now tracking the status of webcompat issues with interventions differently.
Status: RESOLVED → VERIFIED
Keywords: webcompat:sitepatch-applied
| Reporter | ||
Updated•1 year ago
|
Status: VERIFIED → REOPENED
Resolution: FIXED → ---
| Reporter | ||
Updated•1 year ago
|
Severity: -- → S2
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: --- → 6
Component: Interventions → Site Reports
Keywords: webcompat:needs-diagnosis,
webcompat:site-report
Priority: -- → P2
Updated•1 year ago
|
Keywords: webcompat:needs-diagnosis
Updated•1 year ago
|
Webcompat Score: 6 → 3
Updated•1 year ago
|
Webcompat Score: 3 → 2
Updated•1 year ago
|
Webcompat Score: 2 → 1
Updated•8 months ago
|
User Story: (updated)
Updated•3 months ago
|
Webcompat Priority: P2 → P3
You need to log in
before you can comment on or make changes to this bug.
Description
•