On Wed, Feb 15, 2012 at 6:12 PM, Jian Li <[email protected]> wrote:
> > > On Wed, Feb 15, 2012 at 9:46 AM, Jon Lee <[email protected]> wrote: > >> On Feb 13, 2012, at 5:51 PM, Andrew Wilson <[email protected]> wrote: >> > I don't have an answer for you here, as the internet is vast :) Among >> google properties, Gmail and Google Calendar currently use it. I'm not >> aware of any other google property that uses it in their web pages, but >> some do via extensions. >> >> >> >> On Feb 13, 2012, at 5:29 PM, Adam Barth <[email protected]> wrote: >> > IRCCloud is an example of a site that I use every day that uses >> notifications. >> >> >> Ok, thanks for providing these sites. >> >> It seems to me that we are in agreement with most of the proposal. I >> would like to begin work on these changes. I will file a master bug so that >> we can track progress. I think we can make these improvements without >> disturbing what we already have, to maintain current compatibility. Does >> this sound good? >> > My concerns are two-fold: 1) Can we run this by the standards body first? I think it makes sense to gain some consensus among the webkitters before going to the standards body, but now that we have this consensus, I'd really like to give that group a chance to comment before we start implementation in case there's something we missed. Is there a compelling reason to move forward with implementing before getting their feedback (or perhaps do that in parallel?) 2) I'm still concerned with the use of WebKitNotification(), when we already have a proposed API in place for Notification(). Even if we leave the current APIs intact (which is good!), we'll end up with 3 separate notification APIs (the current window.webkitNotifications, your proposed WebKitNotification(), and the final Notification()). It feels like the standards proposal is stable enough that we could move directly to implementing Notification(), especially if we can get prompt feedback about your proposed changes. I may have misunderstood your statement - perhaps you are planning to implement this as Notification() and not WebKitNotification(). I just hate to have yet another set of notification APIs that we'll have to deprecate, so I'd like to avoid it if possible. > > Sounds good, as long as we keep in mind of not to breaking > backward compatibility until app developers can switch to new syntax and > scheme. > >> >> Jon >> _______________________________________________ >> webkit-dev mailing list >> [email protected] >> http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev >> > >
_______________________________________________ webkit-dev mailing list [email protected] http://lists.webkit.org/mailman/listinfo.cgi/webkit-dev
