Closed
Bug 97633
Opened 25 years ago
Closed 24 years ago
After selecting text in first cell of a table and typing over the text the text jumps above table
Categories
(SeaMonkey :: Composer, defect)
SeaMonkey
Composer
Tracking
(Not tracked)
VERIFIED
WORKSFORME
mozilla1.1alpha
People
(Reporter: TucsonTester2, Assigned: cmanske)
References
Details
From Bugzilla Helper:
User-Agent: Mozilla/5.0 (Windows; U; Win98; en-US; rv:0.9.3+) Gecko/20010828
Netscape6/6.1b1
BuildID: 20010828
After I selected the text in the first cell of the table and then typed over it
the text jumped out of the table.
Reproducible: Always
Steps to Reproduce:
1.Open composer
2.Insert a default table - 2x2 100% width
3.Type some text in the first cell (top right cell)
4.Highlight the text in the cell from right to left using the mouse and then
type over it.
Actual Results: The text jumps out of the table onto the line above. I could
not reproduce this bug using the arrow keys and the shift key to highlight the
text or by highlighting from left to right using the mouse. Because of this it
seems the highlighting goes out of the table, but it shouldn't have to be so
exact as to keep the highlighting within the table.
Expected Results: The text should stay in the table and appear in the cell I
was typing in regardless of how I highlight it.
This actually isn't an editor backend bug ... the only way I could reproduce the
problem was to select the text and move the mouse across the top left cell to
outside the left edge of the table. Doing that means that you've selected from
the content inside the top-right cell and everything between it to where you
released the mouse button (outside the table). The act of typing over that kind
of selection means that the new content will go wherever the selection collapsed
to after the delete of the selected content ... in this case, outside the table.
It sounds to me like the user may be expecting selection to be constrained to
the cell that they initialy clicked in. If so, then this is a table selection
issue for cmanske and mjudge.
brade, what do you want to do about this bug?
| Reporter | ||
Comment 3•25 years ago
|
||
Yep that is exactly what I am looking for. I would think that the selection
would be a little more constrained to the cell. Right now the margin you have
for error is not very large. In order to make sure I don't have anything
outside of the table selected, I have to make sure the cursor is an I-beam, but
a large amount of users are not going to know to look for that. Also when the
selection does go out of the table it is not visible, there are no highlighted
areas outside of the table showing.
Comment 4•25 years ago
|
||
Reassign to cmanske to coordinate with mjudge when he returns.
Perhaps we shouldn't allow users to type (no deletion occurs; we beep?) when
cells are selected (which will be the new behavior)?
Assignee: kin → cmanske
Status: UNCONFIRMED → NEW
Ever confirmed: true
| Assignee | ||
Comment 5•25 years ago
|
||
Please note that no "cells are selected" in the description of the bug.
This is another example of the kind of behavior that will be solved by changing
to "cell selection mode" when cursor is dragged outside a cell (bug 98558).
If that is fixed as desired, the cell border will become selected and the text
outside the table will not be selectable. That strong visual cue will tell the
user that they have strayed outside the cell, and they can drag back into the cell
if their intention is to select cell contents and not entire cell(s).
| Assignee | ||
Comment 9•24 years ago
|
||
Since bug 98558 is fixed, you can no longer select as orginally described.
When you drag across a cell border, the entire cell will be selected,
so you don't see the described behavior
Status: ASSIGNED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
Updated•21 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•