@aardrian @siblingpastry okay, now that I had time to look at it properly I've decided to leave it as is because Mark and Marktext are the UA defaults anyway. So changing the keywords would be a repetition of the existing rule. It's worth tough considering to create an issue and ask for Mark and MarkText to respect forced colors mode.
> It's worth tough considering to create an issue and ask for Mark and MarkText to respect forced colors mode.
I don’t understand what this means. File an issue with who? And what is the issue?
@aardrian @siblingpastry No, problem, I can explain. :) The issue is described in your article. I'd question if this rule in the UA style sheet is a good idea, or, at least, I'd like to know why they do it.
` mark {
-internal-forced-background-color: yellow;
-internal-forced-color: black;
}
`
For most other elements and properties they use system colors but on mark they force black and yellow.
When I do forced-colors emulation (because flipping in and out blows up a UI control on which I am relying today), I see this in the inspector in both Edge and Chrome for the UA stylesheet:
```
mark {
background-color: mark;
color: marktext;
}
```
And this in CSS you shared:
```
mark {
background-color: Mark;
color: MarkText;
}
```
No other `mark` declarations.
And no `-internal-forced` with Ctrl + F.
@matuzo
So I am curious how you got that since I am not seeing it in the browser(s) nor in the file you linked.
@aardrian @siblingpastry No wonder, I copied the wrong URL. :) The forced colors rules in Chromium are in a separate CSS file.
@matuzo
Ok, that’s interesting because it doesn’t seem to manifest in the inspector.
It’s not clear to me if or how or when those are applied.
How did you encounter this? Or, rather, on what site did you encounter this which triggered these to appear in the UA styles?
@aardrian @siblingpastry I talked to platform devs and they told me that it may have something to do with them using non-standard media queries in their UA styles, and because of these internal properties they use. So it's definitely used but not exposed in Dev Tools.
Again, I didn't discover it, you did. It's on your blog post. I just tested it and confirmed that the color is always yellow/black unless overwritten.