L lindros2 Regular Contributor Jan 30, 2025 #1 Anyone else? I submitted a bug request, and all earlier/alternative browsers appear okay.
B bennor Part of the Furniture Jan 30, 2025 #2 It may help if you provide the merlin firmware version you are experiencing the issue on.
Ripshod Part of the Furniture Jan 30, 2025 #3 Hold on. Isn't chrome 133 the beta? Current release versions for Windows, Apple, Linux and Android are all 132.
Hold on. Isn't chrome 133 the beta? Current release versions for Windows, Apple, Linux and Android are all 132.
L lindros2 Regular Contributor Jan 31, 2025 #4 firmware latest release (3004.388.8_4). Filed Chromium bug. They marked as low priority; something changed (as usual) which borked Merlin.
firmware latest release (3004.388.8_4). Filed Chromium bug. They marked as low priority; something changed (as usual) which borked Merlin.
L lindros2 Regular Contributor Feb 2, 2025 #6 Poul Bak said: Looks like javascript errors Click to expand... but only in the version of Chrome noted. This happens from time to time with Chromium - they break shirt with rendering which kills enterprise software, too. And the Chromium team doesn't give AF.
Poul Bak said: Looks like javascript errors Click to expand... but only in the version of Chrome noted. This happens from time to time with Chromium - they break shirt with rendering which kills enterprise software, too. And the Chromium team doesn't give AF.