Open
Bug 668240
Opened 14 years ago
Updated 2 years ago
Refine how selection and caret affects a text-overflow marker (ellipsis)
Categories
(Core :: Layout: Block and Inline, defect)
Core
Layout: Block and Inline
Tracking
()
NEW
People
(Reporter: MatsPalmgren_bugz, Unassigned)
References
(Blocks 1 open bug)
Details
Currently we inhibit all text-overflow markers inside a block when
that block has a caret (to avoid the caret being hidden behind a marker).
This has an odd side-effect when selecting stuff in that block, as noted
in bug 666669 comment 14:
> Mats Palmgren [:mats] 2011-06-27 20:16:04 PDT
> BTW, there's kind of a funny effect when you select some text in a
> text input/area with a text-overflow marker in it. The mousedown
> (or focus rather) causes the text caret to appear and thus the marker
> is inhibited and you see the full text... then as you start dragging
> with the mouse pressed (to select text) the caret is inhibited (default
> behavior when there is a selection) so now the text-overflow marker
> appears again... so if you drag the mouse back again over the point
> where you started the selection becomes collapsed -> caret shows again
> -> marker disappears.
Here's roc's suggested solution (bug 666669 comment 16):
> Robert O'Callahan (:roc) (Mozilla Corporation) 2011-06-27 21:02:27 PDT
> Seems like the best behavior would be to suppress the marker if the caret
> *or* any selection would overlap the marker, and not suppress it otherwise.
>
> That would be useful for find-as-you-type as well, so we don't hide find
> matches behind the marker.
Updated•8 years ago
|
Blocks: text-overflow
Updated•2 years ago
|
Severity: minor → S4
You need to log in
before you can comment on or make changes to this bug.
Description
•