User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 If you set Firefox to have Hebrew as the highest language preference and view a site such as Gmail (others were observed) and enter a username/password, the textbox is correctly aligned right to left (RTL). However, on returning and beginning to enter the same string, the auto-complete dropdown is incorrectly aligned left to right (LTR). This problem becomes even more noticeable when you use a mixture of RTL and LTR characters such as Hebrew and English. Reproducible: Always Steps to Reproduce: 1.Navigate to a website that supports Hebrew (such as Gmail). Make sure the XP has Hebrew regional settings enabled as well as English. 2.In the username textbox, begin entering "שדגכ"(this string can be entered by switching XP's keyboard to Hebrew and then hitting the keys "asdf". 3.Then switch back to English and type the letters "gh". 4.In the textbox, the input will be correctly displayed as "ghשדגכ" and will be aligned on the right hand side (see screenshot). 5.Type in any password and hit enter to attempt to login. Note, it is ok that this is not real login info, since the point is to get auto-complete to pick up the input. 6.When the page reloads reporting an unrecognized username/password, begin repeating steps 2 and 3 so that the auto-complete dropdown menu appears. Actual Results: Instead of displaying the test as "ghשדגכ" (RTL) the text will be displayed as "שדגכgh" with the english characters displayed on the right hand side. Also this text is incorrectly aligned on the left hand side of the dropdown (see screenshot). Expected Results: The English characters should be displayed to the left of the Hebrew characters (since they were entered left and text is input RTL). Also in the autocomplete dropdown the text should be displayed on the left hand side of the dropdown.

Although this is a screenshot of Gmail, this bug occurs on other sites that correctly support Hebrew.

Thank you for this report. Though it covers a known issue.