Skip to content

TextDecoder is missing x-user-defined encoding #6039

Closed

Description

@ChALkeR

It should be there per spec

It's a simple single-byte encoding despite its name

Can be treated as a single-byte or algorithmic

Spec: https://encoding.spec.whatwg.org/#x-user-defined-decoder

The usecase for that is old compat loading of binary data over strings, as it can be then decoded easily (and TextDecoder does not expose isomporhic, and latin1 maps to windows1252 and is actually non-isomporhic and complex to decode back to bytes).

Activity

  1. JosephDoUrden commented on Feb 7, 2026

    @JosephDoUrden
    Contributor

    I’ll take a look at this and report back shortly

  2. added 2 commits that reference this issue on Feb 7, 2026
    9a380cf
    81a1d3e
  3. added a commit that references this issue on Feb 14, 2026
    67f5d25
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions