Closed
Bug 370839
Opened 18 years ago
Closed 18 years ago
table properties tab control is truncated on the right when UI is RTL
Categories
(SeaMonkey :: Composer, defect)
Tracking
(Not tracked)
RESOLVED
DUPLICATE
of bug 368501
People
(Reporter: tsahi_75, Unassigned)
Details
(Keywords: rtl)
Attachments
(1 file)
27.47 KB,
image/png
|
Details |
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; he-IL; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; he-IL; rv:1.8.1.2pre) Gecko/20070111 SeaMonkey/1.1 when the interface is aligned to the right, e.g. when using a RTL language (like hebrew or arabic), the tab control in table properties dialog is truncated on its right edge. it looks like the dialog window is not wide enough to hold the tabs. Reproducible: Always Steps to Reproduce: 1. aligning the interface to the right: add these lines to the file intl.css, in the locale\en-US\global, in the en-US.jar file (the language pack file, in the chrome folder) or to your userChrome.css: window,dialog,wizard,page { direction: rtl; } menu { direction: rtl; } 2. start seamonkey 3. in composer, create a table, right click it, and select table cell properties Actual Results: table tab is truncated on the right Expected Results: all the UI should be visible. i think the solution should be either widening the dialog, or make its width controllable from the language pack, like some other dialogs.
Reporter | ||
Comment 1•18 years ago
|
||
a similar problem exists on hebrew TB 2.0b2 too.
Comment 2•18 years ago
|
||
Similar problem exists on localized LTR builds: the Table Properties dialog is being cut on the right side and cannot be resized.
Comment 3•18 years ago
|
||
Probably caused by bug 371194.
Comment 4•18 years ago
|
||
Was this fixed by bug 368501 ?
Updated•18 years ago
|
Status: UNCONFIRMED → RESOLVED
Closed: 18 years ago
Resolution: --- → DUPLICATE
Comment 6•16 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
•