Closed Bug 541799 Opened 14 years ago Closed 7 years ago

xul:radiogroup orient can't be changed by theme developers though it should

Categories

(Firefox :: Extension Compatibility, defect)

3.6 Branch
x86
Windows XP
defect
Not set
normal

Tracking

()

RESOLVED INVALID

People

(Reporter: the_herd_of_the_horses, Unassigned)

References

Details

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2) Gecko/20100115 Firefox/3.6

I probably want to make a theme which will have all pref-panes arranged vertically, like in Firefox 1:
http://www.montana.edu/resnet/setup/firefox/firefox1.jpg

Reproducible: Always

Steps to Reproduce:
1.Try to change the orient of prefpanes using userChrome.css and Google and your knowledge
2.
3.
Actual Results:  
No success because in chrome://global/content/bindings/preferences.xml
There is a line 548:
<xul:radiogroup anonid="selector" orient="horizontal"  ...
Which fixes the orient, in XML.

Expected Results:  
It's a cosmetic, appearance issue, theme developers should be able to change it, and so should I with userChrome.css

Maybe it could be harmless for Firefox code developers to write instead
<xul:radiogroup anonid="selector" style="-moz-orient:horizontal;"  ...
So that theme developers can control the orient?
You can override it with !important, can't you? The XML attribute just ends up triggering the relevant attribute selector rule in xul.css.
Nevermind, I was thinking of something else.
I tried to write the followind code in userChrome.css, and it didn't do any single change:

@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
@namespace html url("http://www.w3.org/1999/xhtml");
@namespace xbl url("http://www.mozilla.org/xbl");
radiogroup{-moz-box-orient:vertical !important;}


Which suggestions do you have?
Version: unspecified → 3.6 Branch
Legacy extensions are no longer valid in Firefox 57, closing.
Status: UNCONFIRMED → RESOLVED
Closed: 7 years ago
Resolution: --- → INVALID
You need to log in before you can comment on or make changes to this bug.