It looks like this is the selector that makes Firefox Release and Chrome reject the rest of the rule (disregarding the selector that would otherwise match):
```
.provider-primary-seekbar::-webkit-slider-thumb:hover,
```
The site is accidentally relying on that selector causing the whole rule to be ignored.
Here's a reduced testcase to exercise that, which renders with white background in Firefox release & Chrome, vs. red in Firefox beta 152 and nightly 153.
Bug 2044435 Comment 5 Edit History
Note: The actual edited comment in the bug view page will always show the original commenter’s name and original timestamp.
It looks like this is the selector that makes Firefox Release and Chrome reject the rest of the rule (disregarding the selector that would otherwise match):
```css
.provider-primary-seekbar::-webkit-slider-thumb:hover,
```
The site is accidentally relying on that selector causing the whole rule to be ignored.
Here's a reduced testcase to exercise that, which renders with white background in Firefox release & Chrome, vs. red in Firefox beta 152 and nightly 153.
It looks like this is the selector that makes Firefox Release ~and Chrome~ reject the rest of the rule (disregarding the selector that would otherwise match):
```css
.provider-primary-seekbar::-webkit-slider-thumb:hover,
```
The site is accidentally relying on that selector causing the whole rule to be ignored.
Here's a reduced testcase to exercise that, which renders with white background in Firefox release & Chrome, vs. red in Firefox beta 152 and nightly 153.
It looks like this is the selector that makes Firefox Release ~and Chrome~ reject the rest of the rule (disregarding the selector that would otherwise match):
```css
.provider-primary-seekbar::-webkit-slider-thumb:hover,
```
The site is accidentally relying on that selector causing the whole rule to be ignored.
Here's a reduced testcase to exercise that, which renders with white background in Firefox release ~and Chrome~ vs. red in Firefox beta 152 and nightly 153.