Replies: 1 comment
-
|
Support for IE11 has been dropped by Microsoft themselves, and customers are encouraged to move to a more modern browser. It is no longer considered secure to venture out onto the internet using IE11, as no new security patches will ever again be made for the browser. If your users use IE11, you should implore them to migrate over to Edge, Chrome, Firefox, Safari or any other more modern (continuously updated) browser! I don't personally think we should support IE11 (as you might have gathered from my reasoning above), but I'm interested in hearing why you need the library to support IE11. Do you have a user base using IE11? Are you developing for an internal system built upon specificities of IE11? If there's some reason we haven't thought of, we might consider it (as I agree; the required change is quite small). |
Beta Was this translation helpful? Give feedback.
-
Not sure this has been tested in ie11 , but it erred.
pckeUtils.ts: line 32 has 2 issues for ie 11.
(IE11 uses an old standard of the Web Crypto API, the digest method does not return a promise which happens in all other browsers, instead, it returns a CryptoOperation. There is hardly any reference on the internet about this mysterial operation, as per OAUTH PKCE: Generate code_verifier and code_challenge in IE11 and modern browsers)
May be a support for 1e11 could be beneficial?
Beta Was this translation helpful? Give feedback.
All reactions