avlguest.justice.nsw.gov.au - The page is stuck in a loading state
Categories
(Web Compatibility :: Site Reports, defect, P3)
Tracking
(Webcompat Priority:P3, Webcompat Score:1, firefox144 affected, firefox145 affected, firefox146 affected)
People
(Reporter: rbucata, Assigned: twisniewski)
References
()
Details
(4 keywords, Whiteboard: [webcompat-source:web-bugs])
User Story
user-impact-score:0 platform:windows,mac impact:site-broken configuration:general affects:all branch:release diagnosis-team:webcompat
Attachments
(2 files)
Environment:
Operating system: Windows 10
Firefox version: Firefox 143.0
Steps to reproduce:
- Navigate to: https://avlguest.justice.nsw.gov.au/call/test.link
- Observe
Expected Behavior:
Page loads
Actual Behavior:
Page stuck in loading state
Notes:
- 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/183237
| Reporter | ||
Updated•28 days ago
|
| Reporter | ||
Comment 1•28 days ago
|
||
| Reporter | ||
Comment 2•28 days ago
|
||
The page might not load because the extension is meant for Chrome, but I am not sure if this is the right behaviour or not.
Comment 3•28 days ago
|
||
Since nightly and release are affected, beta will likely be affected too.
For more information, please visit BugBot documentation.
Comment 4•28 days ago
|
||
Console shows:
Uncaught ReferenceError: mozRTCPeerConnection is not defined
<anonymous> jabberguest-web.js:7957
execCb jabberguest-web.js:29
check jabberguest-web.js:18
enable jabberguest-web.js:23
enable jabberguest-web.js:27
enable jabberguest-web.js:23
v jabberguest-web.js:8
z jabberguest-web.js:7
enable jabberguest-web.js:22
enable jabberguest-web.js:27
enable jabberguest-web.js:23
v jabberguest-web.js:8
z jabberguest-web.js:7
enable jabberguest-web.js:22
enable jabberguest-web.js:27
enable jabberguest-web.js:23
v jabberguest-web.js:8
z jabberguest-web.js:7
enable jabberguest-web.js:22
enable jabberguest-web.js:27
enable jabberguest-web.js:23
v jabberguest-web.js:8
z jabberguest-web.js:7
enable jabberguest-web.js:22
init jabberguest-web.js:17
d jabberguest-web.js:26
setTimeout handler*h.nextTick< jabberguest-web.js:31
d jabberguest-web.js:26
requirejs jabberguest-web.js:31
main jabberguest-web.js:18678
<anonymous> jabberguest-web.js:18660
execCb jabberguest-web.js:29
check jabberguest-web.js:18
enable jabberguest-web.js:23
init jabberguest-web.js:17
d jabberguest-web.js:26
setTimeout handler*h.nextTick< jabberguest-web.js:31
d jabberguest-web.js:26
requirejs jabberguest-web.js:31
<anonymous> jabberguest-web.js:18654
<anonymous> jabberguest-web.js:19020
jabberguest-web-min.js:45:6038
Comment 5•28 days ago
|
||
Updated•27 days ago
|
Comment 6•24 days ago
|
||
Simple Chrome spoof doesn't work, so they're doing something else to detect Firefox. Realistically, we should just contact them and ask them to update their stuff.
| Assignee | ||
Comment 7•23 days ago
|
||
For now we might as well make a simple intervention to shim the three moz-prefixed properties that I see them expecting to be present (mozRTCPeerConnection, mozRTCSessionDescription, and mozRTCIceCandidate), which bug 1531812 removed. That at least seems to get us to the final page which requests installing a Firefox add-on (as it requests a Chrome add-on when loaded in Chrome).
| Assignee | ||
Comment 8•22 days ago
|
||
Updated•22 days ago
|
Comment 10•21 days ago
|
||
| bugherder | ||
| Assignee | ||
Updated•21 days ago
|
Updated•20 days ago
|
Description
•