www.catsa-acsta.gc.ca - Dark overlay is present after browsing the page
Categories
(Web Compatibility :: Site Reports, defect, P2)
Tracking
(Webcompat Score:5, Webcompat Priority:P2, firefox134 affected, firefox135 affected, firefox136 affected)
People
(Reporter: rbucata, Unassigned)
References
(Depends on 1 open bug, )
Details
(Keywords: webcompat:platform-bug, webcompat:site-report, Whiteboard: [webcompat-source:web-bugs])
User Story
platform:android impact:site-broken configuration:general affects:some branch:release diagnosis-team:dom user-impact-score:150
Attachments
(4 files)
Environment:
Operating system: Android 14
Firefox version: Firefox Mobile 134.0
Steps to reproduce:
- Navigate to: https://www.catsa-acsta.gc.ca/en/what-can-bring/liquids-non-solid-food-personal-items
- Browser the page for a while and observe
no idea what the overlay was supposed to be.
Expected Behavior:
A survey pop-up is triggered
Actual Behavior:
Dark overlay is present
Notes:
- Reproduces regardless of the status of ETP
- Reproduces in firefox-nightly, and firefox-release
- Does not reproduce in chrome
- Refreshing the page solves the issue
Created from https://github.com/webcompat/web-bugs/issues/146335
Reporter | ||
Comment 1•15 days ago
|
||
Reporter | ||
Updated•15 days ago
|
Comment 2•15 days ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Updated•14 days ago
|
Comment 3•12 days ago
|
||
I can reproduce, using responsive design mode in Firefox Nightly on desktop.
The overlay here is a fixed-position iframe with a semitransparent background:
width: 100%;
height: 100%;
position: fixed;
background: rgba(0, 0, 0, 0.8);
top: 0px;
bottom: 0px;
In Firefox Nightly, this iframe is empty. In Chrome, it's got the "Thank you for visiting [etc]" content in its <body>.
Firefox has this in the web console:
Loading failed for the <script> with source “https://www.catsa-acsta.gc.ca/sites/default/files/google_tag/gtm_website_2024/google_tag.script.js?som8nf”. liquids-non-solid-food-personal-items:27:98
Uncaught TypeError: can't access property "insertBefore", y.parentNode is null
injectJs wet-boew.js:1972
m wet-boew.js:1972
wet-boew.min.js:8:30270
injectJs wet-boew.js:1972
m wet-boew.js:1972
Cookie “AWSALB” has been rejected because it is foreign and does not have the “Partitioned“ attribute. checkSurveyValidity
Cookie “AWSALBCORS” has been rejected because it is foreign and does not have the “Partitioned“ attribute. checkSurveyValidity
Cookie “PHPSESSID” has been rejected because it is foreign and does not have the “Partitioned“ attribute. checkSurveyValidity
The script from “https://surveys-sondages.catsa-acsta.ca//projects/checkSurveyValidity?jsonp=checkSurveyCookie&id=6066662” was loaded even though its MIME type (“text/html”) is not a valid JavaScript MIME type. liquids-non-solid-food-personal-items
Cookie “AWSALB” has been rejected because it is foreign and does not have the “Partitioned“ attribute. checkSurveyValidity
Cookie “AWSALBCORS” has been rejected because it is foreign and does not have the “Partitioned“ attribute. checkSurveyValidity
Cookie “PHPSESSID” has been rejected because it is foreign and does not have the “Partitioned“ attribute. checkSurveyValidity
Probably that insertBefore
error is the most relevant one here.
Comment 4•12 days ago
|
||
(In reply to Daniel Holbert [:dholbert] from comment #3)
Probably that
insertBefore
error is the most relevant one here.
Aha, no, that Uncaught TypeError: can't access property "insertBefore", y.parentNode is null
thing is actually an issue with my BitWarden password extension; but it doesn't seem to be related to the bug here. (It happens at pageload, long before this overlay appears; and I still see this bug even in a fresh profile without that extension & where that particular error doesn't show up.)
No exceptions or logging appears in devtools at the moment that this blank iframe pops up in Firefox, unfortunately.
Comment 5•12 days ago
|
||
Here's a reduced testcase, with an abbreviated version of the function that the site here uses to create the iframe, which is popupview_fn
in https://www.catsa-acsta.gc.ca/themes/custom/catsa/js/popup.js?som8nf
Comment 6•12 days ago
|
||
Comment 7•12 days ago
|
||
Here's a reference case for reduced tescase 2, where I've moved the innerHTML assignment to a setTimeout(...,0) callback. That's sufficient to get things working.
So presumably the iframe here has some work that it queues up as part of getting created; and so any synchronous edits to its DOM right after it's created will get stomped on.
Comment 8•12 days ago
•
|
||
smaug/henri, see the attached testcases (particularly reduced testcase 2 vs. reference case 2) - do you know if there's a known bug on our behavior-difference there vs. Chrome?
Comment 9•6 days ago
|
||
This what https://bugzilla.mozilla.org/show_bug.cgi?id=543435 is about.
Updated•6 days ago
|
Updated•6 days ago
|
Description
•