Description
When opening https://www.l1nieuws.nl/ in a new tab using Microsoft Edge, the page frequently becomes partially unresponsive. The navigation menu no longer responds to clicks and parts of the website stop functioning. Only in the Edge Browser.
The issue does not occur in Google Chrome (same Chromium engine) or Firefox on the same machine.
Steps to reproduce:
Open Microsoft Edge.
Open a new browser tab.
Navigate to https://www.l1nieuws.nl/.
Wait for the advertisements to initialize.
Try using the navigation menu.
Note: The issue is not always reproducible on the first attempt. It may be necessary to close the tab and open the website in a new tab several times before the problem occurs.
Actual result
The page becomes partially unresponsive. The navigation menu no longer reacts to mouse clicks.
The browser console consistently logs:
Booting safeframe for ad-cc1bf465-cc1e-4889-94e7-3815c87b4482-2
Immediately afterwards the following JavaScript exception occurs:
TypeError: n.setAttribute is not a function
The stack trace includes:
Booting safeframe for ad-cc1bf465-cc1e-4889-94e7-3815c87b4482-2
adb2b97.js:2 TypeError: n.setAttribute is not a function
at Array.mi (adb2b97.js:2:59031)
at R (adb2b97.js:2:70408)
at adb2b97.js:2:70631
at R (adb2b97.js:2:71106)
at f.__patch__ (adb2b97.js:2:72277)
at f._update (adb2b97.js:2:48455)
at f.r (adb2b97.js:2:79827)
at t.get (adb2b97.js:2:29739)
at t.run (adb2b97.js:2:30472)
at zr (adb2b97.js:2:32451)
Expected result
The webpage should remain fully responsive after advertisements are initialized.
Additional observations:
- The issue only occurs after opening the website in a new tab.
- Refreshing the page (F5 or Ctrl+F5) does not reproduce the issue. After a refresh, the website works normally.
- The problem is triggered during the initial page load in a new tab.
- Google Chrome: Works correctly on the same machine.
- Mozilla Firefox: Works correctly on the same machine.
- Chrome is allot faster in rendering the webpage
This last point is particularly interesting because Chrome and Edge are based on the same Chromium version, yet only Edge exhibits the problem during the initial navigation. That may help the Edge team narrow down whether the issue is related to an Edge-specific optimization, caching behavior, or the interaction with SafeFrame advertisements.
If anyone on the Edge team has an idea what might be causing this behavior, we'd really appreciate the insight. We've spent quite a bit of time investigating it (HAR captures, performance traces, console logs, and isolating the advertising/SafeFrame interaction), but haven't been able to identify the root cause yet. Our web developer is pulling his hair out over this issue. 🙂
Microsoft Edge | 150.0.4078.48 (Officiële build) (64-bits)
Revisie | 6362dfa84aa4f30c18c60ac12387d02753f37dc6
Chromium-versie | 150.0.7871.47
Description
When opening https://www.l1nieuws.nl/ in a new tab using Microsoft Edge, the page frequently becomes partially unresponsive. The navigation menu no longer responds to clicks and parts of the website stop functioning. Only in the Edge Browser.
The issue does not occur in Google Chrome (same Chromium engine) or Firefox on the same machine.
Steps to reproduce:
Open Microsoft Edge.
Open a new browser tab.
Navigate to https://www.l1nieuws.nl/.
Wait for the advertisements to initialize.
Try using the navigation menu.
Note: The issue is not always reproducible on the first attempt. It may be necessary to close the tab and open the website in a new tab several times before the problem occurs.
Actual result
The page becomes partially unresponsive. The navigation menu no longer reacts to mouse clicks.
The browser console consistently logs:
Booting safeframe for ad-cc1bf465-cc1e-4889-94e7-3815c87b4482-2Immediately afterwards the following JavaScript exception occurs:TypeError: n.setAttribute is not a function
The stack trace includes:
Expected result
The webpage should remain fully responsive after advertisements are initialized.
Additional observations:
This last point is particularly interesting because Chrome and Edge are based on the same Chromium version, yet only Edge exhibits the problem during the initial navigation. That may help the Edge team narrow down whether the issue is related to an Edge-specific optimization, caching behavior, or the interaction with SafeFrame advertisements.
If anyone on the Edge team has an idea what might be causing this behavior, we'd really appreciate the insight. We've spent quite a bit of time investigating it (HAR captures, performance traces, console logs, and isolating the advertising/SafeFrame interaction), but haven't been able to identify the root cause yet. Our web developer is pulling his hair out over this issue. 🙂
Microsoft Edge | 150.0.4078.48 (Officiële build) (64-bits)
Revisie | 6362dfa84aa4f30c18c60ac12387d02753f37dc6
Chromium-versie | 150.0.7871.47