@simplewebauthn/browser v0.10.0 make Edge stuck on Windows 10
See original GitHub issue@simplewebauthn/browser
v0.10.0 make Edge stuck on Windows 10.
const { startAttestation, startAssertion } = require('@simplewebauthn/browser');
// never reached
Build env: commonjs + webpack
Issue Analytics
- State:
- Created 3 years ago
- Comments:6 (2 by maintainers)
Top Results From Across the Web
Microsoft Edge got stuck all time in Windows10-OS
We have multiple windows10 devices in that most of the user having problem in Microsoft Edge freezing issue page cannot be open or...
Read more >SimpleWebAuthn/CHANGELOG.md at master - GitHub
A collection of TypeScript-first libraries for simpler WebAuthn integration. Supports modern browsers and Node. - SimpleWebAuthn/CHANGELOG.md at master ...
Read more >Browser - SimpleWebAuthn
This package is available on npm for use in projects that contain a build step, like in a single-page application: npm install @simplewebauthn/browser....
Read more >SimpleWebAuthn - bytemeta
Feature proposal: Stateless Challenge via JWT · Apple attestation · @simplewebauthn/browser v0.10.0 make Edge stuck on Windows 10 · Fix broken Netlify deploy....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
I’ve created a new “Edge Browser” page on the homepage with information about this issue, including suggestions on how to work around it: https://simplewebauthn.dev/docs/advanced/edge-browser
@mahnunchik Think there’s anything more I should add?
Aha, of course legacy Edge doesn’t support
TextEncoder
🤦caniuse confirms: https://caniuse.com/?search=TextEncoder
I’m torn on how to address this. SimpleWebAuthn supports “modern browsers” which I could argue omits legacy Edge for the Chromium version MS switched to. I see a couple of paths forward:
I’m inclined to go with Option 1. Option 2 would be a waste since it’d only be needed for a single now-deprecated browser.
@mahnunchik would you be willing to identify an
npm
polyfill package that fixes the issue? MDN also includes a spec-compliant polyfill I could link to to solve this with advice to “search NPM for ‘textencoder polyfill browser’”