Closed Bug 1140645 Opened 10 years ago Closed 10 years ago

[RTL] -moz-padding-end/-moz-padding-start inconsistent between LTR & RTL mode for buttons

Categories

(Core :: Layout, defect)

defect
Not set
normal

Tracking

()

RESOLVED DUPLICATE of bug 1010675

People

(Reporter: mikehenrty, Unassigned)

References

Details

Below is a minimum case that reproduces. When in LTR mode, the text will align to the left of the element, and no amount of padding will push it any further. When in RTL mode, the text will be pushed out of the element by the large padding values. The exact opposite happens for -moz-padding-start. <!doctype html> <html lang="en" dir="rtl"> <head> <meta charset="utf-8"> <title>blah</title> <style type="text/css"> .inner { -moz-padding-end: 100px; width: 110px; border: 1px solid black; } </style> </head> <html> <body> <button class="inner">**Text**</button> </body> </html>
Blocks a blocker. Jonathan, any idea what's going on here?
blocking-b2g: --- → 2.2+
Flags: needinfo?(jfkthame)
The situation is further illuminated if you set overflow: hidden, and text-overflow: ellipsis. It looks like the measurements for where the available space is for text is wrong. I hope that helps.
Seems fixed by bug 1010675, unless I misunderstand.
Yes, AFAICS bug 1010675 will fix this. The RTL case then behaves analogously to LTR, with the button growing beyond its specified width once the padding is large enough to require this. The behavior of buttons that have "excessive" padding still seems a bit odd to me, and we probably want to avoid designs that depend on this, but at least it'll be more consistent. So I think we should start by getting 1010675 fixed, and then see if there are remaining issues that can be improved at all.
Flags: needinfo?(jfkthame)
Depends on: 1010675
dup to bug 1010675 based on Comment 3, 4
Status: NEW → RESOLVED
blocking-b2g: 2.2+ → ---
Closed: 10 years ago
Resolution: --- → DUPLICATE
You need to log in before you can comment on or make changes to this bug.