Closed
Bug 569216
Opened 15 years ago
Closed 15 years ago
Cocoa progress widget should support RTL
Categories
(Core :: Widget: Cocoa, defect)
Tracking
()
RESOLVED
FIXED
People
(Reporter: mounir, Assigned: mounir)
References
Details
Attachments
(1 file, 2 obsolete files)
1.70 KB,
patch
|
mstange
:
review+
|
Details | Diff | Splinter Review |
The HTML5 progress element is going to use -moz-appearance: progressbar (see bug 567872). On MacOS X, the progress bar draw the chunks itself so we need to manage the RTL from there.
Let me know if you prefer to have a |mirrorHorizontal| parameter instead of checking inside |DrawProgress|.
Attachment #448367 -
Flags: review?(mstange)
Comment 1•15 years ago
|
||
Please use RenderTransformedHIThemeControl like DrawResizer does. That doesn't only do the horizontal mirroring for you, it also fixes rendering bugs with transformed progress bars. For example, try setting style="transform:rotate(45deg)" on a progressbar - the result will look very strange. RenderTransformedHIThemeControl gets around these bugs by painting the control into a buffer and only transforming the result.
Assignee | ||
Comment 2•15 years ago
|
||
It looks like RenderTransformedHIThemeControl does not do the drawing where it should.
Comment 3•15 years ago
|
||
I think you need to pass aRenderRect to HIThemeDrawTrack where you're passing NULL.
Assignee | ||
Comment 4•15 years ago
|
||
Attachment #448367 -
Attachment is obsolete: true
Attachment #448373 -
Attachment is obsolete: true
Attachment #448375 -
Flags: review?(mstange)
Attachment #448367 -
Flags: review?(mstange)
Updated•15 years ago
|
Attachment #448375 -
Flags: review?(mstange) → review+
This could use a test.
Status: ASSIGNED → RESOLVED
Closed: 15 years ago
Flags: in-testsuite?
Keywords: checkin-needed
Resolution: --- → FIXED
Comment 8•15 years ago
|
||
Mounir, you can look at http://hg.mozilla.org/mozilla-central/rev/074779c640fb for the reftests from the rtl resizer bug. They're basically just doing direction:rtl == -moz-transform:scaleX(-1).
You need to log in
before you can comment on or make changes to this bug.
Description
•