« Bugzilla Issues Index
#1629 — 12.1.1.2: Description in NOTE no longer valid and refers to wrong steps
- bug_id:
1629
- creation_ts:
2013-07-30 12:29:00 -0700
- short_desc:
12.1.1.2: Description in NOTE no longer valid and refers to wrong steps
- delta_ts:
2013-08-23 08:23:03 -0700
- product:
Draft for 6th Edition
- component:
editorial 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:
4603
- comment_count:
0
- who:
André Bargull
- bug_when:
2013-07-30 12:29:52 -0700
The second NOTE in 12.1.1.2 refers to the steps 4 and 5, but it should refer to steps 5-6 instead.
Also the second example in the second NOTE is no longer valid, because the spec has been (partially?) updated to use the completion reform semantics, so `eval("1; {}")` no longer evaluates to `1` but instead to `undefined`.
And step 4 could actually be removed, because s.[[value]] is never empty when s.[[type]] == throw.
- commentid:
4814
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2013-08-07 16:39:13 -0700
fixed the step reference.
The second example is marked with a note in the source document that points out the completion reform change. Going to leave it there for now as a point to review.
I think it's clearer in this case to be explicit about the handling of throw in step 4.
fixed in rev17 editor's draft
- commentid:
5131
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2013-08-23 08:23:03 -0700
fixed in rev17, August 23, 2013 draft