It seems that similar issues exist in dark mode and high-contrast mode.
Perhaps related- when I look at devtools, the background-color property is set to var(--_bu-bg);, and --_bu-bg seems not to be defined.
It seems that similar issues exist in dark mode and high-contrast mode.
Perhaps related- when I look at devtools, the background-color property is set to var(--_bu-bg);, and --_bu-bg seems not to be defined.
Thanks for reporting @starball and sorry for the bug! I'm happy to report that this bug is fixed as of an update pushed out yesterday.
This issue arose because styles on our button component's filled variant (.s-btn__filled) were being superseded by rules applied on :not(.s-btn__outlined). The filled and outlined variants are intended to be used exclusively from one another, so we increased specificity by applying filled styles to elements that matched .s-btn__filled:not(.s-btn__outlined) to resolve this issue.
For more context and details, check out the pull request for this fix in our design system. To see the specific code change made to resolve the problem, see the changes made to button.less.
This seems to be due to an issue with "visited link" highlighting behavior.
If I repro this in an incognito window (or where I haven't clicked "ask" in quite some time), I don't repro:
But doing it again after being logged in and recently clicking the button, it now appears on simple hover:
For further evidence, you can also repro this in an incognito window by using dev tools for force the state of the button to be :visited, which produces the same behavior on hover.