436771 - cannot type the letters t, h, c, or v.

Status: RESOLVED WORKSFORME

(Firefox :: General, defect)

Description

[Veritas]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008052901 Minefield/3.0pre
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008052901 Minefield/3.0pre

I am having to write this in notepad and copy/paste it back into minefield.  This is by far the weirdest bug I have ever seen.  I simply cannot type the letters t, h, c, or v into the address bar, or on a field entry on a page, etc.  It is seemingly reproducible, although I am going to restart my computer after I submit the bug to see if that helps.  I CAN clearly type into all other programs without problem. InTeresTingly, iT will allow THose leTTers if THe sHifT key is pressed.

Reproducible: Always

Steps to Reproduce:
1.
2.
3.
Actual Results:  
expeCTed To be able To Type wHaT i wanT To, buT iT is Very messed up.

Expected Results:  
well, the above sentence shouldn't need to have capital letters in it...

umm....... THis needs To go away.

Comment 1

[Veritas]

using Version :: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008052901 Minefield/3.0pre

Comment 2

[Ria Klaassen (not reading all bugmail)]

Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9pre) Gecko/2008053106 Minefield/3.0pre

This works fine for me: t, h, c, v. Maybe an extension is causing this? 

Comment 3

[Veritas]

you are using a different release candidate.  the new release Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9pre) Gecko/2008053106 Minefield/3.0pre - which is the one you are using, fixes the error.

Comment 4

[Ria Klaassen (not reading all bugmail)]

FIXED means a patch was attached to correct the bug. WORKSFORME seems more appropriate in this case.

Comment 5

[Veritas]

Fair enough -- but I would suggest it has nothing to do with me/you in particular.  It was clearly a bug that was introduced and solved by the dev team between the two builds listed.

Comment 6

[Ria Klaassen (not reading all bugmail)]

In that case you'd need to mention exactly the number of the bug that fixed the problem and make it dependent or mark it as a duplicate of that bug.