Closed Bug 17887 Opened 25 years ago Closed 25 years ago

[M11 BLOCKER] Editor: Enter/Return key doesn't insert carraige return

Categories

(Core :: DOM: Editor, defect, P1)

Product:
Core
Component:
DOM: Editor
Type:
defect

Tracking

()

Status:
VERIFIED FIXED

People

(Reporter: cpratt, Assigned: joki)

Details

Build ID: 1999110308 (Win32), 1999110309 (Linux, Mac OS)
Platform: all

To reproduce:
- Launch the browser
- Select File | New | Edit Blank Page
- Start typing. Press Enter/Return every so often.

Result: No carraige returns are inserted/generated; you keep typing on the same
line.

Expected result: Enter/Return should insert a line feed/carraige return.
Assignee: beppe → joki
Severity: normal → blocker
Priority: P3 → P1
Summary: Editor: Enter/Return key doesn't insert carraige return → [M11 BLOCKER] Editor: Enter/Return key doesn't insert carraige return
looks like joki made some changes last night -- assigning to him
Rebuilding fix now.  Will check in as soon as it finishes and I get permission.
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Ok fixed.  Sorry about that one.  I've been looking at that spec for months and
assuming all the values were the same as ours.  But you know what they say
about assuming, you make... ah forget it.  Marking fixed.
I've built with joki's changes and I still see the problem.
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
based on mscott comments, reopening
Status: REOPENED → RESOLVED
Closed: 25 years ago → 25 years ago
Resolution: --- → FIXED
I'm still asserting this is fixed.  There was some confusion right after the
checkin, it worked for some people or mac, linux, and windows but not for
others.  I think its a build issue.  If it still shows up in tomorrows release
builds I'll take another look.
looks fixed to me in 11/4 builds..I just want Pratt to double check...

Chris, go ahead and close this out if it works for you now...
Status: RESOLVED → VERIFIED
verified in 11/4 build. PRatt verify also...
Passed by retest on Linux / 11-04-08 build. It's working fine now.
You need to log in before you can comment on or make changes to this bug.