Closed
Bug 428854
Opened 17 years ago
Closed 15 years ago
Caret turd in this case when pressing backspace twice
Categories
(Core :: Layout, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: martijn.martijn, Unassigned)
References
()
Details
(Keywords: regression, testcase)
Attachments
(2 files)
See testcase, to reproduce:
- Position the caret in the testcase at the top of where the vertical red dotted lines start
- Press backspace
- Press another time the backspace key, but make sure the blinking caret is just in the visible state
In that case, you get to see a caret **** in current trunk build.
This regressed between 2008-03-29 and 2008-03-30:
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=2008-03-29+04&maxdate=2008-03-30+09&cvsroot=%2Fcvsroot
I guess a regression from bug 421353, somehow.
I saw this bug on GMail, in rich text mode, with double quoted text.
Reporter | ||
Comment 1•17 years ago
|
||
This does the pressing of the delete key automatically. You need to download this file and the testcase to your computer, because of the use of enhanced privileges.
Comment 2•17 years ago
|
||
Did you mean the caret is positioned to wrong points? I'm not sure this is my regression...
Comment 3•17 years ago
|
||
(In reply to comment #2)
> Did you mean the caret is positioned to wrong points? I'm not sure this is my
> regression...
mmmm, I can reproduce the wrong caret position issue on 3-28 build, so, you didn't mean this issue... I cannot understand what is a problem.
Comment 4•17 years ago
|
||
er, ok. I can reproduce the non-erased caret issue. But I still have no idea...
Reporter | ||
Comment 5•17 years ago
|
||
Yeah, I meant with caret **** == non-erased caret.
Comment 6•15 years ago
|
||
-> WFM
I cannot reproduce this bug on current trunk build.
Status: NEW → RESOLVED
Closed: 15 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•