Summary: | TextDecoder doesn't detect invalid UTF-8 sequences early enough | ||||||||
---|---|---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | Andreu Botella <andreu> | ||||||
Component: | DOM | Assignee: | Nobody <webkit-unassigned> | ||||||
Status: | RESOLVED FIXED | ||||||||
Severity: | Normal | CC: | achristensen, andreu, ap, clopez, darin, ews-watchlist, mmaxfield, webkit-bug-importer, youennf, ysuzuki | ||||||
Priority: | P2 | Keywords: | InRadar | ||||||
Version: | WebKit Nightly Build | ||||||||
Hardware: | Unspecified | ||||||||
OS: | Unspecified | ||||||||
See Also: |
https://bugs.webkit.org/show_bug.cgi?id=216202 https://bugs.webkit.org/show_bug.cgi?id=234030 |
||||||||
Attachments: |
|
Description
Andreu Botella
2021-12-07 03:55:22 PST
I think we will need to do basically the same thing as Chromium, but it won't be a simple cherry pick because their DecodeNonASCIISequence returns a different value than our decodeNonASCIISequence and doesn't change the length, and their handlePartialSequence for LChar and UChar are more similar than ours are. *** Bug 234030 has been marked as a duplicate of this bug. *** Created attachment 446994 [details]
Patch
This patch modifies the imported WPT tests. Please ensure that any changes on the tests (not coming from a WPT import) are exported to WPT. Please see https://trac.webkit.org/wiki/WPTExportProcess Created attachment 447070 [details]
Patch
Committed r287024 (245229@main): <https://commits.webkit.org/245229@main> All reviewed patches have been landed. Closing bug and clearing flags on attachment 447070 [details]. |