Open Bug 1901780 Opened 4 months ago Updated 3 months ago

www.vanbreda-health.be - The page never fully load

Categories

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

Desktop
Windows 10

Tracking

(firefox130 fixed)

REOPENED
Tracking Status
firefox130 --- fixed

People

(Reporter: ksenia, Assigned: twisniewski)

References

(Depends on 1 open bug, )

Details

(Keywords: webcompat:needs-contact, webcompat:sitepatch-applied, Whiteboard: [webcompat-source:web-bugs])

User Story

platform:windows,mac,linux,android
impact:site-broken
configuration:general
affects:all

Attachments

(1 file)

Environment:
Operating system: Windows 10
Firefox version: Firefox 103.0

Steps to reproduce:
Start firefox
enter the URL
wait and wait and wait...

Actual Behavior:
The page/form does not load; firefox hangs

Notes:

  • Reproduces regardless of the status of ETP
  • Does not reproduce in Firefox Nightly, Firefox Release, and Chrome

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

Severity: -- → S2
User Story: (updated)
Depends on: 1901778
Priority: P2 → P3

From https://github.com/webcompat/web-bugs/issues/108406#issuecomment-1218553265:

This is caused by their site doing this:

//TODO: this is ugly code but fix to make the ugly has-content - stupid way of styling - concept work inside modals.....
$("body").bind("DOMSubtreeModified", function () {
    /* snip some stuff */
    $(".type-address").removeClass("has-content");
    $("select").closest("li").addClass("has-content");
    $(".type-address").removeClass("has-content");
    $(".type-address").find("select").parent().addClass("has-content");
    $(".clear-multi").parent().find("label").addClass("multi-label");
});

And well, they're not wrong that it's ugly. Chrome seems to handle it more gracefully, but mutation events are deprecated for precisely this reason: they perform super poorly (even on Chrome).

I wonder why they felt the need to do this instead of using Mutation Observers instead.. we should reach out to them and find out. I can't even tell from their code why it's needed after it's called once (maybe they can even just remove the listener after the first time it's handled?)

Diagnosis is already done by Tom. The site has changed and the slowliness only present when selecting radio button options, at least on the page mentioned in the report

Assignee: nobody → twisniewski
Status: NEW → ASSIGNED
Pushed by twisniewski@mozilla.com: https://hg.mozilla.org/integration/autoland/rev/dde74e815a03 disable legacy DOM Mutation Events on vanbreda-health.be to fix performance issues; r=ksenia,webcompat-reviewers
Status: ASSIGNED → RESOLVED
Closed: 3 months ago
Resolution: --- → FIXED

Re-opening, as this is site-patched, not actually fixed.

Status: RESOLVED → REOPENED
Resolution: FIXED → ---
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: