[whatwg] [Notifications] Notification.hasPermission() instead of Notification.permission

The Notification specification defines a static Notification.permission accessor, which returns one of {granted, denied, default}. This requires the browser to synchronously determine whether the page has permission to show notifications, whereas checking this may be an asynchronous operation. This

Re: [whatwg] forwarded: Google opens VP8 video codec

On Thu, May 20, 2010 at 11:55, David Gerard wrote: > 2010/5/20 Peter Beverloo : > > > Microsoft has announced playback support for VP8 in Internet Explorer > 9[1] > > under the condition that one has to install a VP8 codec manually, albeit > via > > inclusion in

Re: [whatwg] Problem with http://www.webmproject.org/

On Thu, May 27, 2010 at 17:12, Michael A. Puls II wrote: > > Off topic (but I couldn't find any contact info on the site) > > Could someone please fix ? The left side of the > page is inaccessible at < 1024 x 768 (800 x 600 for example), which makes the > site unusab

Re: [whatwg] Comment on 6.6 Offline Web Applications

ng to make a proposal, as it isn't hard to think about use-cases for such a feature. Regards, Peter Beverloo [1] http://www.whatwg.org/specs/web-apps/current-work/multipage/offline.html#expiring-application-caches

Re: [whatwg] Potential Danger with Canvas API in html5 #html5 #canvas

On Wed, Jun 9, 2010 at 20:29, narendra sisodiya wrote: > > Canvas API is just great and I love it, You will also love it , if not, just > see Canvas demos - http://www.canvasdemos.com > > But we have potential danger to misuse it also for the sake of non-standards. > > > Case 1 - Abode can make

Re: [whatwg] Potential Danger with Canvas API in html5 #html5 #canvas

On Wed, Jun 9, 2010 at 22:05, narendra sisodiya wrote: > > > On Thu, Jun 10, 2010 at 12:20 AM, Peter Beverloo wrote: >> >> On Wed, Jun 9, 2010 at 20:29, narendra sisodiya >> wrote: >> > >> > Canvas API is just great and I love it, You will also

Re: [whatwg] Prefetch issues

er. The link tag is specifically used for metadata about the current document, so using that across the entire document doesn't sound like a good idea to me. Despite the possibility of abuse by authors, it seems to me that it's a fair use-case for including the attribute. Regards, Peter Beverloo [1] https://developer.mozilla.org/En/Link_prefetching_FAQ

Re: [whatwg] Proposal for a widget tag

On Sun, Jun 13, 2010 at 17:17, Schalk Neethling wrote: > Hi there, > > > > I have watched one video after the other, and read articles just the same. I > know we are all unsure when to use section and when to use article. But > marking up something as simple as a blogroll as an article? This reall

[whatwg] Clarifying the use and requirements of Data URL

the form submission algorithm[4], so they can be applied on the entire document. - Extend the accepted values of @src, @href, @action et al to include support for data: URLs. Thank you, Peter Beverloo [1] http://www.whatwg.org/specs/web-apps/current-work/#dom-canvas-todataurl [2] http://www.whatw

Re: [whatwg] Clarifying the use and requirements of Data URL

On Tue, Aug 24, 2010 at 17:49, Julian Reschke wrote: > > On 18.08.2010 15:21, Peter Beverloo wrote: >> >> Currently the specification requires the use of Data URLs for >> canvas.toDataURL[1] and refers to usage of them a number of times as >> well[2][3].  While step

Re: [whatwg] use cases

terday: http://html5.org/tools/web-apps-tracker?from=5944&to=5945 Most references to the element have been removed as well, and this section has been introduced: http://www.whatwg.org/specs/web-apps/current-work/multipage/dnd.html#obtaining-local-multimedia-content Regards, Peter Beverloo

Re: [whatwg] At Inclusion (a declarative way to "Ajaxise" a website)

On Sun, Jun 17, 2012 at 10:32 AM, Florent FAYOLLE < florent.fayoll...@gmail.com> wrote: > Hello, > > I have written a proposal that introduces a new way to include remote > contents into the document (in other (bad) word, to "Ajaxise" it) using a > declarative way. > This proposal is named At Incl

[whatwg] [Notifications] Persistent notifications depending on Service Workers

Based on Anne's Reviving Notification Objects thread from last year, I would like to propose an alternative solution. http://lists.whatwg.org/htdig.cgi/whatwg-whatwg.org/2013-March/251058.html There are known lifetime issues with Notifications, and rather than tying them all to the page, how abo

Re: [whatwg] [Notifications] Persistent notifications depending on Service Workers

ch in itself may be undesirable to start with. Thanks, Peter On Tue, May 13, 2014 at 3:33 PM, Peter Beverloo wrote: > Based on Anne's Reviving Notification Objects thread from last year, I > would like to propose an alternative solution. > > > http://lists.whatwg.org/htdig.c

Re: [whatwg] [Notifications] Persistent notifications depending on Service Workers

On Fri, May 16, 2014 at 2:57 PM, Anne van Kesteren wrote: > On Thu, May 15, 2014 at 6:12 PM, Peter Beverloo > wrote: > > For |notificationshow|, there is a worry here that if we decide to > support > > delayed notifications, it would enable developers to use notificatio

Re: [whatwg] Notifications improvements

In principle I agree that the specification should be implementable by all major platforms. However, I also think that there is an important trade-off to make here, since they are an increasingly important part of the user experience offered by an applications -- most notably when applications can

[whatwg] [Notifications] Behavior of Notification.requestPermission in workers

Since the entire Notification object is exposed both on window and in workers, I'd like some clarification on the intended behavior of Notification.requestPermission() when called in the background. http://notifications.spec.whatwg.org/#dom-notification-requestpermission Some options: (1) Re

Re: [whatwg] [Notifications] Behavior of Notification.requestPermission in workers

That'd work for me too. Peter On Mon, Jul 28, 2014 at 1:00 PM, Anne van Kesteren wrote: > On Mon, Jul 28, 2014 at 6:55 PM, Peter Beverloo > wrote: > > Any opinions? > > I prefer (4), add [Exposed=Window]. > > > -- > http://annevankesteren.nl/ >

Re: [whatwg] [Notifications] Persistent notifications depending on Service Workers

[onnotificationshow, onnotificationclick, onnotificationclose, onnotificationerror]. The events will receive a NotificationEvent which will contain a notification instance. Thanks, Peter On Fri, May 16, 2014 at 3:17 PM, Anne van Kesteren wrote: > On Fri, May 16, 2014 at 4:02 PM, Peter Beverloo >

Re: [whatwg] [Notifications] Persistent notifications depending on Service Workers

On Tue, Aug 5, 2014 at 3:48 PM, Anne van Kesteren wrote: > On Tue, Jul 29, 2014 at 4:28 PM, Peter Beverloo > wrote: > > When used from a Service Worker, the attribute will implicitly default to > > the ServiceWorkerRegistration of the running Service Worker. > > Is

Re: [whatwg] Notifications improvements

Hi Andrew, On Wed, Aug 6, 2014 at 12:59 PM, Andrew Wilson wrote: > On Wed, Aug 6, 2014 at 12:48 PM, Anne van Kesteren > wrote: > > On Wed, Aug 6, 2014 at 10:08 AM, Andrew Wilson > wrote: > >> I understand your concern that is driving this proposal: you don't > >> want to provide rich APIs that

Re: [whatwg] Notifications improvements

On Mon, Aug 11, 2014 at 9:27 AM, Andrew Wilson wrote: > On Fri, Aug 8, 2014 at 2:48 PM, Peter Beverloo > wrote: > > Hi Andrew, > > > > On Wed, Aug 6, 2014 at 12:59 PM, Andrew Wilson > wrote: > >> > >> On Wed, Aug 6, 2014 at 12:48 PM, Anne van Kester

Re: [whatwg] Notifications and service workers

Let me reply to a few points mentioned in this thread -- it's quite overloaded :-). I've also added Andrew, who might know some historical reasons for the events. (Andrew: most of this is in context of persistent notifications.) * Life-time of existing notifications. Chrome currently treats Web

Re: [whatwg] Notifications and service workers

On Wed, Oct 1, 2014 at 12:31 PM, Anne van Kesteren wrote: > On Fri, Sep 26, 2014 at 4:36 PM, Peter Beverloo > wrote: > > * Life-time of existing notifications. > > > > Chrome currently treats Web Notifications as "persistent" ones. When the > >