Closed
Bug 140763
Opened 22 years ago
Closed 7 years ago
toolbar is offset by a pixel when UI aligned to the right
Categories
(Core :: Layout: Text and Fonts, defect)
Tracking
()
RESOLVED
INVALID
People
(Reporter: tsahi_75, Unassigned)
Details
Attachments
(1 file)
25.41 KB,
image/gif
|
Details |
build ID: 2002041711 (Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.0rc1) Gecko/20020417) Description: when the interface is aligned to the right, e.g. when using a RTL language (like hebrew or arabic), the toolbar is offset to the left by one pixel comparing to the other bars at the top of the Navigator window. this also happens with all other components (mailnews, addressbook, editor). 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): window,dialog,wizard,page { direction: rtl; } menu { direction: rtl; } outliner { direction: rtl; } 2. start mozilla 3. observe the toolbar Expected results: all toolbars should be aligned one under the other, including the collapse handle Actual results: toolbar collapse handle is offset to the left by one pixel comparing to the rest of the bars.
Reporter | ||
Comment 1•22 years ago
|
||
Comment 2•21 years ago
|
||
Reporter: does this still happen in modern moz builds?
Reporter | ||
Comment 3•21 years ago
|
||
this still happens with mozilla 1.3.
Reporter | ||
Comment 5•21 years ago
|
||
still here in mozilla 1.5. can anyone point me as to where to look for the problem?
Component: Layout: BiDi Hebrew & Arabic → Layout: Text
QA Contact: zach → layout.fonts-and-text
Updated•13 years ago
|
Assignee: mozilla → nobody
Reporter | ||
Comment 6•13 years ago
|
||
for the record, i've stopped localizing SeaMonkey some time ago, and i don't know where this stands today.
Reporter | ||
Comment 7•7 years ago
|
||
this bug is irrelevant by now. 16 years. so much time has passed.
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•