MyPal 68

[Tomcat76]

3 hours ago, AstroSkipper said:

If you didn't move it, i.e. the button is still located on the tab bar, then try this code:

.tabs-newtab-button.toolbarbutton-1 {
  display: none !important;
}

Thanks for the suggestion.  It works, in the sense that it always hides the button.  It does the same with ".toolbarbutton-1" removed.  I only want it hidden when there's only one tab.  When there are multiple tabs, I want it back.  Basically, I want to mimic the behavior of the "Hide tab bar with only one tab open" addon.
 
It's weird, because the following should normally do the trick:

tab:only-of-type ~ .tabs-newtab-button.toolbarbutton-1{display:none !important;}

I observed the same issue with:

tab[first-visible-tab="true"] + .tabs-newtab-button{display:none !important;}

and

tab:only-of-type ~ .tabs-newtab-button{display:none !important;}

Oh well... Maybe I'll get used to the lone "+" button... :-)

[AstroSkipper]

7 hours ago, Tomcat76 said:

Thanks for the suggestion.  It works, in the sense that it always hides the button.  It does the same with ".toolbarbutton-1" removed.  I only want it hidden when there's only one tab.  When there are multiple tabs, I want it back.  Basically, I want to mimic the behavior of the "Hide tab bar with only one tab open" addon.
 
It's weird, because the following should normally do the trick:

tab:only-of-type ~ .tabs-newtab-button.toolbarbutton-1{display:none !important;}

I observed the same issue with:

tab[first-visible-tab="true"] + .tabs-newtab-button{display:none !important;}

and

tab:only-of-type ~ .tabs-newtab-button{display:none !important;}

Oh well... Maybe I'll get used to the lone "+" button... :-)

From a programming point of view, this is a condition. If there is only one tab, then hide the tab bar with the New Tab button. If there is more than one tab, then do not hide Tab Bar with the New Tab Button. Something like this should rather be realised with a JavaScript UC.JS file created inside the profile's chrome folder. 

Edited August 29, 2024 by AstroSkipper

[AstroSkipper]

@Tomcat76 I don't think your CSS code, which you didn't post here, is able to hide the tab bar, if only one tab is open, and immediately show it again when opening an additional tab, all in the same browser session.  For that, you need a script which checks the state of the tab bar in the background by an observer function. AFAIK, this can't be done with CSS but with JavaScript.

Edit: I have to correct a bit my statement above. In the special case of hiding the tab bar, when only one tab is open, it can be partially done in Mypal 68 even with CSS, as shown in the following post.

Edited August 30, 2024 by AstroSkipper
Update of content

[Tomcat76]

2 hours ago, AstroSkipper said:

@Tomcat76 I don't think your CSS code, which you didn't post here, is able to hide the tab bar, if only one tab is open, and immediately show it again when opening an additional tab, all in the same browser session.  For that, you need a script which checks the state of the tab bar in the background by an observer function. AFAIK, this can't be done with CSS but with JavaScript.

It's a combination of things.  If it isn't supposed to work, then why are these instructions all over the web?
 
This is what I use:

@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
 
/* Hide single tab -- works */
tab:only-of-type{display:none !important;}
 
/* Hide Open new tab button when only one tab is present -- doesn't work in MyPal 68 */
tab[first-visible-tab="true"] + .tabs-newtab-button{display:none !important;}
 
/* Reduce the minimum height of the tab bar to 0 so that it collapses when empty -- works */
#tabbrowser-tabs, #tabbrowser-arrowscrollbox, #tabbrowser-tabs > .tabbrowser-arrowscrollbox{min-height:0 !important;}

 

[dmiranda]

I can confirm that rebasing xul.dll (I also rebase mozavcodec.dll, libGLESv2.dll and nss3.dll) improves RAM usage by MyPal.  I'm trying the address proposed by @AstroSkippernow, but I used it with other addresses with good effects as well.

ALSO: running mypal in sandboxie (checl @Multibooter's thread in the general windows XP thread) is effective to prevent crashes when using more than a few tabs. Cheers!

[AstroSkipper]

16 hours ago, Tomcat76 said:

It's a combination of things.  If it isn't supposed to work, then why are these instructions all over the web?
 
This is what I use:

@namespace url("http://www.mozilla.org/keymaster/gatekeeper/there.is.only.xul");
 
/* Hide single tab -- works */
tab:only-of-type{display:none !important;}
 
/* Hide Open new tab button when only one tab is present -- doesn't work in MyPal 68 */
tab[first-visible-tab="true"] + .tabs-newtab-button{display:none !important;}
 
/* Reduce the minimum height of the tab bar to 0 so that it collapses when empty -- works */
#tabbrowser-tabs, #tabbrowser-arrowscrollbox, #tabbrowser-tabs > .tabbrowser-arrowscrollbox{min-height:0 !important;}

 

Ok. I can confirm that your code is indeed working except hiding the Open new tab button when only one tab is open. My recommendation is to move the Open new tab button to another toolbar, for example to the left of the url bar or to the right of the search bar, via the toolbar menu entry Customize.  Doing so, this code is enough:

/* Hide single tab -- works */
tab:only-of-type{display:none !important;}
 
/* Reduce the minimum height of the tab bar to 0 so that it collapses when empty -- works */
#tabbrowser-tabs, #tabbrowser-arrowscrollbox, #tabbrowser-tabs > .tabbrowser-arrowscrollbox{min-height:0 !important;}

The moved Open new tab button does no longer cause wasting of screen space. Another solution without the need of moving the Open new tab button will be posted by me, too. 

Edited August 30, 2024 by AstroSkipper

[NotHereToPlayGames]

I'm finally getting around to giving Mypal 68 a trial run.

First, why is the title of this thread called MyPal with a capital P?

Second, based on Speedometer 2.1 scores, this scores 2.2 times faster than Serpent 52 - telling me I should have switched a LONG time ago, lol.

Third, if I drag the edges of a NON-MAXIMIZED window to fill my entire screen, then close and relaunch, why does Mypal (lowercase p) shift to the right by 3-5 pixels or so?

So far, I've only tested in Win10 (to replace my webmail-use-only Serpent 52).  Speedometer scores tell me it will be used on my XP Acer Aspire One (which has a slower CPU than even AstroSkipper uses).

[mina7601]

1 hour ago, NotHereToPlayGames said:

First, why is the title of this thread called MyPal with a capital P?

It's normal. We also say FireFox with a capital F.

[NotHereToPlayGames]

For Mypal, what is the "em:id" for an extension's "install.rdf"?

Edited August 30, 2024 by NotHereToPlayGames

[NotHereToPlayGames]

9 minutes ago, mina7601 said:

It's normal. We also say FireFox with a capital F.

wElL tHaT's JuSt WrOnG  

[NotHereToPlayGames]

1 hour ago, NotHereToPlayGames said:

Third, if I drag the edges of a NON-MAXIMIZED window to fill my entire screen, then close and relaunch, why does Mypal (lowercase p) shift to the right by 3-5 pixels or so?

This appeared promising, but I cannot get Stylish to customize anything in Mypal.

https://support.mozilla.org/en-US/questions/928428

[UCyborg]

52 minutes ago, NotHereToPlayGames said:

For Mypal, what is the "em:id" for an extension's "install.rdf"?

Probably same as Firefox/Basilisk.

But that applies to classic extensions, of which very few may run in Mypal, I doubt anyone that maintains them checks Mypal. Firefox needs some hacks to load specially adapted bootstrapped extensions, one and only remaining kind of classic extensions that may still be loaded.

https://github.com/xiaoxiaoflood/firefox-scripts

Mostly, you're looking for Web Extensions, which have manifest.json rather than install.rdf.

Edited August 30, 2024 by UCyborg

[NotHereToPlayGames]

7 minutes ago, UCyborg said:

But that applies mostly for classic extensions, of which very few may run in Mypal

Yep, that is what I have ran into.  The few extensions that I use(d) for Serpent 52 won't be able to be migrated to Mypal 68.  

I technically only use it/them (Serpent 52 and/or Mypal 68) for Gmail and Google Voice and nothing else so I kind of have to ask myself "why even bother" with updating my one-year-old St52 to either a newer St52 or to Mypal 68).

Other than St52 is the SLOWEST D#MN THING that I have ever witnessed on my old Acer Aspire with in Intel Atom CPU.

Though to be fair I have not tried Mypal 68 on it yet.  Supermium is a no-go and Thorium works but too new just for Gmail and Google Voice.

[AstroSkipper]

3 hours ago, UCyborg said:

But that applies to classic extensions, of which very few may run in Mypal, I doubt anyone that maintains them checks Mypal. Firefox needs some hacks to load specially adapted bootstrapped extensions, one and only remaining kind of classic extensions that may still be loaded.

https://github.com/xiaoxiaoflood/firefox-scripts

 

3 hours ago, NotHereToPlayGames said:

Yep, that is what I have ran into.  The few extensions that I use(d) for Serpent 52 won't be able to be migrated to Mypal 68.  

Personally, I am not really interested in running legacy extensions in Mypal 68. I am more interested in working UC.JS scripts and CSS stylesheets. But there was one legacy extension that I really wanted to get running and was finally able to install in Mypal 68 long time ago. It's the legacy Custom Buttons extension. Here is a screenshot:



The advantage in using legacy custom buttons in Mypal 68 is that they are not restricted in their actions as, for example, webextensions unfortunately are.   Legacy custom buttons just do what their JavaScript code commands them, whatever that may be.

Edited August 30, 2024 by AstroSkipper
Update of content

[Tomcat76]

5 hours ago, NotHereToPlayGames said:

Second, based on Speedometer 2.1 scores, this scores 2.2 times faster than Serpent 52 - telling me I should have switched a LONG time ago, lol.

I haven't used any tools to measure the speed, but I did notice a significant speed bump compared to Serpent 52 as well, especially on Youtube.
 

3 hours ago, NotHereToPlayGames said:

The few extensions that I use(d) for Serpent 52 won't be able to be migrated to Mypal 68.  

Yes.  For me, that includes Classic Theme Restorer, Downloads Window and Session Manager.  Also, the Open in browser extension doesn't run properly: I get two dialog boxes asking me what to do.  In Serpent (which uses an older version) it's only one.
 
To be fair, though, that's Mozilla's doing.  They switched to Web Extensions which have much less control over the UI.