UserChrome.css Issue
Tempuser
the Chrome folder) has no affect on the TB interface?
Running TB 2.0.0.23 under Mac OS 10.6.2 (late 2009 21.5" screen iMac)
with a screen resolution set to 1920x1080. There is no user.js file in
the profile.
This is the entire content of the css file.
/* Menu font */
menu, menulist, menuitem {
font-family: Arial !important;
font-size: 14pt !important;
}
Ron K.
The file is missing key info. This is required to be in the file before any
style rules.
@namespace
url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
--
Ron K.
Who is General Failure, and why is he searching my HDD?
Kernel Restore reported Major Error used BSOD to msg the enemy!
Tempuser
> Tempuser on 11/20/2009 11:30 AM, keyboarded a reply:
>> Does anyone know why the following contents of the userchrome.css (in
>> the Chrome folder) has no affect on the TB interface?
>>
>> Running TB 2.0.0.23 under Mac OS 10.6.2 (late 2009 21.5" screen iMac)
>> with a screen resolution set to 1920x1080. There is no user.js file in
>> the profile.
>>
>> This is the entire content of the css file.
>>
>> /* Menu font */
>> menu, menulist, menuitem {
>> font-family: Arial !important;
>> font-size: 14pt !important;
>> }
>
> The file is missing key info. This is required to be in the file before
> any style rules.
>
> @namespace
> url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
>
>
/*
* Do not remove the @namespace line -- it's required for correct
functioning */
/* set default namespace to XUL */
@namespace
url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
/*
* Menu font
menu, menulist, menuitem {
font-family: Arial !important;
font-size: 14pt !important;
}
*/
Ron K.
You have now commented out the style rule. Use of "/*" and "*/" signal
comments, and You now hive Your rule braceted by these so it is being ignored.
Tempuser
/*
* 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 */
/* set default font */
Tempuser
properly. The first part that sets the colors of tiered replies works,
but the section that changes the font for the compose window is not
working. The reply font is a serif (I assume Times Roman).
/*
* Quote Levels Colors
blockquote[type=cite] {
color: navy !important; background-color: RGB(245,245,245) !important;
}
blockquote[type=cite] blockquote {
color: maroon !important; background-color: RGB(235,235,235) !important;
}
blockquote[type=cite] blockquote blockquote {
color: green !important; background-color: RGB(225,225,225) !important;
}
blockquote[type=cite] blockquote blockquote blockquote {
color: purple !important; background-color: RGB(215,215,215) !important;
}
blockquote[type=cite] blockquote blockquote blockquote blockquote {
color: teal !important; background-color: RGB(205,205,205) !important;
}
*/
/*
* The following code changes the font to Arial in the compose window.
BODY
{
font-family: Arial !important;
font-size: 100% !important;
}
*
Beauregard T. Shagnasty
> I just noticed that the usercontent.css file is also not working
> properly. The first part that sets the colors of tiered replies
> works, but the section that changes the font for the compose window
> is not working. The reply font is a serif (I assume Times Roman).
If that was an exact copy'n'paste of your file, it'll never work.
Everything is commented out!
/* Everything between these is a comment */
--
-bts
-Friends don't let friends drive Windows
Nir
I guess there is a syntax problem somewhere in your userChrome.css code.
An easiest way to find the source of the problem is to check for errors
in Error console. It will give the details of problems in userChrome.css
hacks. So just start Tb and check the errors in error console.
Tempuser
the context menus (right click or cmd click) are using 14pt but
the names of the accounts and messages remain at a fixed point size.
/* 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 font */
menu, menulist, menuitem {
font-family: Arial !important;
font-size: 14pt !important;
}================================================================
UserContent.css contains the following and it works just fine.
/* Quote Levels Colors */
blockquote[type=cite] {
color: navy !important; background-color:
RGB(245,245,245) !important;
}
blockquote[type=cite] blockquote {
color: maroon !important; background-color:
RGB(235,235,235) !important;
}
blockquote[type=cite] blockquote blockquote {
color: green !important; background-color:
RGB(225,225,225) !important;
}
blockquote[type=cite] blockquote blockquote blockquote {
color: purple !important; background-color:
RGB(215,215,215) !important;
}
blockquote[type=cite] blockquote blockquote blockquote
blockquote {
color: teal !important; background-color:
RGB(205,205,205) !important;
}
/* The following code changes the font to Arial in the compose
window. */
Tempuser
I should have said Ctrl Click not Cmd Click.
Ken Whiton
*-* In Article <no6dnWz2qf3X_pXW...@mozilla.org>,
*-* Tempuser wrote
*-* About Re: UserChrome.css Issue
> Nir wrote:
>> On Friday 20 November 2009 10:00 PM, Tempuser wrote:
>>> Does anyone know why the following contents of the userchrome.css
>>> (in the Chrome folder) has no affect on the TB interface?
>>>
>>> Running TB 2.0.0.23 under Mac OS 10.6.2 (late 2009 21.5" screen
>>> iMac) with a screen resolution set to 1920x1080. There is no
>>> user.js file in the profile.
>>>
>>> This is the entire content of the css file.
>>>
>>> /* Menu font */
>>> menu, menulist, menuitem {
>>> font-family: Arial !important;
>>> font-size: 14pt !important;
>>> }
>
>> I guess there is a syntax problem somewhere in your userChrome.css
>> code. An easiest way to find the source of the problem is to check
>> for errors in Error console. It will give the details of problems
>> in userChrome.css hacks. So just start Tb and check the errors in
>> error console.
>
> UserChrome.css contains the following. The font is now Arial, and
> the context menus (right click or cmd click) are using 14pt but the
> names of the accounts and messages remain at a fixed point size.
If I understand correctly what you're saying, that's because the
account/folder list in the folder pane and the message list in the
thread pane aren't menus. If you're not certain which areas of the
screen the terms "folder pane" and "thread pane" refer to, see
<http://kb.mozillazine.org/Window_layout_-_Thunderbird>.
> /* 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 font */
> menu, menulist, menuitem {
> font-family: Arial !important;
> font-size: 14pt !important;
> }
For more information about modifying fonts in the various areas
of TB's UI, see <http://kb.mozillazine.org/Pane_and_menu_fonts>,
especially the section on "Trees".
Ken Whiton
--
FIDO: 1:132/152
InterNet: kenw...@surfglobal.net.INVAL (remove the obvious to reply)
Tempuser
screen resolution and the theme you are using? Is there a way to
change their size?
Kevin
Nir wrote:
>
> I guess there is a syntax problem somewhere in your userChrome.css code.
> An easiest way to find the source of the problem is to check for errors
> in Error console. It will give the details of problems in userChrome.css
> hacks. So just start Tb and check the errors in error console.
>
To validate a CSS file you could upload it here:
http://jigsaw.w3.org/css-validator/#validate_by_upload
It will tell you if there are any syntax errors or non-standards compliant code.
Ken Whiton
*-* In Article <dtqdnQy8368x6ZTW...@mozilla.org>,
*-* Tempuser wrote
*-* About Re: UserChrome.css Issue
> Ken Whiton wrote:
>> *-* Tempuser wrote
> Okay, I got it. Does that mean the fonts are a function of your
> screen resolution and the theme you are using?
I don't know about themes but as I interpret the section on
scaling (Points vs. pixels) it's a function of resolution and screen
size, such that a font size specified in points will appear the same
*physical* size (x.xx in/cm/whatever) regardless of the screen size
and resolution. Note that I had never seen that page before writing
my last post, so I can't be 100% sure of that interpretation.
> Is there a way to
> change their size?
The "Trees" section I mentioned includes samples of code that
include font size. I would imagine that if you modify those it will
change the size.
Ken Whiton
*-* In Article <oradnRcm4_3nhZfW...@mozilla.org>,
*-* I wrote
*-* About Re: UserChrome.css Issue
> *-* Tempuser wrote
>
>> Ken Whiton wrote:
[ ... ]
>>> For more information about modifying fonts in the various areas
>>> of TB's UI, see <http://kb.mozillazine.org/Pane_and_menu_fonts>,
>>> especially the section on "Trees".
>
>> Okay, I got it. Does that mean the fonts are a function of your
>> screen resolution and the theme you are using?
>
> I don't know about themes but as I interpret the section on
> scaling (Points vs. pixels) it's a function of resolution and screen
> size, such that a font size specified in points will appear the same
> *physical* size (x.xx in/cm/whatever) regardless of the screen size
> and resolution. Note that I had never seen that page before writing
> my last post, so I can't be 100% sure of that interpretation.
>
>> Is there a way to
>> change their size?
>
> The "Trees" section I mentioned includes samples of code that
> include font size. I would imagine that if you modify those it will
> change the size.
I normally just use TB's default font size(s), but I just tested
that by closing TB and adding some font size instructions to the
folder pane section of my UserChrome.css file. When I reopened TB the
font size(s) in the folder pane had changed in accordance with those
instructions, so I was correct in that last statement.
For illustration, here's the normal version of the folder pane
section of my UserChrome.css file:
/* Set Colors In Folder/Account Window */
#folderTree > .tree-rows > .tree-bodybox {
background-color: #0000DD !important; }
#folderTree > treechildren::-moz-tree-cell-text(hasUnreadMessages-true) {
font-weight: bold; color: white !important; }
#folderTree > treechildren::-moz-tree-cell-text(hasUnreadMessages-false) {
font-weight: bold; color: yellow !important; }
#folderTree > treechildren::-moz-tree-cell-text(isServer-true) {
font-weight: bold; color: white !important; }
And here is the modified version I used for the test:
/* Set Colors In Folder/Account Window */
#folderTree > .tree-rows > .tree-bodybox {
background-color: #0000DD !important; }
#folderTree > treechildren::-moz-tree-cell-text(hasUnreadMessages-true) {
font-weight: bold; font-size: 16pt; color: white !important; }
#folderTree > treechildren::-moz-tree-cell-text(hasUnreadMessages-false) {
font-weight: bold; font-size: 6pt; color: yellow !important; }
#folderTree > treechildren::-moz-tree-cell-text(isServer-true) {
font-weight: bold; color: white !important; }
The exaggerated size difference between the folders containing
unread messages and those with none was easy to see, easily confirming
that the modification had worked.