-
-
Notifications
You must be signed in to change notification settings - Fork 32.2k
Open
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.encodingIssues and PRs related to the TextEncoder and TextDecoder APIs.Issues and PRs related to the TextEncoder and TextDecoder APIs.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.
Description
Version
v23.6.0, v22.13.0
Platform
Darwin xxx 24.1.0 Darwin Kernel Version 24.1.0: Thu Oct 10 21:00:32 PDT 2024; root:xnu-11215.41.3~2/RELEASE_ARM64_T6030 arm64
(but no problems reproducing it on Linux amd64 or arm64/)
Subsystem
No response
What steps will reproduce the bug?
const decoded = new TextDecoder("Windows-1252").decode(new Uint8Array([146])).charCodeAt(0);;
console[decoded === 8217 ? 'error' : 'log'](`Expected 8217 got ${decoded}`);
146 is now decoded as 146, not 8217. This still worked in v23.3.0 and v22.12.0 - might be related to the fix for #56219 ?
How often does it reproduce? Is there a required condition?
It always fails
What is the expected behavior? Why is that the expected behavior?
https://web.archive.org/web/20151027124421/https://msdn.microsoft.com/en-us/library/cc195054.aspx shows 0x92 should indeed be 0x2019
What do you see instead?
something else
Additional information
No response
apm78, galdebert, Basilio-mgd and 190n
Metadata
Metadata
Assignees
Labels
confirmed-bugIssues with confirmed bugs.Issues with confirmed bugs.encodingIssues and PRs related to the TextEncoder and TextDecoder APIs.Issues and PRs related to the TextEncoder and TextDecoder APIs.good first issueIssues that are suitable for first-time contributors.Issues that are suitable for first-time contributors.