Yonke imikhiqizo Community Forum

When I go to some websites, such as Corair.com it hangs. I cannot click on anything. If I try to access specific pages via a search engine the same happens. I can close the browser but the 8+ processes don't terminate so I have to kill them from task manager.

I clear all of my browser history when I close FF so I can't remember all of the sites this happens on, but it was more than just Corsair.com.

I'm using 140.2.0esr, but also had the problem with 140.1.0esr. I did not have this issue on 128.12.0esr (I upgrade to 140 after that).

I tried turning use hardware acceleration off/on, that didn't fix it.

I am just about to try safe mode.

FF bug (?) (my own tests), Chrome works as expected, was also gemini ai discussed.:

 Why for the following css rule (new FF):
 header:has(~ noscript) ~ * div[class*="-slider"] {width: calc(var(--number-of-slides) * 100%);}
 the --number-of-slides is defined and visible:
 header:has(~ noscript) ~ * div[class*="-slider"] {--number-of-slides: 1}
 but this one isn't at all:
 header:has(~ noscript:has([value="1"])) ~ * div[class*="-slider"] {--number-of-slides: 1}
 And all remembering that in the noscript there is direct descendant having value="1"

As mentioned it works as expected (so average person naturally may think it sould) well for Chrome - noscript is visible, js disabled, controls are visible. Sophisticated use case of :has() but it sort of "has right" to happen.