Switch more invocations of JS parser to use UTF-8 parser
Categories
(Core :: JavaScript Engine, task, P1)
Tracking
()
| Tracking | Status | |
|---|---|---|
| firefox110 | --- | fixed |
People
(Reporter: tcampbell, Assigned: tcampbell)
References
(Blocks 1 open bug)
Details
Attachments
(5 files)
Now that we have UTF-8 JS parsing support, the char16_t should be deprecated. Numerous loaders in gecko decode from streams and then parse to JS. This bug is about switching those cases to decode into UTF8 before parsing. These cases already required well-formed UTF16, so using UTF8 as the target instead is can be done without further information loss.
| Assignee | ||
Comment 1•3 years ago
|
||
Similar to the ConvertToUTF16 overload for JS owned strings, add an overload for
the UTF8 case. This simplifies later work to switch parsing to UTF8.
| Assignee | ||
Comment 2•3 years ago
|
||
Depends on D164930
| Assignee | ||
Comment 3•3 years ago
|
||
Depends on D164931
| Assignee | ||
Comment 4•3 years ago
|
||
Depends on D164932
| Assignee | ||
Comment 5•3 years ago
|
||
Depends on D164933
Comment 7•3 years ago
|
||
| bugherder | ||
https://hg.mozilla.org/mozilla-central/rev/300945b39f81
https://hg.mozilla.org/mozilla-central/rev/0df4af33a26e
https://hg.mozilla.org/mozilla-central/rev/089548c43a16
https://hg.mozilla.org/mozilla-central/rev/3bdaef5f3363
https://hg.mozilla.org/mozilla-central/rev/0734671d309a
Description
•