mobile page of dlive.tv/ doesn't load properly
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Not tracked)
People
(Reporter: jgraham, Unassigned)
References
(Depends on 1 open bug, )
Details
(Keywords: webcompat:needs-diagnosis)
User Story
platform:android impact:site-broken affects:all diagnosis-team:dom
If one visits the mobile page of https://dlive.tv/ (for instance, in the responsive design mode with a Chrome device and user-agent string selected), the page does not load properly. For whatever reason, as the page loads their scripts try to alter window.location.href
to dlive://dlive.tv
twice in rapid succession:
return a &&
(
window.location.href = e,
window.location.href = e,
setTimeout((function () {
void 0 !== t &&
t()
}), 1500)
),
Commenting out one of those two window.location.href
lines fixes the issue, as Firefox blocks one of them. It ought to be blocking both, which is what Chrome seems to do, and why the page loads on Chrome for Android.
Either way this is a webcompat issue that's breaking a site outright, even if the site seems to be going out of their way to do something ill-conceived.
Comment 1•17 days ago
•
|
||
The broken behavior was gone for a while according to bug 1840731 comment 6 and bug 1840731 comment 7. However, it's back to me when I was reproducing with Firefox (131.0.3) Android on my phone Pixel 4a, today.
Bug 1840731 comment 7 hinted that the buggy pattern with rapid double-redirect seemed to be gone. I didn't seem to find that pattern when I quickly search using devtool Debugger as well. Therefore, I am changing the bug title to reflect the breakage but less about that specific redirect pattern. I think we need diagnosis again.
Comment 2•17 days ago
|
||
I got several errors in console:
- Loading failed for the <script> with source “https://dlive.tv/js/chunk-6ba0e756.10accffa.js”. home:1:1
- Uncaught (in promise) ChunkLoadError: Loading chunk fp failed. (error: https://dlive.tv/js/fp.342c2ed9.js)
Comment 3•17 days ago
|
||
(In reply to Hsin-Yi Tsai (she/her) [:hsinyi] from comment #1)
The broken behavior was gone for a while according to bug 1840731 comment 6 and bug 1840731 comment 7. However, it's back to me when I was reproducing with Firefox (131.0.3) Android on my phone Pixel 4a, today.
However, I have no problems when using Nightly Firefox on Android 133.
Bug 1840731 comment 7 hinted that the buggy pattern with rapid double-redirect seemed to be gone. I didn't seem to find that pattern when I quickly search using devtool Debugger as well. Therefore, I am changing the bug title to reflect the breakage but less about that specific redirect pattern. I think we need diagnosis again.
Comment 4•14 days ago
•
|
||
So..by using mozregression, I am able to isolate a fix happens around Sept 10 fixes this.
By looking at all the commits around that time, I think bug 1911977 fixes this.
Comment 5•14 days ago
|
||
Yeah, I removed the changes from bug 1911977, and this site was back to no-loading again.
Maybe there's still an issue with loading invalid protocol twice
, but I think we can close this bug given this is about dlive.tv not loading.
Description
•