Good day.
I'm using Firefox 121.0 64 bit on Win 10 Pro.

Like many I guess, I have a functioning chrome userChrome file containing
snippets of css I've found in various places over the years to make my
usage of Fx easier... Like Tabs where I want them. ;-)

I have a snippet of code that colors the tabs, and yes it works okay.

However what would be helpful in my advancing years, is another snippet of
css that would color inactive tabs a different colour to the active tab.

If that's possible, does any kind person have those lines of css, and
might pass them on to me. :-)

It would be appreciated.
D.

On 12/24/23 05:18 AM, News wrote:
> Good day.
> I'm using Firefox 121.0 64 bit on Win 10 Pro.
>
> Like many I guess, I have a functioning chrome userChrome file containing
> snippets of css I've found in various places over the years to make my
> usage of Fx easier... Like Tabs where I want them. ;-)
>
> I have a snippet of code that colors the tabs, and yes it works okay.
>
> However what would be helpful in my advancing years, is another snippet of
> css that would color inactive tabs a different colour to the active tab.
>
> If that's possible, does any kind person have those lines of css, and
> might pass them on to me. :-)
>
> It would be appreciated.
> D.
>
I don't use this, I've found themes that do a good job, but you're welcome to this.
I also don't know if it works. FF's code and item naming conventions are fluid.

..tab-background:not([selected]) { background-color: #222222 !important; }
--
Linux Mint 21.2 Cinnamon
Al

On Sun, 24 Dec 2023 10:18:48 +0000 (GMT), News <news@triffid.co.uk>
wrote:

>Good day.
>I'm using Firefox 121.0 64 bit on Win 10 Pro.
>
>Like many I guess, I have a functioning chrome userChrome file containing
>snippets of css I've found in various places over the years to make my
>usage of Fx easier... Like Tabs where I want them. ;-)
>
>I have a snippet of code that colors the tabs, and yes it works okay.
>
>However what would be helpful in my advancing years, is another snippet of
>css that would color inactive tabs a different colour to the active tab.
>
>If that's possible, does any kind person have those lines of css, and
>might pass them on to me. :-)
>
>It would be appreciated.
>D.

Wha I had in my userChrome several years ago stopped working at one
major Ffox update, but I agree with Big Al that several themes fit the
bill to highlight the *active* tab.

I routinely use "Blue Mozilla Firefox", but also have "Dream of Waves"
and "Lufthansa Terminal" loaded. That last one has a really
in-your-face active tab with the current Ffox floating tab set-up.

Looking at my Thunderbird userChrome, I *think* these are what I had
for Ffox, but tread carefully. They worked well in conjunction with
the "Dream of Waves" theme:

-------------------------

}
..tab-background {
border-radius: 12px 12px 0px 0px !important;
border-image: none !important;
border-left: 1px solid !important;
border-right: 1px solid !important;
border-top: 1px solid !important;
background-color: #FFE4B5 !important;

}

..tab-background[selected="true"] {
background-attachment: none!important;
background-color: #7FFFD4!important;
background-image: none!important;
background-position: none!important;
background-repeat: none!important;
background-size: none!important;
}

----------------------

In article <tumgoih9qu69vfmopqi831sjok1mghe2jd@4ax.com>,
Nobody <jock@soccer.com> wrote:
[Snippy]
> Looking at my Thunderbird userChrome, I *think* these are what I had
> for Ffox, but tread carefully. They worked well in conjunction with
> the "Dream of Waves" theme:

> -------------------------

> }
> .tab-background {
> border-radius: 12px 12px 0px 0px !important;
> border-image: none !important;
> border-left: 1px solid !important;
> border-right: 1px solid !important;
> border-top: 1px solid !important;
> background-color: #FFE4B5 !important;

> }

> .tab-background[selected="true"] {
> background-attachment: none!important;
> background-color: #7FFFD4!important;
> background-image: none!important;
> background-position: none!important;
> background-repeat: none!important;
> background-size: none!important;
> }

Excellent, that worked with my "Soft Drawing Paper" theme.

Interestingly, the snippet of css I already had in place that stopped
working after a recent update was almost the same as yours.

I just needed to modify a couple of lines and it was back in action.

Thanks, much appreciated.

Best wishes for Christmas & the new year. :-)

D.

News graced us with on 12/24/2023 1:19 PM:
> In article <tumgoih9qu69vfmopqi831sjok1mghe2jd@4ax.com>,
> Nobody <jock@soccer.com> wrote:
> [Snippy]
>> Looking at my Thunderbird userChrome, I *think* these are what I had
>> for Ffox, but tread carefully. They worked well in conjunction with
>> the "Dream of Waves" theme:
>
>> -------------------------
>
>> }
>> .tab-background {
>> border-radius: 12px 12px 0px 0px !important;
>> border-image: none !important;
>> border-left: 1px solid !important;
>> border-right: 1px solid !important;
>> border-top: 1px solid !important;
>> background-color: #FFE4B5 !important;
>
>> }
>
>> .tab-background[selected="true"] {
>> background-attachment: none!important;
>> background-color: #7FFFD4!important;
>> background-image: none!important;
>> background-position: none!important;
>> background-repeat: none!important;
>> background-size: none!important;
>> }
>
> Excellent, that worked with my "Soft Drawing Paper" theme.
>
> Interestingly, the snippet of css I already had in place that stopped
> working after a recent update was almost the same as yours.
>
> I just needed to modify a couple of lines and it was back in action.
>
> Thanks, much appreciated.
>
> Best wishes for Christmas & the new year. :-)

The XUL version of the browser had an DOM Inspector add-on that allowed
one to "inspect" the browser chrome (nav buttons, tabs, url bar, &c.)
This feature is now intrinsic to the browser but by default disabled.
Below is a link that describes how to enable it and open its window for
interrogating chrome elements. Click "OK" to the Incoming Connection
dialog pop-up.

Once the DOM Inspector window is open, press the square with a pointer
in it icon, then click the element of interest. The left panel will move
to and highlight the clicked element on the left pane and display the
CSS being used on it.

Cheers and Seasons Greetings!

--
Sailfish
CDC Covid19 Trends: https://www.facebook.com/groups/624208354841034
Rare Mozilla Stuff: http://tinyurl.com/z86x3sg

Sailfish graced us with on 12/24/2023 2:08 PM:
> News graced us with on 12/24/2023 1:19 PM:
>> In article <tumgoih9qu69vfmopqi831sjok1mghe2jd@4ax.com>,
>> Nobody <jock@soccer.com> wrote:
>> [Snippy]
>>> Looking at my Thunderbird userChrome, I *think* these are what I had
>>> for Ffox, but tread carefully. They worked well in conjunction with
>>> the "Dream of Waves" theme:
>>
>>> -------------------------
>>
>>> }
>>> .tab-background {
>>> border-radius: 12px 12px 0px 0px !important;
>>> border-image: none !important;
>>> border-left: 1px solid !important;
>>> border-right: 1px solid !important;
>>> border-top: 1px solid !important;
>>> background-color: #FFE4B5 !important;
>>
>>> }
>>
>>> .tab-background[selected="true"] {
>>> background-attachment: none!important;
>>> background-color: #7FFFD4!important;
>>> background-image: none!important;
>>> background-position: none!important;
>>> background-repeat: none!important;
>>> background-size: none!important;
>>> }
>>
>> Excellent, that worked with my "Soft Drawing Paper" theme.
>>
>> Interestingly, the snippet of css I already had in place that stopped
>> working after a recent update was almost the same as yours.
>>
>> I just needed to modify a couple of lines and it was back in action.
>>
>> Thanks, much appreciated.
>>
>> Best wishes for Christmas & the new year. :-)
>
> The XUL version of the browser had an DOM Inspector add-on that allowed
> one to "inspect" the browser chrome (nav buttons, tabs, url bar, &c.)
> This feature is now intrinsic to the browser but by default disabled.
> Below is a link that describes how to enable it and open its window for
> interrogating chrome elements. Click "OK" to the Incoming Connection
> dialog pop-up.
>
> Once the DOM Inspector window is open, press the square with a pointer
> in it icon, then click the element of interest. The left panel will move
> to and highlight the clicked element on the left pane and display the
> CSS being used on it.
>
Ugh! The forgotten link:
https://superuser.com/questions/1764681/how-to-inspect-the-chrome-of-firefox/1764682#1764682

Cheers and Seasons Greetings!
--
Sailfish
CDC Covid19 Trends: https://www.facebook.com/groups/624208354841034
Rare Mozilla Stuff: http://tinyurl.com/z86x3sg

Sailfish graced us with on 12/24/2023 2:11 PM:
> Sailfish graced us with on 12/24/2023 2:08 PM:
>> News graced us with on 12/24/2023 1:19 PM:
>>> In article <tumgoih9qu69vfmopqi831sjok1mghe2jd@4ax.com>,
>>> Nobody <jock@soccer.com> wrote:
>>> [Snippy]
>>>> Looking at my Thunderbird userChrome, I *think* these are what I had
>>>> for Ffox, but tread carefully. They worked well in conjunction with
>>>> the "Dream of Waves" theme:
>>>
>>>> -------------------------
>>>
>>>> }
>>>> .tab-background {
>>>> border-radius: 12px 12px 0px 0px !important;
>>>> border-image: none !important;
>>>> border-left: 1px solid !important;
>>>> border-right: 1px solid !important;
>>>> border-top: 1px solid !important;
>>>> background-color: #FFE4B5 !important;
>>>
>>>> }
>>>
>>>> .tab-background[selected="true"] {
>>>> background-attachment: none!important;
>>>> background-color: #7FFFD4!important;
>>>> background-image: none!important;
>>>> background-position: none!important;
>>>> background-repeat: none!important;
>>>> background-size: none!important;
>>>> }
>>>
>>> Excellent, that worked with my "Soft Drawing Paper" theme.
>>>
>>> Interestingly, the snippet of css I already had in place that stopped
>>> working after a recent update was almost the same as yours.
>>>
>>> I just needed to modify a couple of lines and it was back in action.
>>>
>>> Thanks, much appreciated.
>>>
>>> Best wishes for Christmas & the new year. :-)
>>
>> The XUL version of the browser had an DOM Inspector add-on that
>> allowed one to "inspect" the browser chrome (nav buttons, tabs, url
>> bar, &c.) This feature is now intrinsic to the browser but by default
>> disabled. Below is a link that describes how to enable it and open its
>> window for interrogating chrome elements. Click "OK" to the Incoming
>> Connection dialog pop-up.
>>
>> Once the DOM Inspector window is open, press the square with a pointer
>> in it icon, then click the element of interest. The left panel will
>> move to and highlight the clicked element on the left pane and display
>> the CSS being used on it.
>>
A more robust explanation:
https://firefox-source-docs.mozilla.org/devtools-user/browser_toolbox/index.html

--
Sailfish
CDC Covid19 Trends: https://www.facebook.com/groups/624208354841034
Rare Mozilla Stuff: http://tinyurl.com/z86x3sg

On 12/24/23 05:13 PM, Sailfish wrote:
> Sailfish graced us with on 12/24/2023 2:11 PM:
>> Sailfish graced us with on 12/24/2023 2:08 PM:
>>> News graced us with on 12/24/2023 1:19 PM:
>>>> In article <tumgoih9qu69vfmopqi831sjok1mghe2jd@4ax.com>,
>>>>    Nobody <jock@soccer.com> wrote:
>>>> [Snippy]
>>>>> Looking at my Thunderbird userChrome, I *think* these are what I had
>>>>> for Ffox, but tread carefully.  They worked well in conjunction with
>>>>> the "Dream of Waves" theme:
>>>>
>>>>> -------------------------
>>>>
>>>>> }
>>>>> .tab-background {
>>>>>   border-radius: 12px 12px 0px 0px !important;
>>>>>   border-image: none !important;
>>>>>   border-left: 1px solid !important;
>>>>>   border-right: 1px solid !important;
>>>>>   border-top: 1px solid !important;
>>>>>   background-color: #FFE4B5 !important;
>>>>
>>>>> }
>>>>
>>>>> .tab-background[selected="true"] {
>>>>>     background-attachment: none!important;
>>>>>     background-color: #7FFFD4!important;
>>>>>     background-image: none!important;
>>>>>     background-position: none!important;
>>>>>     background-repeat: none!important;
>>>>>     background-size: none!important;
>>>>> }
>>>>
>>>> Excellent, that worked with my "Soft Drawing Paper" theme.
>>>>
>>>> Interestingly, the snippet of css I already had in place that stopped
>>>> working after a recent update was almost the same as yours.
>>>>
>>>> I just needed to modify a couple of lines and it was back in action.
>>>>
>>>> Thanks, much appreciated.
>>>>
>>>> Best wishes for Christmas & the new year.  :-)
>>>
>>> The XUL version of the browser had an DOM Inspector add-on that allowed one to "inspect" the browser chrome (nav
>>> buttons, tabs, url bar, &c.) This feature is now intrinsic to the browser but by default disabled. Below is a link
>>> that describes how to enable it and open its window for interrogating chrome elements. Click "OK" to the Incoming
>>> Connection dialog pop-up.
>>>
>>> Once the DOM Inspector window is open, press the square with a pointer in it icon, then click the element of
>>> interest. The left panel will move to and highlight the clicked element on the left pane and display the CSS being
>>> used on it.
>>>
> A more robust explanation:
> https://firefox-source-docs.mozilla.org/devtools-user/browser_toolbox/index.html
>
And if you set
devtools.debugger.prompt-connection = false
the DOM inspector won't ask you to connect.
--
Linux Mint 21.2 Cinnamon
Al

Big Al graced us with on 12/24/2023 2:54 PM:
> On 12/24/23 05:13 PM, Sailfish wrote:
>> Sailfish graced us with on 12/24/2023 2:11 PM:
>>> Sailfish graced us with on 12/24/2023 2:08 PM:
>>>> News graced us with on 12/24/2023 1:19 PM:
>>>>> In article <tumgoih9qu69vfmopqi831sjok1mghe2jd@4ax.com>,
>>>>> Nobody <jock@soccer.com> wrote:
>>>>> [Snippy]
>>>>>> Looking at my Thunderbird userChrome, I *think* these are what I had
>>>>>> for Ffox, but tread carefully. They worked well in conjunction with
>>>>>> the "Dream of Waves" theme:
>>>>>
>>>>>> -------------------------
>>>>>
>>>>>> }
>>>>>> .tab-background {
>>>>>> border-radius: 12px 12px 0px 0px !important;
>>>>>> border-image: none !important;
>>>>>> border-left: 1px solid !important;
>>>>>> border-right: 1px solid !important;
>>>>>> border-top: 1px solid !important;
>>>>>> background-color: #FFE4B5 !important;
>>>>>
>>>>>> }
>>>>>
>>>>>> .tab-background[selected="true"] {
>>>>>> background-attachment: none!important;
>>>>>> background-color: #7FFFD4!important;
>>>>>> background-image: none!important;
>>>>>> background-position: none!important;
>>>>>> background-repeat: none!important;
>>>>>> background-size: none!important;
>>>>>> }
>>>>>
>>>>> Excellent, that worked with my "Soft Drawing Paper" theme.
>>>>>
>>>>> Interestingly, the snippet of css I already had in place that stopped
>>>>> working after a recent update was almost the same as yours.
>>>>>
>>>>> I just needed to modify a couple of lines and it was back in action.
>>>>>
>>>>> Thanks, much appreciated.
>>>>>
>>>>> Best wishes for Christmas & the new year. :-)
>>>>
>>>> The XUL version of the browser had an DOM Inspector add-on that
>>>> allowed one to "inspect" the browser chrome (nav buttons, tabs, url
>>>> bar, &c.) This feature is now intrinsic to the browser but by
>>>> default disabled. Below is a link that describes how to enable it
>>>> and open its window for interrogating chrome elements. Click "OK" to
>>>> the Incoming Connection dialog pop-up.
>>>>
>>>> Once the DOM Inspector window is open, press the square with a
>>>> pointer in it icon, then click the element of interest. The left
>>>> panel will move to and highlight the clicked element on the left
>>>> pane and display the CSS being used on it.
>>>>
>> A more robust explanation:
>> https://firefox-source-docs.mozilla.org/devtools-user/browser_toolbox/index.html
>>
>>
> And if you set
> devtools.debugger.prompt-connection = false
> the DOM inspector won't ask you to connect.

+1

--
Sailfish
CDC Covid19 Trends: https://www.facebook.com/groups/624208354841034
Rare Mozilla Stuff: http://tinyurl.com/z86x3sg

In article <umaa57$2nn9g$2@dont-email.me>,
Sailfish <NIXCAPSsailfish@NIXCAPSunforgettable.com> wrote:
[Snippy]
> The XUL version of the browser had an DOM Inspector add-on that allowed
> one to "inspect" the browser chrome (nav buttons, tabs, url bar, &c.)
> This feature is now intrinsic to the browser but by default disabled.
> Below is a link that describes how to enable it and open its window for
> interrogating chrome elements. Click "OK" to the Incoming Connection
> dialog pop-up.

> Once the DOM Inspector window is open, press the square with a pointer
> in it icon, then click the element of interest. The left panel will move
> to and highlight the clicked element on the left pane and display the
> CSS being used on it.

> Cheers and Seasons Greetings!

Yeeees! well! Interesting thought, but way outside my knowledge base...

I had a look at it out of interest, but as just a user/abuser of apps,
that presented as an awful mess... :-/

D.

On 12/25/23 04:19 AM, News wrote:
> In article <umaa57$2nn9g$2@dont-email.me>,
> Sailfish <NIXCAPSsailfish@NIXCAPSunforgettable.com> wrote:
> [Snippy]
>> The XUL version of the browser had an DOM Inspector add-on that allowed
>> one to "inspect" the browser chrome (nav buttons, tabs, url bar, &c.)
>> This feature is now intrinsic to the browser but by default disabled.
>> Below is a link that describes how to enable it and open its window for
>> interrogating chrome elements. Click "OK" to the Incoming Connection
>> dialog pop-up.
>
>> Once the DOM Inspector window is open, press the square with a pointer
>> in it icon, then click the element of interest. The left panel will move
>> to and highlight the clicked element on the left pane and display the
>> CSS being used on it.
>
>> Cheers and Seasons Greetings!
>
> Yeeees! well! Interesting thought, but way outside my knowledge base...
>
> I had a look at it out of interest, but as just a user/abuser of apps,
> that presented as an awful mess... :-/
>
> D.
>
It looked that way to me too, but after a long while and a bit of dabble, and seeing code from others, it finally got to
me what was happening.
But it is a bit of a geek thing.
--
Linux Mint 21.2 Cinnamon
Al

Interestingly... :-/

While obviously I don't know the coding minutia of the thing, testing I
have discovered it is Moz Devs who have arrange this (Expletive [Alpha 6
alpha 21]self edited) css tab color annoyance.

In Firefox version 20.0.1 the original tab color css snippet works
correctly.

Updating to 21.0 is the moment when the [Alpha 6 alpha 21] happens.

:-(

D.

News wrote:

> Interestingly... :-/

It might be interesting if anyone else can work out what the hell you're
bleating on about ...

In article <kuvrvoFocmmU1@mid.individual.net>,
Andy Burns <usenet@andyburns.uk> wrote:
> News wrote:

> > Interestingly... :-/

> It might be interesting if anyone else can work out what the hell you're
> bleating on about ...

Baaaah!
Well, if you had followed the thread over the past few days, all would be
revealed. :-)

So I'll summarise for you. :-/

I have a snippet of css in my chrome userChrome file that colors inactive
tabs a different color to the active tab.

After a recent Fx update that bit of css no longer worked and all tabs
active or inactive were the same color.

Nobody(jock@.) gave a possible solution that worked.
Excellent thanks...

So then I was interested in what update had done the (Expletive Alpha 6
alpha 21) css tab color annoyance.

Translated for you an F and a U :-)

I did some 'xperiments' and discovered it was the update from 20.0.1 to
the most recent 21.0 that had done the deed.

So I thought I'd pass on that bit of info.
Ta da!
End of story... :-)

D.

On 12/26/23 02:44 PM, News wrote:
> In article <kuvrvoFocmmU1@mid.individual.net>,
> Andy Burns <usenet@andyburns.uk> wrote:
>> News wrote:
>
>>> Interestingly... :-/
>
>> It might be interesting if anyone else can work out what the hell you're
>> bleating on about ...
>
> Baaaah!
> Well, if you had followed the thread over the past few days, all would be
> revealed. :-)
>
> So I'll summarise for you. :-/
>
> I have a snippet of css in my chrome userChrome file that colors inactive
> tabs a different color to the active tab.
>
> After a recent Fx update that bit of css no longer worked and all tabs
> active or inactive were the same color.
>
> Nobody(jock@.) gave a possible solution that worked.
> Excellent thanks...
>
> So then I was interested in what update had done the (Expletive Alpha 6
> alpha 21) css tab color annoyance.
>
> Translated for you an F and a U :-)
>
> I did some 'xperiments' and discovered it was the update from 20.0.1 to
> the most recent 21.0 that had done the deed.
>
> So I thought I'd pass on that bit of info.
> Ta da!
> End of story... :-)
>
> D.
>
You're still on 20, when FF is a hundred further. You're not worried about any leaks? (obviously)
--
Linux Mint 21.2 Cinnamon
Al

In article <umfdfu$3jhfq$1@dont-email.me>,
Big Al <alan@invalid.com> wrote:

> You're still on 20, when FF is a hundred further. You're not worried
> about any leaks? (obviously)

Good catch Big Al. :-)
And Ooooer! on my part... :-(

I think a bit too much seasons celebration on my part methinks and "1"
went missing...

As per my original post on Christmas eve, Sunday 24th December...

"Good day.
I'm using Firefox 121.0 64 bit on Win 10 Pro."

I do apologise for all our confusions...

Bottom line, Fx 120.0.1 was okay, 121.0 done the deed. :-)

D.

News wrote:

> In article <kuvrvoFocmmU1@mid.individual.net>,
> Andy Burns <usenet@andyburns.uk> wrote:
>> News wrote:
>
>>> Interestingly... :-/
>
>> It might be interesting if anyone else can work out what the hell you're
>> bleating on about ...
>
> Baaaah!
> Well, if you had followed the thread over the past few days, all would be
> revealed. :-)
>
> So I'll summarise for you. :-/
>
> I have a snippet of css in my chrome userChrome file that colors inactive
> tabs a different color to the active tab.
>
> After a recent Fx update that bit of css no longer worked and all tabs
> active or inactive were the same color.

You should always expect firefox to break your userChrome.css, them's
the rules :-)

> Nobody(jock@.) gave a possible solution that worked.
> Excellent thanks...
>
> So then I was interested in what update had done the (Expletive Alpha 6
> alpha 21) css tab color annoyance.
>
> Translated for you an F and a U :-)

I don't think anyone on usenet expects to be protected from expletives,
I actually wondered if "alpha 6" and "alpha 21" were some test-fork code
labels, but couldn't find aything

> I did some 'xperiments' and discovered it was the update from 20.0.1 to
> the most recent 21.0 that had done the deed.

first I wondered if your version numbers were typos, or a broken '1'
key, but you used 2x.y.z instead of 12x.y.z so consistently I though you
must be complaining about a decade old firefox

> So I thought I'd pass on that bit of info.
> Ta da!
> End of story... :-)

In article <kv21blF7do2U2@mid.individual.net>,
Andy Burns <usenet@andyburns.uk> wrote:

> I don't think anyone on usenet expects to be protected from expletives,
> I actually wondered if "alpha 6" and "alpha 21" were some test-fork code
> labels, but couldn't find aything

Very good, I like that. :-)

As for expletives...
In the past Chris Ilias threw me off the old Fx Moz newsgroup a number of
times over the years for some comments he didn't like... Eventually fixing
me out at server level when I sneaked back as someone else. :-)

I'll admit to being a GOM back in the days... (Grumpy Old Man).
But...
As I've gotten older, I've become a mellow fellow and try not be be overly
offensive. :-/

> > I did some 'xperiments' and discovered it was the update from 20.0.1 to
> > the most recent 21.0 that had done the deed.

> first I wondered if your version numbers were typos, or a broken '1'
> key, but you used 2x.y.z instead of 12x.y.z so consistently I though you
> must be complaining about a decade old firefox

Fair comment...

I think it was a brain Fart of the n'th order on my part, as the "1" key
seems to be working okay.

Best wishes for this coming new year.

D.