Closed
Bug 523041
Opened 15 years ago
Closed 2 years ago
-moz-border-radius doesn't drop native theming
Categories
(Core :: Layout: Form Controls, defect)
Tracking
()
RESOLVED
WORKSFORME
People
(Reporter: gargantulakon, Unassigned)
References
(Blocks 1 open bug)
Details
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.0; en-US; rv:1.9.1.3) Gecko/20090824 Firefox/3.5.3 (.NET CLR 3.5.30729) -moz-border-radius and -webkit-border-radius do similar things but when I use it in a form textarea, it only works on the webkit engine. It should work for Mozilla too since it is my favorite browser. I wonder if other fields do not work, but I found this one so far. Reproducible: Always Steps to Reproduce: 1. Set a style with -moz-border-radius: 10px on a textarea 2. Since that the textarea does not have round corners. 3. Use -webkit-border-radius: 10px on a textarea for Safari and see that it works. Actual Results: No round corners Expected Results: Round corners
![]() |
||
Comment 1•15 years ago
|
||
You can presumably make this work by setting "-moz-appearance: none", but should we be dropping native theming for border-radius like we do for border-width/color/style?
Status: UNCONFIRMED → NEW
Ever confirmed: true
![]() |
||
Updated•15 years ago
|
Summary: Custom CSS codes works in webkit, but not Mozilla → -moz-border-radius doesn't drop native theming
Comment 2•15 years ago
|
||
Perhaps. Should the list of things that we drop native theme for include just what's required for Web compatibility, be anything anybody asks for, or be something in between (and if so, what)? I'd like to avoid having the list grow too long, though adding additional border properties does make some sense.
![]() |
||
Comment 3•15 years ago
|
||
Good question. In some sense, anything we don't honor while native theming is enabled should be considered for dropping it...
That principle makes a lot of sense to me.
Comment 5•15 years ago
|
||
What about all the things that we don't honor on form controls with or without native theming? And what happens when we change that list?
Reporter | ||
Comment 6•15 years ago
|
||
Cool, thanks. Using "-moz-appearance: none" does work, but I needed to add "border: solid 1px #000" and "padding: 5px;" too so that it looks just like the Web kit one does. Without it, a funky "3D" effect appears. It is interesting since on this page, it states that the initial value is none. I hope these round corners make it to CSS3.
Reporter | ||
Comment 7•15 years ago
|
||
When I mentioned this page, I meant: https://developer.mozilla.org/en/CSS/-moz-appearance
Reporter | ||
Comment 8•15 years ago
|
||
I think I get it now. The textarea is probably set to "-moz-appearance: menulist-textfield" by default.
![]() |
||
Comment 9•15 years ago
|
||
> What about all the things that we don't honor on form controls Yeah, that's why I wasn't entirely sure of my comment 3 suggestion...
Updated•15 years ago
|
Blocks: border-radius
Updated•2 years ago
|
Severity: trivial → S4
Comment 12•2 years ago
|
||
In-content native theming is gone
Status: NEW → RESOLVED
Closed: 2 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•