Firefox 2 does not recognize profile userChrome.css
Jeff
are ignored by Firefox. I know I am in the correct folder:
C:\Documents and Settings\_myusername_\Application
Data\Mozilla\Firefox\Profiles\3up4n94n.default\chrome
Is there something I can do to find out why Firefox is ignoring my
userChrome.css file? Something in about:config I m ay have inadvertantly
changed or asomething else?
Would aqpreciate any help.
Here is my userChrome.css file contents:
/*
* Edit this file and copy it as userChrome.css into your
* profile-directory/chrome/
*/
/*
* This file can be used to customize the look of Mozilla's user interface
* You should consider using !important on rules which you want to
* override default settings.
*/
/*
* Do not remove the @namespace line -- it's required for correct
functioning
*/
@namespace
url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul"); /* set
default namespace to XUL */
/*
* Some possible accessibility enhancements:
*/
/*
* Make all the default font sizes 20 pt:
*
* * {
* font-size: 20pt !important
* }
*/
/*
* Make menu items in particular 15 pt instead of the default size:
*
* menupopup > * {
* font-size: 15pt !important
* }
*/
/*
* Give the Location (URL) Bar a fixed-width font
*
* #urlbar {
* font-family: monospace !important;
* }
*/
/*
* Eliminate the throbber and its annoying movement:
*
* #throbber-box {
* display: none !important;
* }
*/
/* Multi-row bookmarks toolbar */
#bookmarks-ptf {display:block}
#bookmarks-ptf toolbarseparator {display:inline}
/*
* For more examples see http://www.mozilla.org/unix/customizing.html
*/
Would apreciate any help. I've previously made other changes which have
similarly been ignored.
Jeff
Peter Potamus the Purple Hippo
the file must be saved as a text file, and you must restart FF.
--
Peter Potamus & His Magic Flying Balloon:
http://www.toonopedia.com/potamus.htm
http://www.bcdb.com/cartoon/46347-Peter_Potamus_Show.html
http://www.toonarific.com/show.php?s_search=Potamus&Button_Update=Search&show_id=2778
Please do not email me for help. Reply to the newsgroup only. Thanks
Peter Potamus the Purple Hippo
> Jeff wrote:
>> Since I upgraded to Firefox 2, any changes I make to my userChrome.css
>> file are ignored by Firefox. I know I am in the correct folder:
>> C:\Documents and Settings\_myusername_\Application
>> Data\Mozilla\Firefox\Profiles\3up4n94n.default\chrome
>>
>> Is there something I can do to find out why Firefox is ignoring my
>> userChrome.css file? Something in about:config I m ay have
>> inadvertantly changed or asomething else?
>>
>> Would aqpreciate any help.
>>
>> Here is my userChrome.css file contents:
>>
>> have similarly been ignored.
>>
>> Jeff
>>
>
> the file must be saved as a text file, and you must restart FF.
>
also, why do you have all those * there and you've got them in the wrong
place. Try this and see if it works any better:
@namespace
url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
/* Make all the default font sizes 20 pt: */
{
font-size: 20pt !important
}
/* Make menu items in particular 15 pt instead of the default size: */
menupopup > * {
font-size: 15pt !important
}
/* Give the Location (URL) Bar a fixed-width font */
#urlbar {
font-family: monospace !important;
}
/* Eliminate the throbber and its annoying movement: */
#throbber-box {
display: none !important;
}
/* Multi-row bookmarks toolbar */
#bookmarks-ptf {display:block}
#bookmarks-ptf toolbarseparator {display:inline}
--
Ed Mullen
1. The @namespace line(s) can be deleted
2. Everything is commented out except the "Multi-row bookmarks ..."
3. What the heck are all those extraneous "*"?
4. The userContent.css file should be edited while FF is NOT running.
Make your edits THEN run FF.
5. Create a new clean profile. Copy your userContent.css file into the
chrome folder of that profile. Run Profile Manager and start FF using
that new profile.
Report back.
--
Ed Mullen
http://edmullen.net
http://mozilla.edmullen.net
http://abington.edmullen.net
David McRitchie
> 3. What the heck are all those extraneous "*"?
The extra asterisks are to make sure you know
that it is commented out because it is all within
/* comment delimiters */
It is copied directly from the userChrome-example.css
One person had a problem because he did not expand
the name column as seen in File manager that is was
userChrome-example.css and was not userChrome.css
It is rather curious that the only code that was active
was the code for bookmarks tab that seems to give
inconsistent results regardless of coding.
Irwin Greenwald
--
Irwin
Please do not use my email address to make requests for help.
Knowledge Base: http://kb.mozillazine.org/Main_Page
Jeff
"Peter Potamus the Purple Hippo" <peter.potamus.t...@gmail.com>
wrote in message news:jKKdnbjF7dqVGVLY...@mozilla.org...
Did that, more than once. Even rebooted.
Jeff
Jeff
The only part I added (and does not work) is
/* Multi-row bookmarks toolbar */
#bookmarks-ptf {display:block}
#bookmarks-ptf toolbarseparator {display:inline}
The rest is the example userChrome.css and they have * because they are
supposed to be ignored.
I also once added
/* Change color of active tab */
tab{
-moz-appearance: none !important;
}
tab[selected="true"] {
background-color: rgb(195,212,195) !important;
color: navy !important;
}
/* Change colour of normal tabs */
tab:not([selected="true"]) {
color: gray !important;
}
to the userChrome.css and it too was ignored so I gave up on it. Used to
work in an earlier Firefox on another PC.
Jeff
Jeff
"David McRitchie" <nospam@nospam> wrote in message
news:8rKdnQewtZYjC1LY...@mozilla.org...
I did not know that. But I had the same problem when I added
/* Change color of active tab */
tab{
-moz-appearance: none !important;
}
tab[selected="true"] {
background-color: rgb(195,212,195) !important;
color: navy !important;
}
/* Change colour of normal tabs */
tab:not([selected="true"]) {
color: gray !important;
}
That was also ignored and I finally gave up. Actually, it created a fine
redline around the active tab, which did not help much. It used to work in
Firefox on another PC running XP.
I did not try creating a new profile. Will try that.
Jeff
Jeff
OK
> 2. Everything is commented out except the "Multi-row bookmarks ..."
> 3. What the heck are all those extraneous "*"?
except for the "Multi-row bookmarks" part everything else is the
exampleuserChrome.css which I left as is in case I might need them later.
> 4. The userContent.css file should be edited while FF is NOT running.
Did that.
> Make your edits THEN run FF.
Did that.
> 5. Create a new clean profile. Copy your userContent.css file into the
> chrome folder of that profile. Run Profile Manager and start FF using
> that new profile.
That I did not do. Will do that now. Hope it helps.
> Report back.
>
> --
> Ed Mullen
Thanks. Jeff
Jeff
(Sorry for the long message)
OK, I created a new profile folder (with Firefox completely off), copied the
files from my old default profile into it. Edited my userChrome.css (using
notepad) so that it now includes:
/* Multi-row bookmarks toolbar */
#bookmarks-ptf {display:block}
#bookmarks-ptf toolbarseparator {display:inline}
/* Change color of active tab */
tab{
-moz-appearance: none !important;
}
tab[selected="true"] {
background-color: rgb(195,212,195) !important;
color: navy !important;
}
/* Change colour of normal tabs */
tab:not([selected="true"]) {
color: gray !important;
}
Booted into the new profile. Still no effect in Firefox 2. I am working in
XP Media Center Edition, SP 2 in a laptop with a duo Intel T2050 CPU in case
that has a bearing.
Earlier when I was trying to get the
/* Change color of active tab */ part
to work, I tried all sorts of things and even uninstalled all extensions and
rebooted and that did not help either.
It is not that important <grin>, but I asked again in case someone else may
have encountered this problem and might have some suggestions.
Jeff
Tony Mechelynck
Can't you read? It says right there (in the userChrome-example.css) that it
can't. There is a reason for that: I think that @namespace line is related to
the difference between chrome and content.
> 2. Everything is commented out except the "Multi-row bookmarks ..."
Yes. That is intentional.
> 3. What the heck are all those extraneous "*"?
They are part of comments.
> 4. The userContent.css file should be edited while FF is NOT running.
No matter. I've edited it many times while Firefox was running, including with
the ChromEdit or MR-Tech Local Install extensions. Firefox reads it at startup
and never writes it so it's no problem. And on my system, userChrome.css works
(and always has for as long as I've used it), in all three of Thunderbird,
Firefox and SeaMonkey.
What souldn't be edited while Firefox is running is the prefs.js, because
Firefox writes that one at shutdown.
> Make your edits THEN run FF.
> 5. Create a new clean profile. Copy your userContent.css file into the
> chrome folder of that profile. Run Profile Manager and start FF using
> that new profile.
>
> Report back.
>
Jeff, are you sure of your selectors? I tried to find that ID "bookmarks-ptf"
but got a crash so I can't be sure.
Best regards,
Tony.
--
"Pascal is not a high-level language."
-- Steven Feiner
Tony Mechelynck
Well, just FYI, here Firefox does change the colour of the active tab, except
of course when both (a) the tab is no bigger than the favicon due to crowding,
and (b) the favicon has no transparent areas. You can see (or download) a copy
of my userChrome.css at
http://users.skynet.be/antoine.mechelynck/other/userChrome.css
I think your "tab" selector is in error. It should be .tabbrowser-tabs *|tab
Best regards,
Tony.
--
hundred-and-one symptoms of being an internet addict:
25. You believe nothing looks sexier than a man in boxer shorts illuminated
only by a 17" inch svga monitor.
Jeff
"Tony Mechelynck" <antoine.m...@belgacom.net> wrote in message
news:HPqdnSy-ypklQVLY...@mozilla.org...
Thank you very much. I will try your userChrome.css and report back.
What does it do to the active tab so I know what to look for?
Jeff
Jeff
No I am not sure of any of this. I got this code from messages on this
newslist and entered it as instructed <grin> I am no programmer.
Jeff
> Best regards,
> Tony.
Ed Mullen
> "Ed Mullen" <e...@edmullen.net> wrote in message
>> 3. What the heck are all those extraneous "*"?
>
> The extra asterisks are to make sure you know
> that it is commented out because it is all within
> /* comment delimiters */
Well, umm, ok. But, if you actually know what that everything in
between /* this */ is a comment, all you're doing is giving yourself a
lot more crap to edit out should you want to activate those lines. I'm
into simple. :-) YMMV
Ed Mullen
> Ed Mullen wrote:
>> 1. The @namespace line(s) can be deleted
>
> Can't you read?
Yes. (That sounded a tad testy, Tony. Did I offend you in some way?)
> It says right there (in the userChrome-example.css) that
> it can't. There is a reason for that: I think that @namespace line is
> related to the difference between chrome and content.
You /think/ it is needed? Well, can't /you/ *test*? Take it out and
see what happens. And go to the page and examine the source. Does it
do anything to MY installation of FF? I'm happy to be convinced
otherwise but I see no functional purpose (other than promotional) for
that reference and page.
Tony Mechelynck
[...]
> Thank you very much. I will try your userChrome.css and report back.
>
> What does it do to the active tab so I know what to look for?
>
> Jeff
Gives it a greyish-blue background colour (#699 which is short for #669999
i.e. red 40%, green 60%, blue 60%).
Best regards,
Tony.
--
"I'm fed up to the ears with old men dreaming up wars for young men to
die in."
-- George McGovern
Tony Mechelynck
> Tony Mechelynck wrote:
>> Ed Mullen wrote:
>>> 1. The @namespace line(s) can be deleted
>>
>> Can't you read?
>
> Yes. (That sounded a tad testy, Tony. Did I offend you in some way?)
You didn't. You just sounded as if you were unable or unwilling to read what
was laid out in plain English in a comment just above that @namespace line.
>
>> It says right there (in the userChrome-example.css) that it can't.
>> There is a reason for that: I think that @namespace line is related to
>> the difference between chrome and content.
>
> You /think/ it is needed? Well, can't /you/ *test*? Take it out and
> see what happens. And go to the page and examine the source. Does it
> do anything to MY installation of FF? I'm happy to be convinced
> otherwise but I see no functional purpose (other than promotional) for
> that reference and page.
>
Did you test all possible cases? Of course not. The Mozilla programmers put
that line there for a reason. My guess (but it's only a guess) is that with
that line present, chrome privileges are not extended to "content" code (I
notice that the userContent-example.css has no @namespace line, for instance).
Since I don't understand the reason why the gurus inserted that line, I don't
play smart: if it protects against something, I don't want to wait wide-open
for that something to hit me -- better safe than sorry.
I went to the page and looked at the source, but since I don't know the
meaning of @namespace it doesn't tell me much anyway.
Best regards,
Tony.
--
The Kennedy Constant:
Don't get mad -- get even.
Sailfish
as intuited here:
http://books.mozdev.org/html/mozilla-chp-2-sect-2.html#mozilla-CHP-2-EX-3
Thus, HTML, CSS or mis-spelled XUL should trigger an error. I believe
that is the reason why theme subskins require that their CSS @import
statement be placed prior to the @namespace statement.
--
Sailfish - Netscape/Mozilla Champion
Netscape/Mozilla Tips: http://www.ufaq.org/ , http://ilias.ca/
mozilla-based Themes: http://www.projectit.com/freestuff.html
Brian Heinrich
> Tony Mechelynck wrote:
>> Ed Mullen wrote:
>>> 1. The @namespace line(s) can be deleted
>>
>> Can't you read?
>
> Yes. (That sounded a tad testy, Tony. Did I offend you in some way?)
>
>> It says right there (in the userChrome-example.css) that it can't.
>> There is a reason for that: I think that @namespace line is related to
>> the difference between chrome and content.
>
> You /think/ it is needed? Well, can't /you/ *test*? Take it out and
> see what happens. And go to the page and examine the source. Does it
> do anything to MY installation of FF? I'm happy to be convinced
> otherwise but I see no functional purpose (other than promotional) for
> that reference and page.
AFAIK, the @namespace URL simply defines a namespace. In other words, the
@namespace declaration tells Gecko to parse (e.g.) CSS declarations in
userContent.css as belonging the the XUL namespace.
/b.
--
People are stupid. /A/ person may be smart, but /people/ are stupid.
--Stephen M. Graham
Brian Heinrich
<snip />
> My guess (but it's only a guess) is
> that with that line present, chrome privileges are not extended to
> "content" code (I notice that the userContent-example.css has no
> @namespace line, for instance).
Which makes perfect sense, since userChrome.css affects the chrome, which is
within the XUL namespace.
/b.
<snip />
squaredancer
generate the following:? :
> "Tony Mechelynck" <antoine.m...@belgacom.net> wrote in message
> news:JI6dnYRBcOywTlLY...@mozilla.org...
>
>> Ed Mullen wrote:
>>
>>> Jeff wrote:
>>>
>>>
>> Jeff, are you sure of your selectors? I tried to find that ID
>> "bookmarks-ptf" but got a crash so I can't be sure.
>>
>
> No I am not sure of any of this. I got this code from messages on this
> newslist and entered it as instructed <grin> I am no programmer.
>
> Jeff
>
>
Hah, Jeff! reckon you're in for a big surprise, as to what your future
hobby will be *lol*
"Happy Programming" is all I can say! 8-)
reg