323019 - textbox and textarea insertion point not visible

Status: RESOLVED INCOMPLETE

(Firefox :: General, defect)

Description

[Robert Lee]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8) Gecko/20051111 Firefox/1.5

The insertion point for the textboxes and textarea disappears on some sites. An example is http://www.okcupid.com/ but others may by affected as well. It is very inconsistant across sites but I can reproduce the behaviour every time on okcupid on my machine.

Reproducible: Always

Steps to Reproduce:
1. Logon to Okcupid.
2. Find somebody online to instant message
3. Have an IM conversation with them using the built in site IM.

Actual Results:  
The textarea in the IM will work normally except that the insertion point will not be displayed.

Expected Results:  
The insertion point will appear any time the textarea has focus.

That textarea has wrap=virtual. But the other textboxes on the same page at the same time also fail to show a cursor.

Comment 1

[Adam Guthrie]

Do you have a more-accessible URL where this bug is displayed?

Comment 2

[Robert Lee]

(In reply to comment #1)
> Do you have a more-accessible URL where this bug is displayed?
> 

No sorry I don't. It may have something to do with rtl insertion points (text carot). That site uses direction:rtl for layout on some objects and the rtl insertion point appears in the text-box in question. This site also uses AJAX for sending and receiving text with this textarea. But so far I have seen no other web page with the disappearing cursor including pages using AJAX and rtl. Based on the design on their site, I'm sure they are inadvertantly doing something to cause this.

-Robert

Comment 3

[Steve England [:stevee]]

Reporter, do you still see this problem with the latest Firefox 2? If not, can you please close this bug as WORKSFORME. Thanks!

Comment 4

[Carsten Book [:Tomcat]]

Closing as INCOMPLETE due to lack of updates. Please reopen if you're still
seeing this issue. It would be great if you could attach a testcase or a url where we don`t need a login account.