Closed Bug 230109 Opened 22 years ago Closed 10 years ago

text cursor is visible only when it (really) blinks

Categories

(Core :: XUL, defect)

x86
Windows XP
defect
Not set
minor

Tracking

()

RESOLVED WORKSFORME

People

(Reporter: komka_p, Unassigned)

Details

User-Agent: Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.1; .NET CLR 1.0.3705) Build Identifier: Mozilla Thunderbird 0.4 (20031205) In XP it is possible to set the blinking rate to "no blink" ("zero"). In that case, the cursor does not appear. (At least in fields like "To" and "Subject".) One does not know, in which field he is. (Until types some letters.) Reproducible: Always Steps to Reproduce: 1. in XP control panel / keyboard, set blinking speed to "0" (no blinking) 2. press Ctrl-M (new letter) Actual Results: you are in the "To" field -- but it turns out only when you pressed a letter.. Expected Results: visible cursor (as in the body area)
I have mine set to blink and I still seem to have the "no cursor" (I-beam) problem sometimes, also; I noticed it last night working in the Address Book of Mozilla Suite; this is probably an issue that affects both. Haven't isolated the problem. (BTW, I was using a classic-style theme. Maybe this doesn't happen in Modern?)
This appears to be a problem with text fields in chrome but not in content. Another place where this fails is the browser URLbar. Confirmed with Thunderbird 0.6 and SeaMonkey 1.7 branch build 2004051108.
Assignee: mscott → mozeditor
Status: UNCONFIRMED → NEW
Component: Message Compose Window → Editor: Core
Ever confirmed: true
Product: Thunderbird → Browser
QA Contact: bugzilla
Version: unspecified → Trunk
->toolkit
Assignee: mozeditor → jag
Component: Editor: Core → XP Toolkit/Widgets
QA Contact: bugzilla → jrgmorrison
I see this bug in Firefox 1.5.0.4 as well.
Assignee: jag → nobody
Has anyone noticed this lately? I haven't on either OS X (which I've been using a lot of) or Windows (with occasional use) ... granted, that would be in Firefox these days and not the suite as when I noticed this problem many years ago, but I think it showed up in both, anyway. Otherwise, unless anyone still sees this, I think we could WORKSFORME it.
Per my previous comment six years ago, I'm going to resolve this. I'm guessing it was fixed somewhere along the line with many changes that have been made since this time since it WORKSFORME and presumably does for anyone else who hasn't commented since this time.
Status: NEW → RESOLVED
Closed: 10 years ago
Resolution: --- → WORKSFORME
You need to log in before you can comment on or make changes to this bug.