archives

« Bugzilla Issues Index

#1670 — 15.13.6, 15.13.7: TypedArray and DataView objects both use the same internal data property names

• bug_id: 1670
• creation_ts: 2013-07-31 05:15:00 -0700
• short_desc: 15.13.6, 15.13.7: TypedArray and DataView objects both use the same internal data property names
• delta_ts: 2013-08-23 08:23:13 -0700
• product: Draft for 6th Edition
• component: technical issue
• version: Rev 16: July 15, 2013 Draft
• rep_platform: All
• op_sys: All
• bug_status: RESOLVED
• resolution: FIXED
• priority: Normal
• bug_severity: normal
• everconfirmed: true
• reporter: André Bargull
• assigned_to: Allen Wirfs-Brock

---

• commentid: 4644
• comment_count: 0
• who: André Bargull
• bug_when: 2013-07-31 05:15:36 -0700

TypedArray and DataView objects both have internal data property names [[ViewedArrayBuffer]], [[ByteLength]], and [[ByteOffset]]. But [[ViewedArrayBuffer]] is also used to test for TypedArray resp. DataView object-ness, that means an algorithm which currently only tests for [[ViewedArrayBuffer]] can not differentiate between both kinds of objects.

For example the abstract operation for DataView objects "GetViewValue()" is currently also applicable for TypedArray objects.

Or 15.13.6.3.6 "%TypedArray%.prototype.set(array, offset = 0 )", step 11 is currently undefined because only [[ViewedArrayBuffer]] is tested on the target variable, but if target is a DataView object [[TypedArrayName]] is not present.

Or you can use the DataView constructor to perform (half-)initialisation of TypedArray objects ([[ViewedArrayBuffer]], [[ByteLength]], and [[ByteOffset]] get updated, but [[ArrayLength]] is still 0).

---

• commentid: 4987
• comment_count: 1
• who: Allen Wirfs-Brock
• bug_when: 2013-08-21 13:01:28 -0700

fixed in rev17 editor's draft

---

• commentid: 5148
• comment_count: 2
• who: Allen Wirfs-Brock
• bug_when: 2013-08-23 08:23:13 -0700

fixed in rev17, August 23, 2013 draft