Open Bug 1956063 Opened 1 month ago Updated 23 days ago

www.soundersfc.com - Content missing on several categories/sections of the page

Categories

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

Unspecified
All

Tracking

(Webcompat Score:5, Webcompat Priority:P2, firefox136 affected, firefox137 affected, firefox138 affected)

Webcompat Score 5
Webcompat Priority P2
Tracking Status
firefox136 --- affected
firefox137 --- affected
firefox138 --- affected

People

(Reporter: ctanase, Unassigned)

References

(Depends on 1 open bug, )

Details

(Keywords: webcompat:needs-sitepatch, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])

User Story

platform:windows,mac,linux,android
impact:workflow-broken
configuration:general
affects:all
branch:release
diagnosis-team:webcompat
user-impact-score:160

Attachments

(1 file)

Environment:
Operating system: Android 12/Windows 10
Firefox version: Firefox Mobile 136.0/138

Steps to reproduce:

  1. Go to https://www.soundersfc.com/schedule
  2. Observe the page.

Expected Behavior:
Game schedule is shown.

Actual Behavior:
The game schedule is missing, page content is blank.

Notes:

  • Reproducible on both Android and Desktop (Windows 10)
  • Reproduces regardless of the status of ETP
  • Reproduces in firefox-nightly, and firefox-release
  • Does not reproduce in chrome

Created from https://github.com/webcompat/web-bugs/issues/150088

Attached image image.png

Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.

FWIW, it seems to work if install uBlock Origin (with its default settings).

Webcompat Score: --- → 1
Severity: -- → S2
User Story: (updated)
Webcompat Priority: --- → P2
Webcompat Score: 1 → 5
Priority: -- → P2

This is also reproducible on Desktop (in RDM as well as in just a normal browser window). Under "Matches|Standings|..." at the top left, there's supposed to be a button labeled 2025, and a menu labeled "All Competitions", but in Firefox that whole area is blank.

I do see some uncaught errors in Error Console that don't show up when I test in Chrome -- those might be relevant. They all look like this (with a series of different chunk numbers and numeric JS filenames):

Uncaught (in promise) ChunkLoadError: Loading chunk 8521 failed.
(missing: https://www.soundersfc.com/assets/js/8521.js?_t=351b979f1dd8c6508215)
    j jsonp chunk loading:27
    e ensure chunk:6
    e ensure chunk:5
    <anonymous> base.js:7
    <anonymous> base.js:2
    <anonymous> base.js:2
jsonp chunk loading:27:17

bug 1839053 has the same "Loading chunk [...] failed", for what it's worth. --> putting this in diagnosis-team:networking to see if this breakage is the same issue as was discussed there.

User Story: (updated)
See Also: → 1839053

Do you think this is the same as bug 1839053? And do we have a way forward on that bug?

Flags: needinfo?(valentin.gosu)

Seems related, but this site doesn't seem to be built with nuxt2
I'm also seeing some issues with webpack and the way sourcemaps are defined:
webpack://mlssoccer/netcore/webpack/runtime/jsonp%20chunk%20loading

I find it funny that running ublock will block https://cookie-cdn.cookiepro.com/consent/d107bbf3-79fc-412c-897c-98d0bb8d65a8/OtAutoBlock.js and fix this, but I'm not sure whether the bug is coming from that script.

Flags: needinfo?(valentin.gosu)

Note that I don't see any failed network requests in the console, so I assume this is a site bug.

(In reply to Valentin Gosu [:valentin] (he/him) from comment #7)

I find it funny that running ublock will block https://cookie-cdn.cookiepro.com/consent/d107bbf3-79fc-412c-897c-98d0bb8d65a8/OtAutoBlock.js and fix this, but I'm not sure whether the bug is coming from that script.

It is! That script seems to be OneTrust Cookie Auto-Blocking and it contains code that blocks some scripts (that's where the ChunkLoadErrors are coming from). It does so by adding a beforescriptexecute event handler that calls e.preventDefault(). That event is only implemented in Firefox. If I override Element.prototype.addEventHandler to ignore handlers for the beforescriptexecute event then the site works.
My guess is that this is caused by a misconfiguration of the blocking feature for that site which only causes an issue in Firefox because the other browsers don't implement beforescriptexecute.
I think we could fix this with a site patch.

User Story: (updated)

This is fixed in the latest Nightly, probably due to Bug 1954685.

See Also: → 1954685

I've verified that it was fixed by Bug 1954685: the site works if and only if the dom.events.script_execute.enabled pref is set to false.

Depends on: 1584269
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: