[webkit-dev] Followup on removing webkitNotifications.createHTMLNotification

[Adam Barth]

On Wed, Jan 23, 2013 at 11:28 AM, Jon Lee <jonlee at apple.com> wrote:
> Happy to hear about this!
>
> As a follow-up question, what numbers are you seeing with the rest of the legacy API? (webkitNotifications.createNotification, webkitNotifications.checkPermission, and webkitNotifications.requestPermission)

The only other API we're measuring is createNotification, which seems
to be used about 4x as often as createHTMLNotification.  That's
certainly in the range where we should consider removing support for
the prefixed version in favor of the unprefixed version.

The reason I haven't done it yet is that there isn't very good
developer documents explaining how to use the unprefixed API.  As I
mentioned earlier in this thread, I'm working with our developer
relations folks to improve that situation.  Once we have some good
documentation out, we should consider removing the prefixed API as
well.

Adam


> On Jan 23, 2013, at 1:11 AM, Adam Barth <abarth at webkit.org> wrote:
>> On Wed, Jan 23, 2013 at 1:08 AM, Andrew Wilson <atwilson at google.com> wrote:
>>> Apologies for the confusion - I should have finished my coffee before
>>> reading my mail. I didn't realize this only impacts HTML notifications.
>>>
>>> It's still a good reminder that Google really should migrate to the new
>>> notification APIs, though. I'll get the ball rolling on gmail, at least.
>>
>> Thanks!  Let me know if you run into any trouble.
>>
>> Adam
>>
>>
>>> On Wed, Jan 23, 2013 at 9:58 AM, Adam Barth <abarth at webkit.org> wrote:
>>>>
>>>> On Wed, Jan 23, 2013 at 12:45 AM, Andrew Wilson <atwilson at google.com>
>>>> wrote:
>>>>> Hmmm. Does FeatureObserver detect features invoked from web apps like
>>>>> Gmail?
>>>>
>>>> Yes.
>>>>
>>>>> Because I'm fairly certain that Gmail and Google Calendar still use
>>>>> webkitNotifications for their notifications. Not to say that we
>>>>> shouldn't
>>>>> land this patch anyway - just pointing out that this may still be used
>>>>> more
>>>>> often than your stats would indicate.
>>>>
>>>> As Morrita-san writes:
>>>>
>>>> On Wed, Jan 23, 2013 at 12:50 AM, Hajime Morrita <morrita at google.com>
>>>> wrote:
>>>>> It looks the patch is removing a specific API called
>>>>> createHTMLNotification().
>>>>> Unless these apps are showing HTML-based notification, it should keep
>>>>> working even after this change.
>>>>
>>>> If Gmail is still using the vendor-prefixed webkitNotifications
>>>> version of the API, they should update to the unprefixed "new
>>>> Notification" version of the API, which is implemented by a number of
>>>> different browsers.
>>>>
>>>> I know there's some amount of confusion about the current status of
>>>> the web notification APIs.  I'm working with Chrome's developer
>>>> relation folks to update our various pieces of documentation and
>>>> tutorials.
>>>>
>>>> Adam
>>>>
>>>>
>>>>> On Wed, Jan 23, 2013 at 1:47 AM, Adam Barth <abarth at webkit.org> wrote:
>>>>>>
>>>>>> As discussed in February 2012 [1], we have been deprecating the
>>>>>> webkitNotifications.createHTMLNotification API for almost a year.
>>>>>> According to FeatureObserver, the API is used in only 0.0008% of web
>>>>>> page views, indicating that we have been successful in depreciating
>>>>>> it.  I've posted a patch to remove it:
>>>>>>
>>>>>> https://bugs.webkit.org/show_bug.cgi?id=107598
>>>>>>
>>>>>> Thanks,
>>>>>> Adam
>>>>>>
>>>>>> [1]
>>>>>> http://lists.webkit.org/pipermail/webkit-dev/2012-February/019354.html
>>>>>> _______________________________________________
>>>>>> webkit-dev mailing list
>>>>>> webkit-dev at lists.webkit.org
>>>>>> http://lists.webkit.org/mailman/listinfo/webkit-dev
>>>>>
>>>>>
>>>
>>>
>> _______________________________________________
>> webkit-dev mailing list
>> webkit-dev at lists.webkit.org
>> http://lists.webkit.org/mailman/listinfo/webkit-dev
>