Closed
Bug 1576076
Opened 5 years ago
Closed 4 months ago
Latin1 strings: Add a Latin1 flavor of JSExternalString
Categories
(Core :: JavaScript Engine, enhancement, P3)
Core
JavaScript Engine
Tracking
()
RESOLVED
FIXED
122 Branch
Tracking | Status | |
---|---|---|
firefox122 | --- | fixed |
People
(Reporter: hsivonen, Assigned: arai)
References
Details
Attachments
(2 files, 1 obsolete file)
To enable buffer sharing of DOM ByteString
, let's add a Latin1 flavor of JSExternalString
.
Updated•5 years ago
|
Priority: -- → P3
Assignee | ||
Comment 1•3 years ago
|
||
Updated•2 years ago
|
Severity: normal → S3
Updated•5 months ago
|
Attachment #9232384 -
Attachment is obsolete: true
Assignee | ||
Comment 2•5 months ago
|
||
In order to avoid confusion and collision with Latin1 flavor, rename existing
APIs to use UC prefix.
Latin1 flavor usually doesn't have any prefix/suffix, but the next patch uses
ExternalStringLatin1, to avoid another confusion with current UTF-16 APIs.
Updated•5 months ago
|
Assignee: nobody → arai.unmht
Status: NEW → ASSIGNED
Assignee | ||
Comment 3•5 months ago
|
||
Adds:
- JS_NewExternalStringLatin1
- JS_NewMaybeExternalStringLatin1
- IsExternalStringLatin1
- latin1 methods for JSExternalStringCallbacks
Depends on D194672
Pushed by arai_a@mac.com: https://hg.mozilla.org/integration/autoland/rev/4b98a0b46db4 Part 1: Rename existing ExternalString APIs to use ExternalUCString. r=sfink https://hg.mozilla.org/integration/autoland/rev/90b59d83622d Part 2: Support Latin1Char in JSExternalString. r=sfink
Comment 5•4 months ago
|
||
bugherder |
https://hg.mozilla.org/mozilla-central/rev/4b98a0b46db4
https://hg.mozilla.org/mozilla-central/rev/90b59d83622d
Status: ASSIGNED → RESOLVED
Closed: 4 months ago
status-firefox122:
--- → fixed
Resolution: --- → FIXED
Target Milestone: --- → 122 Branch
You need to log in
before you can comment on or make changes to this bug.
Description
•