Closed Bug 23169 Opened 25 years ago Closed 25 years ago

can't insert line breaks in the middle of an existing line (plaintext)

Categories

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

Other
Other
defect

Tracking

()

VERIFIED FIXED

People

(Reporter: akkzilla, Assigned: akkzilla)

References

()

Details

Go to the bugzilla bug page. Click in the text area for long description. Type some stuff. Click back in the middle of a line you just typed. Hit return. Observe that nothing happens. There's no way to split an existing line.
Status: NEW → ASSIGNED
i noticed this worked for me, and talked to akkana about it. Turns out we see it in commercial optimized build, but not mozilla debug build. I kinda suspect this may not be an editor problem, but I'll look into it.
i did an optimized build on mac and still cant reproduce this problem. Akkana is going to try to generate a fresh opt linux build and see what happens.
Update: I have an optimized build today, and I do see the problem. I'm using printfs to track the problem down further (SplitNode is failing for some reason).
Assignee: jfrancis → akkana
Status: ASSIGNED → NEW
The problem was that result was uninitialized at the beginning of SplitNodeImpl. Isn't there any way to get the Mac build system to show uninitialized variable warnings? I see several more of these in the editor code. Taking bug -- will check in a fix as soon as I get Joe's review.
Status: NEW → ASSIGNED
Turns out Linux builds don't show this warning for debug builds (and hence they're not on the warnings page) either. I'm talking to slamm and mcafee about how we can get these warnings to show up on the warnings page.
i reviewd and approved akkana's changes. thanks akkana!
Status: ASSIGNED → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Fixed -- we fixed several more uninitialized variables while we were in there.
Status: RESOLVED → VERIFIED
verified in 1/13 build.
setting to an approximate milestone so it can be off of the no TFV list
Target Milestone: --- → M13
You need to log in before you can comment on or make changes to this bug.