Closed Bug 475834 Opened 13 years ago Closed 13 years ago
/**/ comments with newlines in them do not act as line breaks
This matters in automatic semicolon insertion in ES3. Doug Crockford pointed this out and said only Opera follows the spec. We should make the fix, as I doubt it will break anyone and it is easy -- and anyway the spec is better than the bug. /be
This was the most obvious way to do it.
Assignee: general → mrbkap
Status: NEW → ASSIGNED
Attachment #359410 - Flags: review?(brendan)
Attachment #359481 - Flags: review?(brendan) → review+
Safe ride-along for 3.1, gets us right with jslint and other analyzers. /be
Comment on attachment 359481 [details] [diff] [review] Better [Checkin: Comment 8 & 9] Shouldn't need much baking -- pls. get it into tm and m-c asap. /be
Status: ASSIGNED → RESOLVED
Closed: 13 years ago
Flags: wanted1.9.1? → wanted1.9.1+
Resolution: --- → FIXED
This seems well-baked for 1.9.1. /be
Attachment #359481 - Attachment description: Better → Better [Checkin: Comment 8 & 9]
Needs approval1.9.1 before checkin-needed.
Whiteboard: fixed-in-tracemonkey → [needs 1.9.1 landing] fixed-in-tracemonkey
Target Milestone: --- → mozilla1.9.2a1
Whiteboard: [needs 1.9.1 landing] fixed-in-tracemonkey → fixed-in-tracemonkey
You need to log in before you can comment on or make changes to this bug.