Windows-Admin-Center-Ideas-and-Feedback
Windows-Admin-Center-Ideas-and-Feedback copied to clipboard
MicrosoftDocs
[WAC] - 2306 fails to load properly in Firefox
Gateway Version: 2306
To Reproduce Steps to reproduce the behavior:
- Navigate to gateway using recent Firefox (tested in 116.0.2)
Expected behavior Gateway loads
Screenshots & Additional context
Loading screen gets stuck on "Gathering environment info—this may take a few moments." Nothing in the browser console is of any use to me in understanding what has gone wrong.
Hi,
Unfortunately Firefox is not supported and the supported browsers are Edge or Chrome.
Kind regards!
The same issue here, tested with Firefox 119.0 (64-bits). Clearing cache and cookies + starting Firefox in safe mode does not make a difference. The same Windows Admin Center loads fine in Edge.
I too am running into this same issue with Firefox, but now also with Chrome & Edge. While there's been community provided fixes (ex.: Modifying the .js file that contains the malformed string, then re-compressing the ux.zip file in the program files directory).
What's happening is the web page hangs at 'Gathering Environment Info..." permanently. I do know this is likely related to the issue of Firefox running its own certificate store, but this shouldn't be a penalty against Firefox - most Systems Administrators I know use Firefox because of this feature.
Yes, why exactly is Firefox not supported? what there is to support, aside from standard HTML and scripting? it looks like Microsoft is trying to force people to use Edge, which is based on Chrome, so they cannot do the same to Chrome.
This is still true as of 4/21/2024, now using Firefox version 125.0.1. This feels extremely anti-competitive and has been going on long enough to seem intentional by Microsoft and the WAC team.
Edit: I wanted to add, I'd love to have this available for our mixed Windows/Linux team to use, but things like this are what keep many of us from making more use of WAC beyond treating it as a home lab tool.
Based on information found elsewhere, it may be due to use of the ancerstorOrigins API, which Firefox are currently refusing to implement because as currently defined it is a privacy leak. TL;DR: this was sort of forced into the standard by Google using a loophole in the requirement for two shipping engines to implement it first.