no idea who caused the issue
but there are always differences between browsers, maybe it didnt work in Chrome, because Chrome is using the good html standards and other browsers not, so maybe Xerox also wasnt following the html standards
who knows, you should :) what did Xerox do to fix it?
It was already fixed in Chrome Canary for a while, so I don't know what Xerox could have done in firmware
Chrome 75 on the left, 77 on the right
fixed in firmware release xx.45.61 , so seems to be a versalink issue after all :)
from rls notes : Unable to log into printer webui as admin when connected with Google Chrome version 74.0.3729.131.
It's also present on Version 75.0.3770.80 (Build officiel) (64 bits). Since the version 74.
Sentence 1 in the posted solution "Chrome 74 is the only browser with the issue, downgrade Chrome and it will work again"
If you install Google Canary (Which is beta Chrome, right now it is Version 76.0.3790.0 (Official Build) canary (64-bit) ) the issue still occurs, so it seems it won't be fixed soon.
Chrome also has an option to report issues like this ala Hamburger menu > Settings > About Chrome > Report an issue. But I can't figure out exactly what to report since I doubt they have access to a VersaLink device, and I don't know exactly what is causing it.
I can confirm that Xerox developers have had the issue escalated to them in france, the ID is CQGbl01337152, at this moment, nothing has been logged it the escalation.
Chrome 74 is the only browser with the issue, downgrade Chrome and it will work again.
As far as I know, nobody has figured out what they did to it, but it is absolutely Chrome 74 that caused it, maybe they created a bug, maybe they implemented a security nobody else has, maybe they dropped a protocol (Similar effect happens to Chrome if you disable SOAP on the printer, similar, but not the same, so don't bother going in and messing wiht it, I did for hours and got nowhere)
Edge browser also does it if you are on the Insider fast lane, so it would seem Chromium may be the source of the problem (Chrome is built on Chromium, and EDGE is moving to it)
It isn't just the C405 either, it is every Xerox VersaLink product.
You are far from the only one who noticed. Another guy posted a few hours ago.
I actually came across it back on April 30th. Xerox knows about it, no idea if Google does (or cares)