Is the "Hide Caption Titlebar Plus" extension still the best solution for hiding the titlebar on Linux?

[__NM64__]

I was wondering if Hide Caption Titlebar Plus was still the best solution for hiding the titlebar on Linux to achieve the GUI appearance that debuted back with Firefox 4 on Windows. In particular, I previously stated that v2.7.3.1 seems to work perfectly fine, possibly due to it being the last pre-Australis version (v4.1.1 "works" but does have some quirks however; same goes for v2.8.2.1, v2.8.6.1, and v2.8.7rc).

The main thing is that, despite my essentially non-existent software-dev skills, I spent the last few hours copying and pasting what looked like relevant code from version 2.8.6.1 to version 2.7.3.1 to successfully backport the "autohide the toolbar buttons in Full-Screen mode" setting (I'm honestly kind of amazed doing this "just work" considering that I don't really understand the actual lines of code in question).

However, I was wondering if I was a bit hasty and maybe there's was already a better solution? In particular, it's looking like the function introduced in v2.8.9.1 (in fact is one of if not the only change relative to v2.8.8.1) to still show the toolbar buttons in fullscreen whenever the toolbar is visible may be a function exclusive to Australis—either that, or the developer of the extension simply did not implement such a function until the extension had already dropped support for non-Australis (the latter of which occurred with v2.8.8.1).

—————————————————

At least for documentation purposes, here are the lines of code to modify in v2.7.3.1 to backport the aforementioned "autohide the toolbar buttons in Full-Screen mode" setting (you'll also probably want to increment the version number or something in the install.rdf file); all three of the modified files are located in chrome/fx4/content/

In the file HCPlusLib.js add the following at line 473:

Code: Select all

		// fullscrButs_autohide
		this.arrayOptions.push( new HCPlusLib.Hcp_PrefValue( "BOOL_PREF", "plus.home.fullscrButs_autohide"   	   , function(option_hPrefVal){
			option_hPrefVal.setAsDomAttribute(document.getElementById("main-window"));
		  }, true                 , true )  ); 

In the file opt_look2_home.xul add the following at line 114 (if for some reason you did the 3rd step before this one, then it may be at line 116 or 117 instead):

Code: Select all

<groupbox style="">
 <caption> Full-Screen mode option: </caption>
  <hbox class="baseline  inline" flex="1">
		<checkbox id="check_fullscrButs_autohide" preference="fullscrButs_autohide"  flex="1"
		 	label="Autohide also Firefox 'Home' Button and Custom-Min,Max,Close buttons when autohiding Toolbars in Full-Screen mode   (default: yes)"
			/>
  </hbox>
</groupbox>

Also in the file opt_look2_home.xul add the following at line 32:

Code: Select all

	<preference id="fullscrButs_autohide"            name="extensions.hide_caption.plus.home.fullscrButs_autohide" type="bool"   instantApply="true" onchange="" />

In the file overlay.xul replace the entire existing line of code on line 28 with:

Code: Select all

		<hbox id="hcp-rightbar-fixed" context="hcp-menu-windowcontrols"  class="collapseWith_fullscrBars">

Also n the file overlay.xul replace the entire existing line of code on line 159 with:

Code: Select all

			class="collapseWith_fullscrBars  hc-hideon-fx4titlebar-all-platform" 

[billmcct]

Could you add some screen shots of the end results?
I've been using v2.8.7rc since forever it seems.
Has lots of bugs, especially in Win 10.

[__NM64__]

Oh whoops, I didn't realize that 2.7.3.1 wasn't available for download from the link I gave because that version was marked as "Windows only" (even though it seems to work great on LInux?) and it seems that archive.org doesn't use a Windows user agent when creating snapshots of webpages, so a download link wasn't even listed for 2.7.3.1.

There is an alternative archive.org link for 2.7.3.1 but, last I knew of from a few years back, directly linking to XPI files from random sources would be against the rules since the orig
inal server was not addons.mozilla.org... Otherwise you can just get 2.7.3.1 from the Classic Add-ons Archive.

I've been using v2.8.7rc since forever it seems.
Has lots of bugs, especially in Win 10.

It's not clear from your post what you're trying to achieve, but keep in mind that the GUI appearance that debuted back with the Windows version of Firefox 4 is natively supported in the Windows version of Pale Moon and does not require an extension—all you need to do is press the "Alt" keyboard key and then enable the following menu option:

• View ▶ Toolbars ▶ Tabs on top

(to be clear, this is with a stock unmodified Pale Moon user profile)

Could you add some screen shots of the end results?

Could you not just get a copy of Pale Moon portable and install 2.7.3.1 to try for yourself?:

• https://www.palemoon.org/download.shtml ... e_versions

My modification doesn't actually change the visual result of 2.7.3.1, I just really wanted the toolbar buttons to not be visible during fullscreen video, but that was a setting not introduced until 2.8.6.1.

And, to be clear, and various GUI bugs is a big reason I wanted to stay with 2.7.3.1 because the very next version, 2.8.2.1, is where themes and stuff begin to no longer look quite right (and this persists with the newest 4.1.1 as well).

[Lootyhoof]

Version 4.2.0 worked quite well from what I recall. You can find it here: https://addons.thunderbird.net/en-GB/th ... -plus-sma/

I'd actually contacted the developer a few years ago to try to get them to add it to our site, but they went quiet.

[__NM64__]

Version 4.2.0 worked quite well from what I recall.

On the contrary, it has the same graphical errors as 2.8.2+, at least when paired with your Moonfox3 theme regardless of whether your customuserChrome.css for the blue "Pale Moon" button is used or not.

There are three main issues that do not exist in 2.7.3.1:

• an incorrectly-sized back button
• your userChrome.css results in a tiny 2 pixel-wide "Pale Moon" button
• enabling the custom "Pale Moon" button adds a second button rather than replacing the existing

But on 2.7.3.1...

• the back button has the correct sizing
• your userChrome.css works and looks perfect
• enabling the custom "Pale Moon" button does nothing, preserving the perfect Pale Moon button from your userChrome.css

(also a minor benefit of 2.7.3.1 is that it uses slightly less vertical space)

[Lootyhoof]

There are three main issues that do not exist in 2.7.3.1:

an incorrectly-sized back button
your userChrome.css results in a tiny 2 pixel-wide "Pale Moon" button
enabling the custom "Pale Moon" button adds a second button rather than replacing the existing

Sorry but in regards to the first note this is likely due to the toolbar button sizing option within HCTP. Such options are largely catered to the default theme and can't reasonably be expected to work on custom themes. With regards to your other notes, the original appmenu-toolbar-button can be removed to produce a result like so, which looks reasonably close to the Windows counterpart (ignoring some oddities of my current GTK theme):

I used the below (can replace the other userChrome.css you used previously) which uses only the HCTP button and not the original and uses the correct dropmarker image.

Code: Select all

#appmenu-toolbar-button .toolbarbutton-icon {
  display: none !important;
}

.hctp-appmenu-button-cls  > .button-box > .button-menu-dropmarker {
  list-style-image: url(chrome://browser/skin/appmenu-dropmarker.png);
  -moz-image-region: auto;
}

If you do truly want additional screen real estate while wanting something resembling Firefox 3 then I would suggest you use Compact Moon (with Options) and choose the Firefox 3 WinXP iconset while using HCTP for the tabs-in-titlebar effect. Note that this isn't really in line with the original Firefox 3 design though which is what I was under the impression you were aiming to achieve.