« Bugzilla Issues Index
#396 — Completion [[value]] empty or undefined?
- bug_id:
396
- creation_ts:
2012-06-16 16:16:00 -0700
- short_desc:
Completion [[value]] empty or undefined?
- delta_ts:
2012-09-28 12:54:56 -0700
- product:
Draft for 6th Edition
- component:
technical issue
- version:
Rev 8: June 15, 2012 Draft
- rep_platform:
All
- op_sys:
All
- bug_status:
RESOLVED
- resolution:
FIXED
- priority:
Normal
- bug_severity:
normal
- everconfirmed:
true
- reporter:
Rick Waldron
- assigned_to:
Allen Wirfs-Brock
- cc:
waldron.rick
- commentid:
1033
- comment_count:
0
- who:
Rick Waldron
- bug_when:
2012-06-16 16:16:45 -0700
Newly added Completions are using:
Completion {[[type]]: continue, [[value]]: undefined, [[target]]: empty}.
...While existing Completions used:
Completion {[[type]]: continue, [[value]]: empty, [[target]]: empty}.
Perhaps this is intended?
- commentid:
1186
- comment_count:
1
- who:
Allen Wirfs-Brock
- bug_when:
2012-07-08 16:21:18 -0700
Yes, it should be emptry in the cases where a break is thrown
fixed in editor's draft
- commentid:
1774
- comment_count:
2
- who:
Allen Wirfs-Brock
- bug_when:
2012-09-28 12:54:56 -0700
fixed in rev10, Sept. 27 2012 draft