Bugzilla

This "override colors" feature has a spec, it's in [here](https://drafts.csswg.org/css-color-adjust/#forced) and we follow that.

FWIW you can emulate this mode on any OS in Chrome and Edge using DevTools, and they behave like we do.

It seems like the behavior comment 0 is expecting is something like what would be achieved by having a user style like:

```
:any-link { color: LinkText !important; }
* { forced-color-adjust: initial !important }
```

Or so. That's trivial to do as an extension, but I don't think we should do it by default.

I think this is not a core bug, per se. This is working as intended.  That said, I'd argue that our color dialog UI is, indeed, a bit confusing... If only, because pages can opt out of this behavior themselves by using something like `forced-color-adjust: none`.

So we should probably reword the settings UI to not be so strict (or adding another setting to "really really force them please").

This "override colors" feature has a spec, it's in [here](https://drafts.csswg.org/css-color-adjust/#forced) and we follow that.

FWIW you can emulate this mode on any OS in Chrome and Edge using DevTools, and they behave like we do.

It seems like the behavior comment 0 is expecting is something like what would be achieved by having a user style like:

```
:any-link { color: LinkText !important; }
:any-link:visited { color: VisitedText !important }
/* optionally: * { forced-color-adjust: initial !important } */
```

Or so. That's trivial to do as an extension, but I don't think we should do it by default.

I think this is not a core bug, per se. This is working as intended.  That said, I'd argue that our color dialog UI is, indeed, a bit confusing... If only, because pages can opt out of this behavior themselves by using something like `forced-color-adjust: none`.

So we should probably reword the settings UI to not be so strict (or adding another setting to "really really force them please").