Incorrect accented character typing for first accented character in a page

RESOLVED INCOMPLETE

Status

()

Firefox
General
RESOLVED INCOMPLETE
9 years ago
7 years ago

People

(Reporter: Sérgio Gomes, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Whiteboard: [closeme 2010-10-01])

(Reporter)

Description

9 years ago
User-Agent:       Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2
Build Identifier: Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.5; en-US; rv:1.9.1b2) Gecko/20081201 Firefox/3.1b2

When typing an accented character with a deadkey, e.g., "´" + "e" to produce "é", the first time that any such combination is pressed in a page, it will render both characters separately, instead of rendering the composite character, e.g., "´" + "e" becomes "´e" instead of "é". For any subsequent typing in the same page, this works correctly.

Reproducible: Always

Steps to Reproduce:
1. Go to a page with text fields, e.g. www.google.com. If you are already there, refresh the page.
2. Type any deadkey + character combination to get an accented character, e.g., "´" + "e"
Actual Results:  
Two separate characters (an accent and a regular character) are produced on the text field. In the example above, "´e".

Expected Results:  
An single, accented character should have appeared on the text field; in the example above, "é".

Subsequent typing on the same page works correctly. After refreshing or changing page, the same problem occurs for the first character.

Did not happen in any 3.0 release I've tried, but does happen in 3.1b2 OSX.

Comment 1

7 years ago
do you see this problem in version 3.6?
Whiteboard: [closeme 2010-10-01]
No reply, INCOMPLETE. Please retest with Firefox 3.6.10 or later and a new profile (http://support.mozilla.com/kb/Managing+profiles). If you continue to see this issue with the newest firefox and a new profile, then please comment on this bug.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 7 years ago
Resolution: --- → INCOMPLETE
You need to log in before you can comment on or make changes to this bug.