Open
Bug 475190
Opened 16 years ago
Updated 2 years ago
Need -moz-border-radius-(top|bottom)(start|end) or -moz-border-(top|bottom)-(start|end)-radius for RTL
Categories
(Core :: CSS Parsing and Computation, defect)
Core
CSS Parsing and Computation
Tracking
()
NEW
People
(Reporter: philor, Unassigned)
References
(Blocks 1 open bug)
Details
For the flat parts of borders, we have the very handy -moz-border-start and -moz-border-end to make things work out in RTL locales, but because -moz-border-radius- only has topleft etc., rounded corners that aren't left-right symmetric require hacking around with separate chromedir="rtl" selectors. It would be much nicer to have -moz-border-radius-topstart (or to have CSS3 backgrounds hit CR, have bug 451134 fixed, and have -moz-border-top-start-radius, but fixing this shouldn't depend on that just because topstart is ugly).
I tend to think we probably just want (before|after)-(start|end) and we don't want properties with mixed physical and logical directions, although I'm not sure.
Updated•14 years ago
|
Blocks: border-radius
Comment 2•9 years ago
|
||
While there are border-{block,inline}-{start,end}-* in http://dev.w3.org/csswg/css-logical-props/ there aren't border-radius properties.
border-block-start-inline-end-radius is a pretty awful name, though
Updated•2 years ago
|
Severity: normal → S3
You need to log in
before you can comment on or make changes to this bug.
Description
•