Caret invisible when using a input/textarea/designmode placed on a DIV placed after a FIXED DIV.

RESOLVED WORKSFORME

Status

()

Firefox
General
RESOLVED WORKSFORME
11 years ago
11 years ago

People

(Reporter: Dirk Schippers, Unassigned)

Tracking

({testcase})

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(1 attachment)

(Reporter)

Description

11 years ago
User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; nl; rv:1.8.1.3) Gecko/20070309 Firefox/2.0.0.3

I've seen several posts about invisible carets but none of them really fits what I am experiencing.

I created some kind of javascript user interface that generates divs with content on them.

These divs (position: absolute) are added after a fixed div (for design's sake).
Whenever a div is above this fixed div, the caret becomes invisible on any type of input-field (text, password, textarea, designmode) that is put on that div.

When the input field is not completely over the fixed div, the part that is not, does have a visible caret.

This example shows the problem, try to edit the field and move the caret over the fixed div:

<div id="somefixeddiv" style="position:fixed;top:0px;left:0px;width:120;height:500;background-color:#000000;visibility: visible;">
</div>

<div id="fiets" style="position: absolute;top: 100px;left: 100px;width: 200px;height: 200px;background-color: #400000;">
<input type="text" name="wortel" value="fietsen is gezond">
</div>

Reproducible: Always
Created attachment 261946 [details]
testcase from comment 0

I see the caret issue in
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.8.1.4pre) Gecko/2007041304 BonEcho/2.0.0.4pre

No caret issue in
Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.9a4pre) Gecko/20070417 Minefield/3.0a4pre ID:2007041704 [cairo]

Updated

11 years ago
Keywords: testcase
I don't know when this was fixed, but it's fixed on the trunk, so --> WORKSFORME
Status: UNCONFIRMED → RESOLVED
Last Resolved: 11 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.