Closed
Bug 1120503
Opened 11 years ago
Closed 11 years ago
Fix seal/freeze for typed arrays
Categories
(Core :: JavaScript Engine, defect)
Tracking
()
RESOLVED
FIXED
mozilla38
Tracking | Status | |
---|---|---|
firefox38 | --- | fixed |
People
(Reporter: jorendorff, Assigned: evilpies)
References
(Blocks 1 open bug)
Details
Attachments
(1 file)
3.89 KB,
patch
|
Waldo
:
review+
|
Details | Diff | Splinter Review |
> // Typed arrays are always sealed.
> *resultp = true;
> } else {
> // Typed arrays cannot be frozen, but an empty typed array is
> // trivially frozen.
Jeff pointed out that neither comment is true anymore (bug 1112778 comment 22).
Assignee | ||
Comment 1•11 years ago
|
||
In theory we just need to remove the if (IsAnyTypedArray(obj)) block and add some tests.
Assignee | ||
Updated•11 years ago
|
QA Contact: evilpies
Assignee | ||
Updated•11 years ago
|
Assignee: nobody → evilpies
QA Contact: evilpies
Assignee | ||
Comment 2•11 years ago
|
||
As I suggested, this just removes the special code for typed arrays. I added some tests that makes sure we still consider non-extensible empty arrays as sealed and frozen. And some other cases like that non-empty arrays are never frozen, because the elements always stay writable.
Attachment #8564258 -
Flags: review?(jwalden+bmo)
Updated•11 years ago
|
Attachment #8564258 -
Flags: review?(jwalden+bmo) → review+
Assignee | ||
Comment 4•11 years ago
|
||
Comment 5•11 years ago
|
||
Status: NEW → RESOLVED
Closed: 11 years ago
status-firefox38:
--- → fixed
Flags: in-testsuite+
Resolution: --- → FIXED
Target Milestone: --- → mozilla38
You need to log in
before you can comment on or make changes to this bug.
Description
•