If you think a bug might affect users in the 57 release, please set the correct tracking and status flags for Release Management.

JSON acceptance tests should include multibyte codepoint string literals

NEW
Assigned to

Status

Tamarin
Library
P3
minor
6 years ago
6 years ago

People

(Reporter: pnkfelix, Assigned: Dan Schaffer)

Tracking

unspecified
Q1 12 - Brannan
Bug Flags:
flashplayer-injection -
flashplayer-qrb +
flashplayer-bug +

Details

(Whiteboard: loose-end)

Follow up work for Bug 673039.

As discussed at: http://en.wikipedia.org/wiki/UTF-8
(and also in diagrams within our code, such as above _analyzeUtf8 in StringObject.cpp), UTF-8 code points can be represented by multibyte sequences up to 6 bytes in length.

We neglected to include any cases beyond the 1 byte case.  (Whoops.)  Bug 673039 illustrates a 2 byte case.  But it would be best to cover each of the 5 cases beyond the single byte cases (and preferably tickle the edges between the cases).
(Reporter)

Updated

6 years ago
Blocks: 673039
(Reporter)

Updated

6 years ago
Assignee: nobody → fklockii
(Reporter)

Updated

6 years ago
Status: NEW → ASSIGNED
Note that the description at the UTF-8 wikipage of the different multi-byte encoding cases is talking about a range going up to 31 bits, but a unicode escape sequence \uNNNN can represent at most 16 bits.

I'm not a unicode expert.  I'm currently assuming I'll be using surrogate pairs to construct cases for 0x10000 and above.  (Still reading.)
(Reporter)

Updated

6 years ago
Status: ASSIGNED → NEW
See Also: → bug 676235

Comment 2

6 years ago
Dan, include in your i9 work.
Assignee: fklockii → dschaffe
Flags: flashplayer-qrb+
Flags: flashplayer-injection-
Flags: flashplayer-bug+
Priority: -- → P3
Whiteboard: loose-end
Target Milestone: --- → Q1 12 - Brannan
You need to log in before you can comment on or make changes to this bug.