tab bar background color) <- in our case here the active windows accent color If there is an additional need to force users for the New Light Colors, then force enabling Light theme for them (still not the best solution)Ī workaround would be to edit userChrome.css for the following design elements: If the whole change was dictated by the new Design choice, then the more logical way would be to change the Light theme coloring, and leaving the existing Default theme as it is.

the feature was not interfering with either Light or Dart theme.

after the bug 1686529 default theme is virtually the same as Light theme.

the feature was present before and worked without any visual bugs.

With all respect this does looks and sound like a Regression: This means that virtually every Windows 10 user that is aware of/uses the OS accent color and Default Firefox theme is affected by the change.Īnt if it worked before and stopped working now, in terms of user experience this is a drawback.Īre there any metrics that show the amount of users that potentially will be affected by this change (usage of accent color in Firefox)? The Titlebar Background color is one of the first things that is visible to user once the Browser starts. The key point is that Proton did support accent at some point, and it coexisted with remaining built-in themes. VS code - agree, it is hard to tell why is doesn't tolerate the accent color. One Note - exclusively uses Purple as its accent color (like the mayorify of Office apps) Steam - uses its separate skin system that doesn't have any connection with the OS accent at all Not all examples provided are a not 100% relevant.

Windows 10 inactive title bar color