ORB rollout breaks loading drivenc.gov
Categories
(Core :: DOM: Networking, defect, P3)
Tracking
()
Tracking | Status | |
---|---|---|
firefox-esr115 | --- | unaffected |
firefox118 | --- | wontfix |
firefox119 | --- | fixed |
firefox120 | --- | fixed |
People
(Reporter: ke5trel, Unassigned)
References
(Regression, )
Details
(Keywords: regression)
Attachments
(2 files)
STR:
- Visit https://drivenc.gov/.
Page fails to load with red screen error message:
• Error with TIMS API.
Does not happen with browser.opaqueResponseBlocking.javascriptValidator = false
or browser.opaqueResponseBlocking = false
.
Works on Chromium.
Regression window:
https://hg.mozilla.org/integration/autoland/pushloghtml?fromchange=98757eed8fe28543f60094e0b131339c71d368b8&tochange=1f3b1e93b0fad0f7ea0300f6ba9741d84223d725
Regressed by Bug 1814478.
Comment 1•1 year ago
|
||
Error with TIMS API
is raised because we block https://eapps.ncdot.gov/services/traffic-prod/v1/incidents/groups
which is a legit block from the OpaqueResponseBlocking perspective.
This is how they detect the blockage and raise the error
function loadScript(e,t,o){
var n=document.getElementsByTagName("script")[0],
a=document.createElement("script");
a.type="text/javascript",a.src=e,o&&(a.onerror=o),n.parentNode.insertBefore(a,n.nextSibling),t&&t()
}
loadScript(
_data.source.base+_data.source.groups,
null,
function(){
initErrors("Error with TIMS API."),
_data.source.error=!0
}
)
Technically speaking, Using <script> tag to load no-cors JSON data is meaningless as they can't read the response. Maybe they use it just to determine whether the service is up? They can probably change it to a different way. So this is more like a site issue.
As being said, we'd like the site to fix it. However in the meantime, we'll prepare a patch as well to fix this from Firefox's side.
Comment 3•1 year ago
|
||
fwiw i no longer see the error on MacOS on the latest nightly after bug 1855838 landed
Comment 4•1 year ago
|
||
:sefeng any further action required here?
See comment 3
Comment 5•1 year ago
|
||
I think we can leave this bug open to see if drivenc.gov wants to update their site because that's a bad pattern.
Though we don't have action items left. I mean if Dennis doesn't think outreach is necessary, we can also close the bug.
Updated•1 year ago
|
Comment 6•1 year ago
•
|
||
Also confirmed it is working in 119.0b7.
Marking 119 and 120 as fixed by bug 1855838.
Will wait for Dennis to close out this bug.
Updated•8 months ago
|
Updated•8 months ago
|
Comment 8•8 months ago
|
||
I tried pinging them multiple times to get a chance to confirm this. I haven't heard back, but we also didn't see a new report about this. Let's assume this is indeed fixed.
Description
•