windoze trunk 0409 Steps: 1 Launch composer 2 Add a 20x20 (100% width) table 3 Now, type some text in the first row first cell, some other row's first cell(in the middle maybe) and in the last cell (basically to distinguish each row) 4 Now right click in the first cell in the middle row and select 'Table Insert|Row above' 5 Observe that a row (with contents of the last row- another bug )gets added at the bottom instead of where I asked it to get added (middle)

on win98, a row gets inserted where I instructed it to be inserted and the phontom extra row at the bottom goes away if the window is minimized and then redisplayed. are you sure a row did not get inserted? can you try this on other platforms?

back to me

pls try it on this attachment(still happens) : http://bugzilla.mozilla.org/showattachment.cgi?attach_id=30202

just worked through this with shrir, the rows appear if the window is minimized and redisplayed, handiong this over to kevin, this seems like a rendering issue

cc :paw

*** Bug 75275 has been marked as a duplicate of this bug. ***

Reassigning to Karnaze. This is a table row invalidation problem.

cc:kin

This is very disconcerting to users creating tables. I found that dragging the mouse over the table where I inserted a row updates the table too. This prevents me from using the Composer in NS6.5 because it's so annoying. Nominating nsbeta1

I agree with scalkins, very disconcerting: - I create a table with 2 rows and 2 columns - Enter "1" in the first cell, first row (cursor is now to the right of "1") - Select Table|Insert|Row Above (cursor now moves to the left of "1" and a row appears added to the bottom. I try editing this cell and I can't highlight "1", I can't delete it...) - Selected Table|Select|Cell (the cell is highlighted and the text disappears) The average user will think that they lost their data.

hmm..isn't this working now(0613 trunk iwndows)...nbaca can you pls retry with a recent trunk ? Thanks!

Build 2001-06-15-14 trunk: WinMe Sorry, still seeing the problem.

This was fixed, possibly by the patch to bug 89452. wfm.

verified...