Caret disappears when pressing up arrow to arrive left of image.

VERIFIED WORKSFORME

Status

()

VERIFIED WORKSFORME
14 years ago
14 years ago

People

(Reporter: stephend, Unassigned)

Tracking

Trunk
x86
Windows XP
Points:
---

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(3 attachments, 1 obsolete attachment)

(Reporter)

Description

14 years ago
Build ID: 2005-06-21-05, Windows XP Seamonkey trunk.

Summary: Caret disappears when pressing up arrow to arrive left of image.

Steps to Reproduce:

1. Load the attached testcase.
2. Click to focus in-between the two Netscape images.
3. Press the up arrow (this makes the caret arrive left of the 1st image).

Expected Results:

Caret blinks

Actual Results:

Caret disappears.  To verify that indeed we have a caret, begin typing and
you'll see the caret blink.  Must be killing the timer here?
(Reporter)

Comment 1

14 years ago
Created attachment 186976 [details]
Testcase

Open in Composer and follow the testcase given in comment 0.
(Reporter)

Comment 2

14 years ago
Created attachment 186977 [details]
1st image for testcase
(Reporter)

Comment 3

14 years ago
Created attachment 186978 [details]
2nd image for testcase
(Reporter)

Comment 4

14 years ago
Created attachment 186979 [details]
Revised testcase (use remote images rather than broken local)
Attachment #186976 - Attachment is obsolete: true
This WFM starting from the 2005-06-29-07 build (but not on 2005-06-28-10).
I couldn't find which patch fixed it, so resolving WORKSFORME.

Would be nice if someone can confirm.
Status: NEW → RESOLVED
Last Resolved: 14 years ago
Resolution: --- → WORKSFORME
(Reporter)

Comment 6

14 years ago
And for me too.  No idea what fixed this.  There is still a problem with order
of the cursor's movement (there are two spaces, and if you start from the
right-most image, it goes to the 1st space, instead of the 2nd space (which is
closest to the right-most image), but someday I'll file that separately...
Status: RESOLVED → VERIFIED
You need to log in before you can comment on or make changes to this bug.