Closed Bug 42112 Opened 24 years ago Closed 24 years ago

hitting return in TEXTAREA doesn't have effect immediately

Categories

(Core :: Layout: Form Controls, defect, P1)

defect

Tracking

()

VERIFIED FIXED

People

(Reporter: ekrock, Assigned: mjudge)

References

Details

(Keywords: regression, Whiteboard: [nsbeta2+])

Using Commercial 2000060908 on WinNT 4.0 SP4.

To repro:
1) in a bugzilla report description, type a few characters, then hit return


Expected: I bar moves to next line

Actual: I bar remains on current line; if you then type a space, both the return
and the space suddenly take effect
Nom. dogfood. This is making it very hard to use the daily build for bugzilla usage.
Keywords: dogfood
This regressed between the win98 mozilla builds of 06-08 and 06-09.  cc:ing
mjudge (who I believe turned on Ender lite during that time period).
Keywords: regression
Putting on [nsbeta2+][dogfood-] radar.  Does not need a fix ASAP for daily work, 
but we should fix this for beta2.
Whiteboard: [nsbeta2+][dogfood-][w/b minus on 6/15]
Assignee: rods → mjudge
reassigning
asking Joe to take a quick look at this to see if there is anything he can do to 
help.
Assignee: mjudge → jfrancis
Upgrading platform and OS to 'All'.

PDT: please leave nsbeta2+.  Forms are everywhere, people use them, and will be 
_quite_ unhappy about this bug, possibly to the point of not using the product.  
OS: Windows NT → All
Hardware: PC → All
accepting bug
Status: NEW → ASSIGNED
setting to m16 where all + bugs live
Target Milestone: --- → M16
6/15 has passed... cleaning up whiteboard and setting as nsbeta2 minus. Folks 
are too doomed to handle this bug for beta2. Note that it appears that bugzilla 
etc. are usable, it is just that user-feedback after a ENTER is pressed is not 
provided until the next chanacter is typed.
Since this is a bothersome regression, I'm putting in a beta3 nomination
Keywords: nsbeta2, nsbeta3
Whiteboard: [nsbeta2+][dogfood-][w/b minus on 6/15] → [nsbeta2-][dogfood-]
I agree with ckritzer's comments, and I am clearing the [nsbeta2-] for 
reevaluation (it was previously [nsbeta2+][6/15] -- see jar's comments).  This 
bug is painfully obvious (and often very confusing) to anyone who fills out a 
form with a textarea, and it will make the beta look very bad (and discourage 
many people from using it).
Whiteboard: [nsbeta2-][dogfood-] → [dogfood-]
This is an odd bug.  It only happens in ender lite.  I have to jumnp through some 
hoops when you type a return at the end of a block: I have to out in two break 
nodes to generate the blank line that users expect.  When I step through the code 
here and examine the content afterwards, everything looks correct.  

Yet there is no blank line.  But the second br is there.

I'm going to have to get with Mike on this one: it's either a selection problem 
or a layout problem, I beleive.
moving out to m17, removed dogfood and nsbeta2 keywords
Keywords: dogfood, nsbeta2
Whiteboard: [dogfood-]
Target Milestone: M16 → M17
Process note: when one person has cleared the [nsbeta2-] to trigger nsbeta2 
re-evaluation, another person should not clear the nsbeta2 keyword.

I agree completely with ckritzer and dbaron. HTML forms are used everywhere on 
the Internet. It is unacceptable to ship a Netscape Beta 2 with this 
disconcerting behavior. End users will hate it, and reviewers will justly slam 
us for it. PDT may have decided that this is not dogfood, but it's definitely a 
beta 2 stopper. Restoring nsbeta2 keyword to trigger re-evaluation for beta2, 
and cc:ing johng, Navigator PM, for further comments.

PDT team: if you're considering not fixing this for beta 2, please call John and 
me into the meeting to discuss.
Keywords: nsbeta2
nsbeta2+
Whiteboard: [nsbeta2+]
assigningto mjudge to get it on his radar.  Mike, I'll help you with this when 
I get back from MacHack on monday.
Assignee: jfrancis → mjudge
Status: ASSIGNED → NEW
updated priority and severity
Severity: normal → critical
Priority: P3 → P1
*** Bug 43967 has been marked as a duplicate of this bug. ***
This is a dup of the 'caret doesn't move on return' bug, I think.
Assignee: mjudge → jfrancis
*** Bug 42483 has been marked as a duplicate of this bug. ***
I'm not sure why Simon assigned this back to me, but Mike investigated and 
discovered this is a selection problem.  moving over to mike cuz he's da MAN!

Besides, as part of a team building exercise we are all moving our bugs over to 
mike...
Assignee: jfrancis → mjudge
fixed.
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
Judge, yo da man.
Marking VERIFIED FIXED on:
- MacOS9 2000-07-06-08-M17 Commercial
- Linux6 2000-07-07-10-M17 Commercial
- Win98  2000-07-07-13-M17 Commercial
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.