Closed
Bug 292376
Opened 20 years ago
Closed 20 years ago
No RTL aligment possible in "plain" textbox
Categories
(Firefox :: General, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: dyahalom, Unassigned)
References
()
Details
(Keywords: rtl)
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7.7) Gecko/20050414 Firefox/1.0.3 The plain textbox (either single line or multi line) used in most sites (such as Gmail's compose new messege page or even the bugzilla enter a bug page) which FireFox renders doesn't allow you to switch text editing directions - from LTR to RTL. This means RTL text enterd into the textbox (such as Hebrew text) will always be LTR aligned (Hebrew is an RTL lang). It is worthy to note that certain other browsers, such as IE, allow you to swtich text directions using the Shift+Ctrl combination. This is probably becuase IE users the Windows OS generic textbox (that supports RTL) while Firefox uses it's own that doesn't? Reproducible: Always Steps to Reproduce: 1.Enter the compose a new messege page in Gmail. 2.In the messege body textbox, try switching the direction of the text to RTL (by using Shift+Ctrl for example). 3.try writing some text. Actual Results: The text will be LTR aligned and not RTL aligned Expected Results: The text should be RTL aligned - as required by BiDi langs.
Comment 1•20 years ago
|
||
This was fixed in Firefox 1.0, and you should be able to switch the text direction by pressing Ctrl+Shift+x inside the text box. you may also need to enable this option on you're system. to do this: 1. type about:config in the address bar. 2. right click somewhere inside the window and select New-> Boolean-> bidi.browser.ui-> true. this should enable this option on you're system.
Status: UNCONFIRMED → RESOLVED
Closed: 20 years ago
Resolution: --- → WORKSFORME
Comment 2•17 years ago
|
||
Mass-assigning the new rtl keyword to RTL-related (see bug 349193).
Keywords: rtl
You need to log in
before you can comment on or make changes to this bug.
Description
•