On 8/1/23 9:55 PM, Jörg Lorenz wrote:
> Am 02.08.23 um 06:50 schrieb Jörg Lorenz:
>> Am 01.08.23 um 23:29 schrieb The Real Bev:
>>> On 8/1/23 11:19 AM, Mr. Man-wai Chang wrote:
>>>> On 7/29/2023 5:12 AM, The Real Bev wrote:
>>>>>
>>>>> Trying to find a theme that makes toolbar/menu text legible against its
>>>>> background. If you have normal vision you migh be surprised to find
>>>>> that this is harder than you might think. I found a couple that I like,
>>>>> but when I open the Nightly the color combination (black on various
>>>>> shades of dark green) changes until I disable and re-enable the theme.
>>>>> Does that with two different acceptable themes.
>>>>>
>>>>> Minor annoyance, of course, but text is really important for us
>>>>> astigmatics with the image slightly larger in one eye than the other.
>>>>> Yes, you're right, god hates me.
>>>>
>>>> Haver you ever tried the "layout.css.devPixelsPerPx" in about:config? It
>>>> could alter text size across the whole Firefox.
>>>
>>> It's set to -1. Changed it to +1 with no change to the menu etc. fonts.
>>> Control+/- changes the size of the 'regular' fonts, but I saw no
>>> change when I rebooted FF.
>>
>> -1 is default value. Do not change to +1 instead use in a first move
>> +1.5. You will be surprised. You can scale to your taste.
>
> BTW: Works also with TB.
>
> In my TB on my Mac mini on a 4K screen with 27"
>
> layout.css.devPixelsPerPx 2.3

Damn!

--
Cheers, Bev
The volume of a pizza of thickness 'a' and radius 'z'
is given by pi*z*z*a

Am 02.08.23 um 07:28 schrieb The Real Bev:
> On 8/1/23 9:55 PM, Jörg Lorenz wrote:
>> Am 02.08.23 um 06:50 schrieb Jörg Lorenz:
>>> Am 01.08.23 um 23:29 schrieb The Real Bev:
>>>> On 8/1/23 11:19 AM, Mr. Man-wai Chang wrote:
>>>>> On 7/29/2023 5:12 AM, The Real Bev wrote:
>>>>>>
>>>>>> Trying to find a theme that makes toolbar/menu text legible against its
>>>>>> background. If you have normal vision you migh be surprised to find
>>>>>> that this is harder than you might think. I found a couple that I like,
>>>>>> but when I open the Nightly the color combination (black on various
>>>>>> shades of dark green) changes until I disable and re-enable the theme.
>>>>>> Does that with two different acceptable themes.
>>>>>>
>>>>>> Minor annoyance, of course, but text is really important for us
>>>>>> astigmatics with the image slightly larger in one eye than the other.
>>>>>> Yes, you're right, god hates me.
>>>>>
>>>>> Haver you ever tried the "layout.css.devPixelsPerPx" in about:config? It
>>>>> could alter text size across the whole Firefox.
>>>>
>>>> It's set to -1. Changed it to +1 with no change to the menu etc. fonts.
>>>> Control+/- changes the size of the 'regular' fonts, but I saw no
>>>> change when I rebooted FF.
>>>
>>> -1 is default value. Do not change to +1 instead use in a first move
>>> +1.5. You will be surprised. You can scale to your taste.
>>
>> BTW: Works also with TB.
>>
>> In my TB on my Mac mini on a 4K screen with 27"
>>
>> layout.css.devPixelsPerPx 2.3
>
> Damn!

???

--
Alea iacta est

On 8/1/23 10:29 PM, Jörg Lorenz wrote:
> Am 02.08.23 um 07:28 schrieb The Real Bev:
>> On 8/1/23 9:55 PM, Jörg Lorenz wrote:
>>> Am 02.08.23 um 06:50 schrieb Jörg Lorenz:
>>>> Am 01.08.23 um 23:29 schrieb The Real Bev:
>>>>> On 8/1/23 11:19 AM, Mr. Man-wai Chang wrote:
>>>>>> On 7/29/2023 5:12 AM, The Real Bev wrote:
>>>>>>>
>>>>>>> Trying to find a theme that makes toolbar/menu text legible against its
>>>>>>> background. If you have normal vision you migh be surprised to find
>>>>>>> that this is harder than you might think. I found a couple that I like,
>>>>>>> but when I open the Nightly the color combination (black on various
>>>>>>> shades of dark green) changes until I disable and re-enable the theme.
>>>>>>> Does that with two different acceptable themes.
>>>>>>>
>>>>>>> Minor annoyance, of course, but text is really important for us
>>>>>>> astigmatics with the image slightly larger in one eye than the other.
>>>>>>> Yes, you're right, god hates me.
>>>>>>
>>>>>> Haver you ever tried the "layout.css.devPixelsPerPx" in about:config? It
>>>>>> could alter text size across the whole Firefox.
>>>>>
>>>>> It's set to -1. Changed it to +1 with no change to the menu etc. fonts.
>>>>> Control+/- changes the size of the 'regular' fonts, but I saw no
>>>>> change when I rebooted FF.
>>>>
>>>> -1 is default value. Do not change to +1 instead use in a first move
>>>> +1.5. You will be surprised. You can scale to your taste.
>>>
>>> BTW: Works also with TB.
>>>
>>> In my TB on my Mac mini on a 4K screen with 27"
>>>
>>> layout.css.devPixelsPerPx 2.3
>>
>> Damn!
>
> ???

1.5 resulted in HUGE. 1.2 was too big. 2.3 indicates enviable DAMNABLE
resolution! My eyes aren't anywhere near good enough to appreciate that.

Yet another advantage of getting older: cheaper stereo and photo equipment!

--
Cheers, Bev
The volume of a pizza of thickness 'a' and radius 'z'
is given by pi*z*z*a

Am 02.08.23 um 07:41 schrieb The Real Bev:
> 1.5 resulted in HUGE. 1.2 was too big. 2.3 indicates enviable DAMNABLE
> resolution! My eyes aren't anywhere near good enough to appreciate that.

That very much depends on the resolution setting of the screen. On my
other machines (laptops) the configuration setting is quite different.

--
Alea iacta est

On 8/2/23 01:26, this is what Jörg Lorenz wrote:
> Am 02.08.23 um 07:05 schrieb The Real Bev:
>> I don't suppose you have a magic word for just making everything bold...
>> I really wish I wanted to learn enough css etc. to do my own
>> manipulation,
>
> No in this respect I can't help you. I never had the need to dive that
> far into adjusting a client.
>
You can write a userChrome.css file with one simple line.

* { font-weight: bold !important; }

Wildcard items like this apply to everything. You could set a specific font for instance. Granted, some of the
regular Thunderbird code probably resets you bold in a few places.
--
Linux Mint 21.1 Cinnamon 5.6.8
Al

"The Real Bev" <bashley101@gmail.com> wrote

| > Haver you ever tried the "layout.css.devPixelsPerPx" in about:config? It
| > could alter text size across the whole Firefox.
|

As BigAl noted, userChrome.css works, and it can define
very particular details. Though I'm not sure if it works in all
current FF versions. The file should be in the app data
profile folder (with prefs.js the cookies file, etc.), in a
"chrome" subfolder. So... [profile]\chrome\userChrome.css
If the file or folder are not there, create them. (There's
also userContent.css, which can be used to override
webpage styles. It's potentially very powerful. I use it
to stop or remove anything that moves.**)

Here's what I have to adjust menu labels:

menubar, menubutton, menulist, menu, menuitem {
font-family: verdana !important;
font-size: 10px !important;
color: #0000A0 !important;
line-height: 1.1 !important;
}

I also adjust bookmarks.... This gives me a background
texture, like background on a webpage:

menupopup, popup, menubar, toolbox, toolbar, .tabbrowser-tabs
{background-image: url("back.gif");}

These remove Open in New Tab and Open in Private Window
from the menu and context menu, because I never use either,
so I want the top item to be "Open in New Window".

menuitem[label="New Tab"] {display: none !important;}
menuitem[label="New Private Window"] {display: none !important;}
#context-openlinkintab {display: none !important;}
#context-openlinkprivate {display: none !important;}

It's a clever system that makes FF as customizable as
a webpage. The only problem is that like the prefs settings,
no one has ever completely documented how it works. You
just have to go around looking for samples. It's all CSS, which
is a web standard, but the Mozilla people adopted it. So it's
not real CSS. For example, there's no such HTML tag as
""menuitem" or "toolbar", and CSS IDs like #context-openlinkintab
are not discoverable. It's similar to the brainstorm that created
JSON. People thought, "Let's make a storage file format. I know!
If it looks just like javascript then that would be great, even if
that's an incredibly dumb idea!"

It's similar with userChrome.css. Some bright bulb at Mozilla
thought, "Wouldn't it be cool if we made a customizing system
modelled on CSS. That would be so cool! Docuentation? We
don't need no stinking documentation. It's CSS!" Just be happy
these people prefer to live in basements and don't run for office.

** And example of userContent.css. I use this to block
animation, "dripping" text, etc:

/* stop CSS animation */

* {transform: none !important;
-moz-transform: none !important;
transition-property: none !important;
-moz-transition-property: none !important;
-moz-transition-duration: none !important;
animation: none !important;
-moz-animation: none !important;
-webkit-animation: none !important;}

:before {display: none !important;}
:after {display: none !important;}

"The Real Bev" <bashley101@gmail.com> wrote

> Yet another advantage of getting older: cheaper stereo and photo
> equipment!

Indeed. And who needs a 4K TV? We have two that are
720p. The clarity is amazing to my eyes. On the other
hand, I thought the clarity on the 25 year old Sony CRT
was amazing. That eventually died. The black plastic case
eventually turned as soft as licorice from the heat!

On 8/2/23 4:52 AM, Big Al wrote:
> On 8/2/23 01:26, this is what Jörg Lorenz wrote:
>> Am 02.08.23 um 07:05 schrieb The Real Bev:
>>> I don't suppose you have a magic word for just making everything bold...
>>> I really wish I wanted to learn enough css etc. to do my own
>>> manipulation,
>>
>> No in this respect I can't help you. I never had the need to dive that
>> far into adjusting a client.
>>
> You can write a userChrome.css file with one simple line.
>
> * { font-weight: bold !important; }

I'll give that a shot...
YESSSS! That helps a lot, thanks!

> Wildcard items like this apply to everything. You could set a specific font for instance. Granted, some of the
> regular Thunderbird code probably resets you bold in a few places.

I've had the .css files for a long time with entries similar/identical
to those listed by Newyana2. They still work with Thunderbird 38, but
one by one a number of them had stopped working by the time I stopped at
Firefox 82. Most recent attempts to add entries have failed miserably.
Some continue to work, including the recently-added one to eliminate the
horizontal tab bar (and the 'bold' line above), but others just don't.

--
Cheers, Bev
"We're from the Government. We're here to help."

On 8/2/23 8:22 AM, The Real Bev wrote:
> On 8/2/23 4:52 AM, Big Al wrote:
>> On 8/2/23 01:26, this is what Jörg Lorenz wrote:
>>> Am 02.08.23 um 07:05 schrieb The Real Bev:
>>>> I don't suppose you have a magic word for just making everything bold...
>>>> I really wish I wanted to learn enough css etc. to do my own
>>>> manipulation,
>>>
>>> No in this respect I can't help you. I never had the need to dive that
>>> far into adjusting a client.
>>>
>> You can write a userChrome.css file with one simple line.
>>
>> * { font-weight: bold !important; }
>
> I'll give that a shot...
> YESSSS! That helps a lot, thanks!

Works in Nightly too, which was just updated to FF118.

>> Wildcard items like this apply to everything. You could set a specific font for instance. Granted, some of the
>> regular Thunderbird code probably resets you bold in a few places.
>
> I've had the .css files for a long time with entries similar/identical
> to those listed by Newyana2. They still work with Thunderbird 38, but
> one by one a number of them had stopped working by the time I stopped at
> Firefox 82. Most recent attempts to add entries have failed miserably.
> Some continue to work, including the recently-added one to eliminate the
> horizontal tab bar (and the 'bold' line above), but others just don't.

--
Cheers, Bev
"We're from the Government. We're here to help."

On 8/2/23 11:27, this is what The Real Bev wrote:
> On 8/2/23 8:22 AM, The Real Bev wrote:
>> On 8/2/23 4:52 AM, Big Al wrote:
>>> On 8/2/23 01:26, this is what Jörg Lorenz wrote:
>>>> Am 02.08.23 um 07:05 schrieb The Real Bev:
>>>>> I don't suppose you have a magic word for just making everything bold...
>>>>>    I really wish I wanted to learn enough css etc.  to do my own
>>>>> manipulation,
>>>>
>>>> No in this respect I can't help you. I never had the need to dive that
>>>> far into  adjusting a client.
>>>>
>>> You can write a userChrome.css file with one simple line.
>>>
>>> * { font-weight: bold !important; }
>>
>> I'll give that a shot...
>> YESSSS!  That helps a lot, thanks!
>
> Works in Nightly too, which was just updated to FF118.
>
>>> Wildcard items like this apply to everything.  You could set a specific font for instance.   Granted, some of the
>>> regular Thunderbird code probably resets you bold in a few places.
>>
>> I've had the .css files for a long time with entries similar/identical
>> to those listed by Newyana2.  They still work with Thunderbird 38, but
>> one by one a number of them had stopped working by the time I stopped at
>> Firefox 82.  Most recent attempts to add entries have failed miserably.
>> Some continue to work, including the recently-added one to eliminate the
>> horizontal tab bar (and the 'bold' line above), but others just don't.
>
Yes, that line is so generic!
I too have/had a few hundred lines of css and I seem to now and then drop a few items. Some I don't care, some FF
works better (now) without them. ... don't get me on the latest Thunderbird update.
--
Linux Mint 21.1 Cinnamon 5.6.8
Al

On 8/2/23 10:15 AM, Big Al wrote:
> On 8/2/23 11:27, this is what The Real Bev wrote:
>> On 8/2/23 8:22 AM, The Real Bev wrote:
>>> On 8/2/23 4:52 AM, Big Al wrote:
>>>> On 8/2/23 01:26, this is what Jörg Lorenz wrote:
>>>>> Am 02.08.23 um 07:05 schrieb The Real Bev:
>>>>>> I don't suppose you have a magic word for just making everything bold...
>>>>>>    I really wish I wanted to learn enough css etc.  to do my own
>>>>>> manipulation,
>>>>>
>>>>> No in this respect I can't help you. I never had the need to dive that
>>>>> far into  adjusting a client.
>>>>>
>>>> You can write a userChrome.css file with one simple line.
>>>>
>>>> * { font-weight: bold !important; }
>>>
>>> I'll give that a shot...
>>> YESSSS!  That helps a lot, thanks!
>>
>> Works in Nightly too, which was just updated to FF118.
>>
>>>> Wildcard items like this apply to everything.  You could set a specific font for instance.   Granted, some of the
>>>> regular Thunderbird code probably resets you bold in a few places.
>>>
>>> I've had the .css files for a long time with entries similar/identical
>>> to those listed by Newyana2.  They still work with Thunderbird 38, but
>>> one by one a number of them had stopped working by the time I stopped at
>>> Firefox 82.  Most recent attempts to add entries have failed miserably.
>>> Some continue to work, including the recently-added one to eliminate the
>>> horizontal tab bar (and the 'bold' line above), but others just don't.
>>
> Yes, that line is so generic!
> I too have/had a few hundred lines of css and I seem to now and then drop a few items. Some I don't care, some FF
> works better (now) without them. ... don't get me on the latest Thunderbird update.

Not even thinking about it. Way too much personalization to deal with,
most of which I assume to be either impossible or far more work than
I'm willing to put in again. Just the oauth2 crap was horrible. I'd
only update TB if the only other option were to use gmail at the website.

--
Cheers, Bev
Buckle Up. It makes it harder for the aliens
to suck you out of your car.

On 8/2/23 15:39, this is what The Real Bev wrote:
> On 8/2/23 10:15 AM, Big Al wrote:
>> On 8/2/23 11:27, this is what The Real Bev wrote:
>>> On 8/2/23 8:22 AM, The Real Bev wrote:
>>>> On 8/2/23 4:52 AM, Big Al wrote:
>>>>> On 8/2/23 01:26, this is what Jörg Lorenz wrote:
>>>>>> Am 02.08.23 um 07:05 schrieb The Real Bev:
>>>>>>> I don't suppose you have a magic word for just making everything bold...
>>>>>>>    I really wish I wanted to learn enough css etc.  to do my own
>>>>>>> manipulation,
>>>>>>
>>>>>> No in this respect I can't help you. I never had the need to dive that
>>>>>> far into  adjusting a client.
>>>>>>
>>>>> You can write a userChrome.css file with one simple line.
>>>>>
>>>>> * { font-weight: bold !important; }
>>>>
>>>> I'll give that a shot...
>>>> YESSSS!  That helps a lot, thanks!
>>>
>>> Works in Nightly too, which was just updated to FF118.
>>>
>>>>> Wildcard items like this apply to everything.  You could set a specific font for instance.   Granted, some of the
>>>>> regular Thunderbird code probably resets you bold in a few places.
>>>>
>>>> I've had the .css files for a long time with entries similar/identical
>>>> to those listed by Newyana2.  They still work with Thunderbird 38, but
>>>> one by one a number of them had stopped working by the time I stopped at
>>>> Firefox 82.  Most recent attempts to add entries have failed miserably.
>>>> Some continue to work, including the recently-added one to eliminate the
>>>> horizontal tab bar (and the 'bold' line above), but others just don't.
>>>
>> Yes, that line is so generic!
>> I too have/had a few hundred lines of css and I seem to now and then drop a few items.   Some I don't care, some FF
>> works better (now) without them.  ... don't get me on the latest Thunderbird update.
>
> Not even thinking about it.  Way too much personalization to deal with, most  of which I assume to be either impossible
> or far more work than I'm willing to put in again.  Just the oauth2 crap was horrible.  I'd only update TB if the only
> other option were to use gmail at the website.
>
Ironically I've spent the last 2+ hours looking at my css file for TB. I too didn't want past v102. Nothing worked of
course in v115. But I finally stumbled onto those fancy keyword terms to pick things and get them to work. So it's 95%
there. With the help of that layout.css.devPixelsPerPx setting.
--
Linux Mint 21.1 Cinnamon 5.6.8
Al

On 8/2/2023 3:56 PM, Big Al wrote:
> On 8/2/23 15:39, this is what The Real Bev wrote:
>> On 8/2/23 10:15 AM, Big Al wrote:
>>> On 8/2/23 11:27, this is what The Real Bev wrote:
>>>> On 8/2/23 8:22 AM, The Real Bev wrote:
>>>>> On 8/2/23 4:52 AM, Big Al wrote:
>>>>>> On 8/2/23 01:26, this is what Jörg Lorenz wrote:
>>>>>>> Am 02.08.23 um 07:05 schrieb The Real Bev:
>>>>>>>> I don't suppose you have a magic word for just making everything
>>>>>>>> bold...
>>>>>>>>    I really wish I wanted to learn enough css etc.  to do my own
>>>>>>>> manipulation,
>>>>>>>
>>>>>>> No in this respect I can't help you. I never had the need to dive
>>>>>>> that
>>>>>>> far into  adjusting a client.
>>>>>>>
>>>>>> You can write a userChrome.css file with one simple line.
>>>>>>
>>>>>> * { font-weight: bold !important; }
>>>>>
>>>>> I'll give that a shot...
>>>>> YESSSS!  That helps a lot, thanks!
>>>>
>>>> Works in Nightly too, which was just updated to FF118.
>>>>
>>>>>> Wildcard items like this apply to everything.  You could set a
>>>>>> specific font for instance.   Granted, some of the
>>>>>> regular Thunderbird code probably resets you bold in a few places.
>>>>>
>>>>> I've had the .css files for a long time with entries similar/identical
>>>>> to those listed by Newyana2.  They still work with Thunderbird 38, but
>>>>> one by one a number of them had stopped working by the time I
>>>>> stopped at
>>>>> Firefox 82.  Most recent attempts to add entries have failed
>>>>> miserably.
>>>>> Some continue to work, including the recently-added one to
>>>>> eliminate the
>>>>> horizontal tab bar (and the 'bold' line above), but others just don't.
>>>>
>>> Yes, that line is so generic!
>>> I too have/had a few hundred lines of css and I seem to now and then
>>> drop a few items.   Some I don't care, some FF
>>> works better (now) without them.  ... don't get me on the latest
>>> Thunderbird update.
>>
>> Not even thinking about it.  Way too much personalization to deal
>> with, most  of which I assume to be either impossible or far more work
>> than I'm willing to put in again.  Just the oauth2 crap was horrible.
>> I'd only update TB if the only other option were to use gmail at the
>> website.
>>
> Ironically I've spent the last 2+ hours looking at my css file for TB. I
> too didn't want past v102.  Nothing worked of course in v115.  But I
> finally stumbled onto those fancy keyword terms to pick things and get
> them to work.  So it's 95% there.  With the help of that
> layout.css.devPixelsPerPx setting.
Spoke too soon. It's borked. I'll stay on 102.