W3C home > Mailing lists > Public > public-web-notification@w3.org > May 2014

Re: Rendering notifications with different pixel densities

From: Anne van Kesteren <annevk@annevk.nl>
Date: Thu, 1 May 2014 11:05:02 +0100
Message-ID: <CADnb78goQgmyR+-wNhTk2GO88JCafZ+7SsofwM6UOSGXZuzP3g@mail.gmail.com>
To: Justin DeWitt <dewittj@google.com>
Cc: Mounir Lamouri <mounir@lamouri.fr>, Marcos Caceres <w3c@marcosc.com>, WG <public-web-notification@w3.org>
On Wed, Apr 30, 2014 at 11:05 PM, Justin DeWitt <dewittj@google.com> wrote:
> Icon size information isn't actually sufficient to do both.  This is the
> reason that srcset contains both viewport constraints and scaling factor
> constraints. Frequently, a 32x32 @1x icon is not the same bitmap as a
> 16x16@2x icon.  The smaller the icon the more dramatic the effect.


> It's possible I don't fully understand how a manifest would work with the
> notifications API.  Do you reference the json format only, or somehow think
> that the notification should be able to reference icons specified in a
> manifest?

Share syntax. Notifications should be able to define their own icon.
Falling back to the icon of the page might be a good thing to do
though (with /favicon.ico at the end).

Received on Thursday, 1 May 2014 10:05:31 UTC

This archive was generated by hypermail 2.3.1 : Tuesday, 6 January 2015 19:53:14 UTC