Push API: Implement and ship PushSubscription.options

third_party/WebKit/Source/modules/push_messaging/PushSubscription.idl

 // Copyright 2014 The Chromium Authors. All rights reserved.
 // Use of this source code is governed by a BSD-style license that can be
 // found in the LICENSE file.
 
 // https://w3c.github.io/push-api/#pushsubscription-interface
 
 enum PushEncryptionKeyName {
     "p256dh",
     "auth"
 };
 
 [
     Exposed=(Window,ServiceWorker),
     RuntimeEnabled=PushMessaging,
 ] interface PushSubscription {
     readonly attribute USVString endpoint;
+    [SameObject] readonly attribute PushSubscriptionOptions options;
 
     ArrayBuffer? getKey(PushEncryptionKeyName name);
     [CallWith=ScriptState] Promise<boolean> unsubscribe();
 
     serializer;

[Peter Beverloo, 2016/07/08 18:30:12]

Should the `options` member influence the serializer?

[johnme, 2016/07/13 17:51:57]

The spec explicitly says "the options to a PushSubscription are not
serialized"[1], and I find no strong reason to object (most servers will always
pass the same options, so it's redundant). Perhaps PushSubscriptionOptions
should have its own separate serializer though?

[1]: https://w3c.github.io/push-api/#pushsubscription-interface

 };