- From: Matt Giuca <notifications@github.com>
- Date: Sun, 17 Jun 2018 17:51:38 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <w3c/manifest/issues/695/397918398@github.com>
@kirupa can I clarify with you: is Windows moving towards a space where there is an *expectation* that all apps theme their own title bar (essentially deprecating the concept of a user-preference theme colour)? Or merely moving towards "fancy apps" being able to theme their title bar? Linux is tricky because user agents *can't* override the default title bar, they can only create a fully custom title. However, on Chrome, we're going to need to create a custom title bar anyway in order to add our custom UI, so Linux will actually be a type-(a) as well, at least on Chrome. Even on macOS, I was surprised to learn that a number of high-profile native apps, like Photoshop and Office, as well as Electron apps Spotify, Discord and WhatsApp, apply their own theming to the window. If the world is universally moving towards a model where apps theme their own window with their theme colour, then perhaps we don't need a separate switch for this (user agents can just always use the `theme_color` in the title bar). On the other hand, if the "default" app experience on Windows, macOS and especially Linux, is non-branded theme colour, then I think it makes sense to add this new member to allow "fancy" apps to override that default. On naming: I think there is precedent for calling things what they "commonly mean" as opposed to what the formal specification says they mean. For example, we don't use the word "browser" in standards, because formally a user agent can be something other than a web browser, but we still have "`display: browser`" which is the common name. "title_bar_color" is an appropriate name even though we wouldn't literally say "the title bar" in the standard. -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/manifest/issues/695#issuecomment-397918398
Received on Monday, 18 June 2018 00:52:01 UTC