« Bugzilla Issues Index
#734 — 15.13.7.4: "the result of calling the SetValueInBuffer internal operation"
- bug_id:
734
- creation_ts:
2012-10-05 19:19:00 -0700
- short_desc:
15.13.7.4: "the result of calling the SetValueInBuffer internal operation"
- delta_ts:
2013-07-15 17:03:39 -0700
- product:
Draft for 6th Edition
- component:
editorial issue
- version:
Rev 10: September 27, 2012 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
Michael Dyck
- assigned_to:
Allen Wirfs-Brock
- commentid:
1864
- comment_count:
0
- who:
Michael Dyck
- bug_when:
2012-10-05 19:19:52 -0700
In 15.13.7.4 "Properties of the DataView Prototype Object",
in the definition of SetValue(),
steps 5 and 6 say:
5. Let value be the result of calling the SetValueInBuffer internal operation
(2.5.2) with arguments ...
6. Return value
But SetValueInBuffer doesn't return a value, so change
"Let value be the result of calling"
to just "Call", and delete step 6.
- commentid:
1865
- comment_count:
1
- who:
Michael Dyck
- bug_when:
2012-10-05 19:26:14 -0700
(Also, delete the "(2.5.2)" or change it to "(15.13.6.5.2)".)
- commentid:
2232
- comment_count:
2
- who:
Michael Dyck
- bug_when:
2012-10-27 11:04:23 -0700
From the DataView.prototype.set* methods, it looks like the intent is that SetValue() *does* return a value. In which case, you can drop my suggestion to delete step 6, but everything else still stands.
- commentid:
4285
- comment_count:
3
- who:
Allen Wirfs-Brock
- bug_when:
2013-06-23 13:12:00 -0700
SetValueInBuffer now returns a completion value.
fixed in rev 13 editor's draft
major dataview updates in rev 16
- commentid:
4431
- comment_count:
4
- who:
Allen Wirfs-Brock
- bug_when:
2013-07-15 17:03:39 -0700
fixed in rev16 draft. July 15, 2013