Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This change updates a long-standing piece of Push Subscription directions in the README which demonstrates setting of the applicationServerKey into a Uint8Array from the decoded raw bytes of the vapid public key.
This step is cumbersome and there is a simpler alternative.
The Push API docs for the PushSubscriptionOptions interface say of the applicationServerKey:
RFC 7515 states that the Base64 url-safe encoding omit the padding characters:
The library's generated vapid public key is already Base64 url-safe encoded. However, for historical reasons, Ruby's
Base64.urlsafe_encode64
method includes the padding character, "=", incorrectly by default. This behavior exists in the library's current vapid key generation. Therefore, the directions include explicit deletion of the "=" character.For historical discussion of Ruby's encoding issue, see: https://bugs.ruby-lang.org/issues/10740
I've tested the change in recent versions of macOS-based Chrome, Safari, Firefox, and Edge.