Re: [csswg-drafts] [accent-color] Should interoperability be a goal for the `accent-color` spec? (#5480)

I like form elements to feel "native" to the browser and OS I'm using. If I'm on Chrome, I want the checkboxes and drop-downs to feel like Chrome checkboxes and drop-downs. If I'm on Safari, I want the checkboxes and drop-downs to feel like Safari checkboxes and drop-downs. So, I like the idea of specifying an accent color and allowing browsers to decide where where to use it.

This lines up with how most operating systems use accent colors: In [macOS](https://developer.apple.com/design/human-interface-guidelines/macos/overview/whats-new-in-macos/#app-accent-colors), [Windows](https://docs.microsoft.com/en-us/windows/uwp/design/style/color#accent-color), [iOS](https://medium.com/@priya_talreja/accentcolor-in-swiftui-setting-app-theme-58347682ba54), and [Android](https://www.androidauthority.com/android-q-accent-colors-965511/), when a user or developer sets an accent color, they don't decide which elements are colored – an accent color is set, and the OS applies it where it will.

-- 
GitHub Notification of comment by samuelbradshaw
Please view or discuss this issue at https://github.com/w3c/csswg-drafts/issues/5480#issuecomment-692474545 using your GitHub account


-- 
Sent via github-notify-ml as configured in https://github.com/w3c/github-notify-ml-config

Received on Tuesday, 15 September 2020 05:32:01 UTC