applicationServerKey does not accept a base64url encoded value
Reported by
alexen...@gmail.com,
Jan 16 2018
|
||||
Issue descriptionUserAgent: Mozilla/5.0 (Windows NT 10.0; Win64; x64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/64.0.3282.85 Safari/537.36 Steps to reproduce the problem: 1. Create an empty file service-worker.js 2. Run the test case What is the expected behavior? The push subscription should be created successfully, applicationServerKey should accept a url encoded base64 string https://w3c.github.io/push-api/#dom-pushsubscriptionoptions-applicationserverkey What went wrong? An error is thrown Uncaught (in promise) TypeError: Failed to execute 'subscribe' on 'PushManager': The provided value is not of type '(ArrayBuffer or ArrayBufferView)' at push-bug.js:8 at <anonymous> Did this work before? N/A Does this work in other browsers? Yes Chrome version: 64.0.3282.85 Channel: beta OS Version: 10.0 Flash Version: Shockwave Flash 28.0 r0
,
Jan 16 2018
Thank you for the report! We indeed don't implement this functionality yet, so let me mark this as available.
,
Apr 25 2018
i will take issue. and is this needed to write intent to implement and ship?
,
May 14 2018
https://chromium-review.googlesource.com/c/chromium/src/+/1013839 this patch is blocking until wpt test for push-api created. (https://groups.google.com/a/chromium.org/forum/#!topic/blink-dev/-n133nKRZA4) |
||||
►
Sign in to add a comment |
||||
Comment 1 by krajshree@chromium.org
, Jan 16 2018