-
Notifications
You must be signed in to change notification settings - Fork 4.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(sec): remove MSIE support to allow upgrading to vuln-free dompurify
v3
#3827
fix(sec): remove MSIE support to allow upgrading to vuln-free dompurify
v3
#3827
Conversation
…ify` v3 Signed-off-by: hainenber <dotronghai96@gmail.com>
Above statement is obsolete. All MSIE ref removed |
Signed-off-by: hainenber <dotronghai96@gmail.com>
Signed-off-by: hainenber <dotronghai96@gmail.com>
I removed all proper MSIE references in the codebase. The generated polyfills might not needed anymore but I keep it as safe harness since older browsers can constitute Chrome/Firefox early versions as well. |
Signed-off-by: hainenber <dotronghai96@gmail.com>
Signed-off-by: hainenber <dotronghai96@gmail.com>
afa6c67
to
b344dc1
Compare
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you!
Thank you for the PR. I'll release it now. |
Resolve #3819
Remove MSIE support as CVE-2025-26791 affects
dompurify
v2 and the only resolution is to bump todompurify
v3. However, the new major version dropped support for MSIE sojspdf
must do the same.