User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b) Gecko/20030210 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.3b; MultiZilla v220.127.116.11) Gecko/20030210 The keyboard does not work properly in this page: https://home.citidirect-br.citibank.com/citidirect/servlet/SvCtIndex This page is supposed to provide a virtual keyboard so you do not type your passowrd directly. But the virtual keyboard is only for the Password field (in Brazilian portuguese called "Senha"). The other fields should be write enabled, and should be filled with the bank data of the user (card name). I am not being able to type into any of the text fields. Reproducible: Always Steps to Reproduce: 1. Access the page https://home.citidirect-br.citibank.com/citidirect/servlet/SvCtIndex 2. try to type into any fields Actual Results: nothing :) Expected Results: text typed should have apeared into the text boxes, esxcept for the "senha" text box, which should not be accessible (an error popup message should display if typing into this field).
Yup, I can't get it to work at all. No virtual keyboard, no text going in! Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.4a) Gecko/20030324
I see it too on Linux 2003032305.
I see it too, but you can TAB into the creditcard field if you selected an option from the dropdown list. If this is Mozilla's bug and not poor coding than it should not be component Browser=general but Form controls I think.
Hello. Can any of you reproduce this bug with Citibank Brasil in a recent Mozilla build? I just went there using the 20030924 build and was able to successfully use the virtual keyboard, as well as fill in the other fields that the keyboard does not apply to. It looks like either Mozilla or Citibank fixed the problem. Thank you for any new information.
I get about the same behaviour in MSIE6 as in Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.6b) Gecko/20031217 The "citicard" field is obviously only for numbers, which I can type in directly, without problems (although in Mozilla, the Delete key doesn't work there). So... I'm not sure if this really is a bug.
Now that the crashing bug is fixed I can properly test this, and it seems to work now. Closing as worksforme, but feel free to reopen if it does not work in a recent build.