![]() (Cockpit works in browsers that are roughly 2 years old right now. It also doesn't have web features Cockpit needs to function properly. □)Īnyway, EdgeHTML was completely discontinued by Microsoft a while ago and is, as a result, wildly insecure. (Later that year, it was even released on Linux. It was first announced on December 6, 2018, had a preview and beta cycles, and was finally released fully across all Windows versions on January 15, 2020. Since this time, Microsoft has discontinued support for all versions of EdgeHTML-based Edge browsers and switched to Chromium (the engine that powers Chrome as well as Edge and almost all other browsers other than Firefox and Safari). In this case, that error is correct - their browser does not have support for it (or many other things) and it has gigantic security issues.Įdge 42 was released on Apand features EdgeHTML 17.17134. That's super old and should've not been used for quite some time. You are receiving this because you were mentioned.Message browser was version 42 Reply to this email directly, view it on GitHub Have a login prompt and can log in, then you're not affected. Then I'd suggest installing the backport (if this isn't already). If you cannot log in and have the is:():where() error, It's the same version as theīackport though. Your version, if isn't a backport somehow. The backport is not affected, nor is the non-backports. Letting me log in do everything, including seeing the about box: Here's a screenshot of Cockpit 264 from backports - it works as expected, Latest for non-backports Cockpit on Ubuntu 20.04 is 215. If it's *not* a backport, where did you get 264-1ubuntu0.22.04.1? The ![]() I then installed Cockpit with the instructions on the website. Install of Ubuntu 20.04 that was then upgraded with apt update & apt ![]() I installed Cockpit using the instructions from the website on a fresh Unknown or not applicable Server operating system Other fellow users that might eventually encounter such issue.Details on if a commit broke something else, or if this behaviour is 100% intended, is still unclear. The opened issue is currently awaiting triage on FF end. I never encountered issues with Cockpit before that change. Maybe the FF change broke something else, or maybe it was simply unsupported from the start. I must say, the UI was working fine before that change, therefore I'm not sure if it is essential for Cockpit to check for selector(:is():where()) on the login page and prevent users from logging in if it isn't supported. This change might eventually reach upstream stable branch as Firefox follow W3C guidelines on how things should be reported or implemented on the engine. Since that fix was implemented, Firefox Nightly users can no longer log in into Cockpit. Firefox Nightly now reports unsupported CSS selectors (see issue).
0 Comments
Leave a Reply. |