- From: Peter Beverloo <notifications@github.com>
- Date: Thu, 04 Aug 2016 05:31:14 -0700
- To: w3c/manifest <manifest@noreply.github.com>
- Message-ID: <w3c/manifest/issues/480/237538822@github.com>
Browsers currently use their own icons on Android, but that's definitely not sufficient for branding. That's why the per-notification option was introduced. This is insufficient in two cases: 1. Notifications shown on behalf of the website, but not through the Notification API. (E.g. update notifications, media notifications, Chrome's forced push notification.) 2. Android users using Android L or earlier, where the necessary APIs to do this on a per-notification basis are not available. @skddc It might be, but my concern is that it may be confusing when this happens since it'll be displayed in a different context, much smaller and often with a mask applied. @kenchris We shied away from this in the Notification API because you'd end up defining operating system behaviour that's out of our control. It has a note indicating that certain resources can be modified by the OS to match platform consistency. --- 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/480#issuecomment-237538822
Received on Thursday, 4 August 2016 12:34:43 UTC