default theme disallows customizing userChrome.css

RESOLVED EXPIRED

Status

()

Firefox
General
RESOLVED EXPIRED
14 years ago
10 years ago

People

(Reporter: Zack, Assigned: Arvid Axelsson)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

Attachments

(2 attachments)

(Reporter)

Description

14 years ago
User-Agent:       Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.5) Gecko/20031007 Firebird/0.7
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040402 Firefox/0.8.0+

using different themes is a semi workaround, but then I like the firefox default
theme :-) so it probably has to do with the theme, I would try and fix it
myself, but I am not into making themes enough, nor do I have time right now.

Reproducible: Always
Steps to Reproduce:
1.make the userContent.css file, change the background like they show you how at
http://texturizer.net/firefox/tips.html#app_toolbarbackground
2.feel free to add a few more elements that the style is supposed to apply to
3.start firefox and notice it only comming up with the background applied to the
"menubar" when it should be applied to several other places.

Actual Results:  
comes up with the background only applied to the "menubar" when it should be
applied to several other places.


Expected Results:  
it should be applied to several other places. like
menupopup, toolbox, toolbar, .tabbrowser-tabs


changing themes is a little bit of a workaround (I tried 2 others, they worked
fine), but I like the default theme.
(Reporter)

Comment 1

14 years ago
I am sure someone is going to think that I reported for firebird .7, but I only
typed it up and subbmitted it on firebird .7
I tested it on:
Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.7b) Gecko/20040402 Firefox/0.8.0+

Comment 2

14 years ago
I think you mean userChrome.css, not userContent.css.
Summary: default theme murdered customizing userContent.css → default theme murdered customizing userChrome.css
(Reporter)

Comment 3

14 years ago
(In reply to comment #2)
> I think you mean userChrome.css, not userContent.css.
oh, yes you are correct.
I wrote that and then I think I copied and pasted.... Sorry, and thanks Jesse

Updated

14 years ago
Assignee: firefox → arvid
(Reporter)

Updated

14 years ago
Summary: default theme murdered customizing userChrome.css → default theme disallows customizing userChrome.css

Comment 4

14 years ago
Do you have the following line at the top of your userChrome.css?
@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");

Comment 5

14 years ago
Does this happen to be the same bug that prevents fonts specified in userChrome.css (in Mozilla 1.7rc1) not to be applied, only the colors?

See comments 11,from RKAa, and 59, from myself, about bug 237407.

http://bugzilla.mozilla.org/show_bug.cgi?id=237407

(I never had the @namespace directive mentioned above in userChrome.css.),
(Reporter)

Comment 6

14 years ago
Created attachment 147674 [details]
the userChrome.css file used
(Reporter)

Comment 7

14 years ago
(In reply to comment #4)
> Do you have the following line at the top of your userChrome.css?
> @namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");

yes, after the comments, but look for yourself.
I could also attach a screen shot if anyone thinks that would be useful.
(Reporter)

Comment 8

14 years ago
(In reply to comment #5)
> Does this happen to be the same bug that prevents fonts specified in
userChrome.css (in Mozilla 1.7rc1) not to be applied, only the colors?
> 
> See comments 11,from RKAa, and 59, from myself, about bug 237407.
> 
> http://bugzilla.mozilla.org/show_bug.cgi?id=237407
> 
> (I never had the @namespace directive mentioned above in userChrome.css.),
hmm, they do look a lot alike, I assume that you have tried this with the
classic theme, correct? and, did it work as expected?
Created attachment 153398 [details]
a simple userChrome.css test

Confirmed using Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7)
Gecko/20040707 Firefox/0.9.2, local file C:\Documents and
Settings\Mithgol\Application Data\Mozilla\Profiles\default\[secret random
keystroke].slt\chrome\userChrome.css

Several really simple tricks from http://texturizer.net/firefox/tips.html do
not work. And switching browser themes does not help (neither standard nor
Pinball theme).

I am attaching userChrome.css as a testcase in hope this helps.

By the way, I feel that bug summary needs to be updated (because this bug seems
to happen even when the theme is not default). Do you feel the same?
(Reporter)

Comment 10

13 years ago
yes, the summary should be updated. I called it the 'default' theme as a name
(because "firefox" is not a very clear name, unlike "Qute" or "Silver Skin" )

Any suggestions for what exactly to change the summary to?
This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/
This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.
Status: UNCONFIRMED → RESOLVED
Last Resolved: 12 years ago
Resolution: --- → EXPIRED
You need to log in before you can comment on or make changes to this bug.