- Update dependencies:
web-request-rpc@3.0.1
- BREAKING: Change to module.
- BREAKING: Update dependencies.
web-request-rpc@3
- Ensure
navigator.credentials[get|store]methods from the polyfill will continue to run and processoptions.web|WebCredential, even if those methods are changed by other software that runs after the polyfill is set up.
- Add ability to send
protocolsoption. This property can be used with requests or with aWebCredentialto specify a dictionary of protocol URLs, where the keys in the dictionary are the protocol name and the values are the protocol URLs. These URLs will be passed to any credential handler that registers itscredential_handler.acceptedInput(via its Web app manifest) asurlinstead of the defaultevent. - The
protocolsoption is experimental and may change without a new major revision to the API.
- Throws error when loaded in an insecure context.
- Use
web-request-rpc@2.0.2to avoid chromium mouse event bug.
- Use
web-request-rpc@2.0.1to avoid chromium-based browser focus bug.
- BREAKING: Deprecate and make hints and registration APIs ineffectual.
Registering a credential handler now only involves successfully asking
the user to allow
credentialhandlerpermission -- and providing a validcredential_handlersection inmanifest.json. Hints are no longer used and there is noregistrationAPI. An effort has been made to prevent existing code from breaking if it uses these APIs. Prior to this release using these APIs to add hints or registrations was largely ineffectual or at least unreliable as all that was required to ensure that a credential handler showed up in the mediator UI chooser was the presence of any hint or the use ofcredential_handlerinmanifest.json(plus a recommendation from a relying party when calling thegetorstorecredential API. This has been simplified now -- and to a large extent existing code will continue to function as it did before. This is especially true for most users as the behavior for the Chrome browser is the least changed; other browsers that request permission from a credential handler site (aka digital wallet site) will see those permission requests always result in prompting the user -- as other browsers do not have access to storage to check for a previously saved permission value. The corrective course of action is to move any such code that wasn't previously hidden behind user activation behind one (e.g. a button / click / tap).
- Add option to pass
mediatorOriginas an option to load functions.
- Fix options passed to
WebCredential.
- Add ability to send
recommendedHandlerOrigins. This property can be used with requests or with aWebCredentialto specify an array of credential handler origins (up to 3 will be accepted by the mediator) to recommend.
- Update dependencies.
- Update dependencies.
- Update dependencies.
- Add a default mediator url for the polyfill.
- Use webpack UMD target with
credentialHandlerPolyfillname.
- Darken backdrop for mediator window.
- Up mediator load timeout to 30 seconds.
- Add missing
PermissionManager.js.
- Allow polyfill load to happen in parallel with relying party site load.
- Update dependencies.
- Build browser file with webpack.
- Distribute plain min.js bundle (requires browser async/await support).
- Fix native get() recursion.
- Remove logging.
- Include credential request origin. TBD how origin will be blinded; but will still be included for targeting during signing of verifiable profile.
- Auto-install polyfill.
- Fix bug in
imageToDataUrl.
- Do not inherit custom events from
Event.
- Prefetch icons.
- Allow
nullcredential response.
- Update deps.
-
Add core files.
-
See git history for changes previous to this release.