Open
Bug 394157
Opened 17 years ago
Updated 4 years ago
Cannot move caret to beginning of text if 1st element has -moz-user-select: all
Categories
(Core :: DOM: Editor, defect, P5)
Core
DOM: Editor
Tracking
()
NEW
People
(Reporter: Techrazy.Yang, Unassigned)
References
Details
(Keywords: regression, testcase)
Attachments
(2 files)
I use Editor element to compose my own editor in which some text are atoms. In the attachment is a test case extension. In the extension, there is an editor looking like a input box. And in the editor, there are two span element "Item1","Item2". In Firefox2, the cursor can be moved to the most left side of the editor by arrow key. But in Firefox3, the cursor can not. So, I think this is some bugs in the editor element of Gecko.
The attachment is the test extension. Please install it in both Firefox2 and Firefox3, you will find the difference. Thanks!
Comment 1•17 years ago
|
||
Bo, it would be ideal if you could provide a minimized testcase that didn't require extension installation. For example, you could provide a XUL document that contained an editor and loaded an example document into the editor (perhaps with a data: URL).
Yeah, this is clearly a regression and a bad one.
Severity: normal → major
Status: UNCONFIRMED → NEW
Ever confirmed: true
Keywords: regression
OS: Windows XP → All
Hardware: PC → All
Summary: Different behaviors of Editor element between Firefox 3 and Firefox 2 → Cannot move caret to beginning of text if 1st element has -moz-user-input
Version: 1.8 Branch → Trunk
And please notice that can not move the caret to the beginning of the text is not the only bug. The caret can't move to the beginning of any SPAN node at all. Neither does in Firefox 2. I think this is a bug too.
Comment 4•17 years ago
|
||
Comment 5•17 years ago
|
||
This seems to have regressed between 2006-04-18 and 2006-04-20:
http://bonsai.mozilla.org/cvsquery.cgi?treeid=default&module=all&branch=HEAD&branchtype=match&dir=&file=&filetype=match&who=&whotype=match&sortby=Date&hours=2&date=explicit&mindate=2006-04-18+10&maxdate=2006-04-20+08&cvsroot=%2Fcvsroot
Probably a regression from bug 235223(although bug 334256 might be the culprit, instead).
It doesn't seem like something bug 235223 would cause, although I could be wrong. Probably worth testing backouts of both potential causes...
Comment 7•4 years ago
|
||
Bulk-downgrade of unassigned, 4 years untouched DOM/Storage bugs' priority.
If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.
Severity: major → S4
Priority: -- → P5
You need to log in
before you can comment on or make changes to this bug.
Description
•