Pale Moon forum

Posted: **2017-08-10, 19:09**

Hi, thanks for your updates on themes.

The private mask with Fox 2 The Moon appears on menubar on windows, but not on linux. The theme is up to date on both systems. What could cause this?

See my screenshot:

: screenshot of windows and linux palemoon private windows with fox 2 the moon theme enabled

Case_Of.

Posted: **2017-08-19, 20:52**

Aeromoon has been updated to v2.0.0! This release folds in a large amount of work as done recently in Phoenity Rebirth, as well as a few other fixes.

What's new?
- refactor toolbarbutton styling
- refactor tab styling
- unify platform stylings
- add basic OS X support
- add CSS variables for increased customization
- add private browsing indicator in menubar and (Linux only) tabbar
- sync devtools styling with default
- improve sidebar appearance on Windows
- fix appmenu/caption button margins when tabs are in the titlebar
- improve tab appearance in tabs in titlebar mode
- add missing HTTPS icon for devtools network panel
- ensure that all notification panel icons are shown correctly
- fix notification icon selectors
- fix page info dialog styling
- sync plugins UI with default
- PM27.5: draw a background on Win10 for better accent color detection
- remove Social API components
- major cleanup of stylings

Case_Of wrote:Hi, thanks for your updates on themes.

The private mask with Fox 2 The Moon appears on menubar on windows, but not on linux. The theme is up to date on both systems. What could cause this?

See my screenshot:
Capture d’écran_2017-08-10_21-05-44.png
Case_Of.

Updates for this are coming soon.

Posted: **2017-08-20, 01:10**

Aeromoon 2 looks very crisp. Many thanks

Posted: **2017-08-24, 10:13**

Lootyhoof, do you experience this on Pale Moon Unstable?

Theme: Darkness 1.7.0

: darkness.jpg (49.9 KiB) Viewed 2834 times

Posted: **2017-08-24, 20:49**

Latitude wrote:Lootyhoof, do you experience this on Pale Moon Unstable?

Theme: Darkness 1.7.0

darkness.jpg

Hmm...confirmed. I'll take a look into it soon.

Posted: **2017-09-03, 18:46**

Aeromoon, Darkness and Fox 2 The Moon have been updated to fix some minor issues.

Additionally, Moonfox3 has been updated to v2.0.0, bringing it in line with other Firefox 3-alike themes I develop.

Please see the changelogs on GitHub for full details.

Posted: **2017-09-05, 03:04**

Lootyhoof wrote:Moonfox3 has been updated to v2.0.0, bringing it in line with other Firefox 3-alike themes I develop.

This broke the blue "Pale Moon" menu button on Linux Mint 18.1 x64 Cinnamon and now it only shows a plain hamburger menu icon; it's not due to a conflict with one of my extensions either because it happens even with all extensions disabled (click "show" to see screenshot):

v1.6.0 by comparison does not have this problem (click "show" to see screenshot):

Posted: **2017-09-05, 23:41**

Nintendo Maniac 64 wrote:
Lootyhoof wrote:Moonfox3 has been updated to v2.0.0, bringing it in line with other Firefox 3-alike themes I develop.
This broke the blue "Pale Moon" menu button on Linux Mint 18.1 x64 Cinnamon and now it only shows a plain hamburger menu icon; it's not due to a conflict with one of my extensions either because it happens even with all extensions disabled (click "show" to see screenshot):
v1.6.0 by comparison does not have this problem (click "show" to see screenshot):

This change is intentional and by design. If you need the blue menu button still, does the Blue Moon Linux extension work?

I'm currently away from home, though I'll try to think up a userstyle when I'm back in a few day's time if that doesn't help.

Posted: **2017-09-06, 02:03**

Lootyhoof wrote:This change is intentional and by design.

But on my Windows 7 PC, Moonfox3 v2.0.0 still shows the blue "Pale Moon" button...

Lootyhoof wrote:If you need the blue menu button still, does the Blue Moon Linux extension work?

I think it broke with Pale Moon v27 or something...but I could be wrong. But even then, Blue Moon Linux isn't as ideal because, on a maximized window, the button has a one-pixel gap between the edge of the screen and the button itself which prevents the user from just putting the mouse pointer against the edge of the screen and clicking to open the menu (like can be done on Windows).

Posted: **2017-09-06, 23:19**

Just did some more testing and I can confirm that "Blue Moon Linux" is completely non-functional on Pale Moon v27.4.2 on Linux Mint 18.1 Cinnamon.

I can also confirm that v2.0.0 of both Aeromoon3 and Moonfox3 show the blue Pale Moon button on Windows 7, yet both show a hamburger menu icon on Linux Mint 18.1 Cinnamon. I would think that this discrepancy in appearance between different OSes would be undesirable...

Posted: **2017-09-06, 23:35**

As mentioned, this is intentional.

The blue Pale Moon button makes sense on Windows because it's designed to look similar to, but still visually different from, the caption buttons on the windows.

On Linux, we don't have client side decorations at the moment, and even then, the caption buttons typically don't look like the Windows ones. I added the blue button on an earlier version of Moonfox3 to at least reach visual parity with the Windows version, however in 2.0.0 I revised this to make more sense for the platform. It makes most sense in Gnome-like environments (where they seem to be using this quite a lot lately), though still also does its job as intended elsewhere: you have compacted the menu bar and so are presented with a menu button, typically styled as a hamburger.

If this isn't desired you can of course change this with CSS.

Posted: **2017-09-07, 00:41**

Lootyhoof wrote:This change is intentional and by design. If you need the blue menu button still, does the Blue Moon Linux extension work?

The Blue Moon Linux page states that it is only good thru version 26, so it unsurprising that users are reporting that it is broken in PM 27.

I also get the hamburger menu in Aeromoon and Moonfox, installed in Ubuntu 14.04.5.
So the hamburger menu is meant to be Linux-only?

Posted: **2017-09-09, 18:40**

gracious1 wrote:
Lootyhoof wrote:This change is intentional and by design. If you need the blue menu button still, does the Blue Moon Linux extension work?
The Blue Moon Linux page states that it is only good thru version 26, so it unsurprising that users are reporting that it is broken in PM 27.

I also get the hamburger menu in Aeromoon and Moonfox, installed in Ubuntu 14.04.5.
So the hamburger menu is meant to be Linux-only?

Correct, the hamburger is only for Linux. As this button is Linux-specific (it's treated slightly differently to Windows' appmenu button) I felt it appropriate that this be styled specific to the platform it's featured on.

If anyone needs to restore the previous button, they can use this style in either userChrome.css or Stylish:

Code: Select all

#appmenu-toolbar-button {
  -moz-appearance: none;
  list-style-image: none !important;
  background-clip: padding-box;
  border-radius: 0 0 4px 4px;
  border: 1px solid;
  border-top: none;
  color: white;
  text-shadow: 0 0 1px rgba(0,0,0,.7),
               0 1px 1.5px rgba(0,0,0,.5);
  font-weight: bold;
  padding: 0 1.5em .05em;
  margin: 0 0 2px;
}

#appmenu-toolbar-button:hover:active,
#appmenu-toolbar-button[open] {
  border-radius: 0;
}

#appmenu-toolbar-button {
  background-image: linear-gradient(rgb(82,182,247), rgb(10,98,215) 95%);
  border-color: rgba(6,42,83,.9);
  box-shadow: 0 1px 0 rgba(255,255,255,.25) inset,
              0 0 0 1px rgba(255,255,255,.25) inset;
}

#appmenu-toolbar-button:hover:not(:active):not([open]) {
  background-image: radial-gradient(farthest-side at bottom, rgba(89,240,252,.5) 10%, rgba(89,240,252,0) 70%),
                    radial-gradient(farthest-side at bottom, rgb(60,68,236), rgba(172,229,255,0)),
                    linear-gradient(rgb(69,170,246), rgb(30,40,209) 95%);
  border-color: rgba(6,42,83,.9);
  box-shadow: 0 1px 0 rgba(255,255,255,.1) inset,
              0 0 2px 1px rgba(169,234,250,.7) inset,
              0 -1px 0 rgba(169,234,250,.5) inset;
}

#appmenu-toolbar-button:hover:active,
#appmenu-toolbar-button[open] {
  background-image: linear-gradient(rgb(69,170,246), rgb(0,74,209) 95%);
  box-shadow: 0 2px 3px rgba(0,0,0,.4) inset,
              0 1px 1px rgba(0,0,0,.2) inset;
}

#main-window[privatebrowsingmode=temporary] #appmenu-toolbar-button {
  background-image: linear-gradient(rgb(153,38,211), rgb(105,19,163) 95%);
  border-color: rgba(43,8,65,.9);
}

#main-window[privatebrowsingmode=temporary] #appmenu-toolbar-button:hover:not(:active):not([open])  {
  background-image: radial-gradient(farthest-side at bottom, rgba(240,193,255,.5) 10%, rgba(240,193,255,0) 70%),
                    radial-gradient(farthest-side at bottom, rgb(192,81,247), rgba(236,172,255,0)),
                    linear-gradient(rgb(144,20,207), rgb(95,0,158) 95%);
  border-color: rgba(43,8,65,.9);
  box-shadow: 0 1px 0 rgba(255,255,255,.1) inset,
              0 0 2px 1px rgba(240,193,255,.7) inset,
              0 -1px 0 rgba(240,193,255,.5) inset;
}

#main-window[privatebrowsingmode=temporary] #appmenu-toolbar-button:hover:active,
#main-window[privatebrowsingmode=temporary] #appmenu-toolbar-button[open] {
  background-image: linear-gradient(rgb(144,20,207), rgb(95,0,158) 95%);
}

#appmenu-toolbar-button > .toolbarbutton-menu-dropmarker {
  list-style-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAAAkAAAAHCAYAAADam2dgAAAAAXNSR0IArs4c6QAAAAZiS0dEAP8A/wD/oL2nkwAAAAlwSFlzAAAcIAAAHCABzQ+bngAAAAd0SU1FB9oGCgsoOOaGefgAAACGSURBVBjTdc8xCsJAAETRp6kkKqwgGKy0CN5DPIKFeF5PYWGlB7CJSXZZGwUR/TDNDAwzA4wx8Z8Gpk3TnFJK8Vt9318wg3lZlrsY4z1/0LbtGVssYIg6hHBIKT1yzjnGeMce61cOCmyqqjp2XXcLIRxQv3yDj4EFVljiigvSrycFRu+GN08PhkZJ2TW5PwAAAABJRU5ErkJggg==');
  width: auto;
  height: auto;
  padding: 0;
  margin: 0;
  -moz-margin-start: .5em;
}

#main-window[privatebrowsingmode=temporary] #appmenu-toolbar-button > .toolbarbutton-icon {
  list-style-image: url('data:image/png;base64,iVBORw0KGgoAAAANSUhEUgAAABQAAAAQCAYAAAAWGF8bAAACf0lEQVR42q2UW2hScRzH/Xs7Hu1oOaVwNqq11DWYVg8taF0ftkEQi1Wsy0MXNwhG9bDM2N7qJYiocJf21Ev11IJisGRbW2muOcxr02RdSHtJjyGYIdrvB+eASD4EPnzg/C7fD+f/P6KgVCrVFEGDSkg4hIAIkAAUIOeguJ64Sl+EcHkiwIIbMoAaWA/ogS3AZqAe0AIaQIc9Dj3uchkl5xChUFrPCNV+n/dKd+f+Pfarl06437weYdn0UqFQWF2JhJ627zDuNTduaPN530/8yefjOHMtzDkGB/p6Tnd37Qv5fTYdI9SgC4UyrYI0plI/PXAHiX8Ri36cioSDz6vNIbsIjiZw0SiU19HEHIuuzPMLxWLxez6f/1pNALNv5TVkF9CBLhTSWPiWvTM4nBgfnWxtNtxUSIn9bO9JRzqVivFBeP7Uf/H8OEOJblhaTLcejo1MYj/g/zCnpomFf0MKiubZGeczbjh/7EjHZY2cHF8rI+fu3rn9iBeOOu4/xh7OjnYdHlj2Ls1iH7PoQBcKxVBsGrp+baj8GL9zuWgmwwZyudxq2VG//Mpkgjgr3x2224bRgS4UCuHIdYyUHAgG/C5c+B8i4ZAHsofQgS4UEvhClIoiTW27LNZkIhGuDLldb92Lnneeyv6PZDKye6e5T0mRbejgf9gIgbth1kiJucWw1Tr18sV0hmXjII/YbYNjcgm5AFgdD+49YdPpeDab/ex8Ne1s3W7sxwxm8e3QhTIeoUpGlBA00mLSIROTU0AP1O0QMgAmWkIOQq8XOAM7nTAzYYaXVQoRAgsyWNRCQA8CHYhUcOES6EsVErIOehuBBtxhKEJjptxR63+b2gv/AkhRdgoVlHrNAAAAAElFTkSuQmCC');
}

#main-window[privatebrowsingmode=temporary] #toolbar-menubar[autohide="true"] ~ #TabsToolbar::before {
  display: none !important;
}

#appmenu-toolbar-button > .toolbarbutton-text,
#appmenu-toolbar-button > .toolbarbutton-menu-dropmarker {
  display: -moz-box !important;
}

Posted: **2017-09-09, 20:11**

I still don't really understand the logic going on here...

Moonfox3 and Aerofox3 are both pretty much ports of the Windows Firefox 3 themes, and both themes back in the day had an orange Firefox button. Not only that, but the entire concept of a hamburger menu wasn't even invented when Firefox 3 was a thing (as an example, earlier versions of chrome used a wrench for its menu icon).

Therefore, deviating away from how the menu button looked on a theme that's supposed to mimic an old theme just feel likes, dare I say it, "George Lucas-ification". I mean, if a Linux user chooses to use one of these themes, wouldn't the entire reason be because they want to re-create that older Windows UI experience (at least in their browser?).

Now obviously the blue Pale Moon button doesn't exactly match as the text and color is different from Firefox 3, but as Pale Moon itself has natively had this "blue Pale Moon button" UI element on Windows for literally years now, I think we can make an exception specifically for that.

Posted: **2017-09-09, 20:30**

The menu button was created for Firefox 4, though. Therefore, any work surrounding it is extrapolation of the original vision of the theme. It's hardly "deviating away from how the menu button looked". Additionally, this button didn't even exist in this form before I started work on it. For example, here's how this looks in the default theme:

I'm not sure I understand the argument here. On Linux, this button behaves differently to how one would expect in the Windows world. For example, if we take Moonfox3 and have tabs-on-bottom:

Then apply the userstyle I provided above:

How is this at all relatable to Windows users, who would expect this menu to remain at the top regardless of their tabs position? For that matter, for those who are looking for the true Firefox 3 experience, wouldn't they instead have the menu bar enabled? It's also common knowledge at this point that a hamburger is a menu button - as this isn't the appmenu on Windows, how would you represent it? There was no such button on Firefox 3, and the version offered since Firefox 4 in the default theme (and the version of this theme before I forked) simply provides the name of the program - which should already be available via the window manager.

Posted: **2017-09-09, 20:51**

OK, you're right on the browser UI history - it was Firefox 4 that introduced both the Firefox button and "tabs on top". The thing is, back in the days of Firefox 4, I recall using a theme that did nothing but had the Firefox 3 buttons (similar to the way Moonfox3 behaves on Windows, or on Linux pre-v2.0.0), so it's no surprise that I mixed them up.

But even if I was incorrect on my browser UI history, I also still don't understand why a single custom theme should basically behave as actually being two different themes depending on the OS. If a user previously used Moonfox3 on Windows and then goes to install it on Linux (or heck even vice-versa), shouldn't the user expect the theme to look exactly the same? It is the exact same theme after all. I mean, It's not like the user is presented with the "Aerofox3" buttons if they install "Moonfox3" on Windows Vista/7 simply because "it's Windows Vista/7" (much like what Mozilla did back in the day of Firefox 3).

Honestly, changing the behavior of the exact same piece of software purely based on the OS it is ran on for reasons that aren't technical in nature feels kind of like the application equivalent of user agent sniffing. In this case, does it not just make more sense to have two separate themes - one for each behavior? You provided "Aerofox3" and "Moonfox3" as separately-available themes after all.

Yes the default Pale Moon theme and the like may have differences from the Windows version, but it's not actually the exact same downloaded file (for one, there's no EXE files on the Linux version). Themes and extensions on the other hand are the exact same XPI between OSes - you can stick it on a USB drive and install the same XPI file onto both a Windows Pale Moon and a Linux Pale Moon.

Posted: **2017-09-09, 21:07**

The theme changes per OS to integrate better with it. Usually this is just to make sure that things aren't broken (for example, we offer native toolbarbutton stylings for each OS correctly), but also to improve the appearance on a specific platform. The work required here pretty much warrants its own theme for each platform, but I manage to squeeze them into one theme (you can see the sort of work I do here). For a particularly wild example, see Australium:

Windows 10:

Windows 7:

Linux:

While this isn't as noticeable as the example above, it does show that I do put work into making themes look better on specific platforms - the core of the theme stays the same, while trying to look a bit better on the platform in question. That doesn't mean to say that I (usually) make too many radical changes, just enough to complement the theme in general on specific platforms.

Posted: **2017-09-09, 21:31**

...yeah I'm not really much of a believer in "OS integration" since most people don't choose a specific OS due to its GUI aesthetic, and I'd much rather have a program have the same UI regardless of platform for familiarity sake (VLC is a good example of this).

Then again, I'm the same person that has been using the Windows "high contrast black" theme for possibly over a decade now and have even used it across Windows versions (at least XP and 7), so I'm used to having programs not match my OS theme.

(there's also the fact that I do a lot with emulation, so I'm extremely used to running software that was originally designed for a completely different hardware platform let alone a different OS)

Posted: **2017-09-10, 06:53**

Lootyhoof wrote: While this isn't as noticeable as the example above, it does show that I do put work into making themes look better on specific platforms - the core of the theme stays the same, while trying to look a bit better on the platform in question. That doesn't mean to say that I (usually) make too many radical changes, just enough to complement the theme in general on specific platforms.

I appreciate that. It does actually add to the appeal of the browser and the theme.

Posted: **2017-09-10, 14:35**

Nintendo Maniac 64 wrote:...yeah I'm not really much of a believer in "OS integration" since most people don't choose a specific OS due to its GUI aesthetic

You would be surprised how many people would argue against that.

Just because something looks fine for YOU doesn't mean it does for everyone else. I'd honestly love to not have to style things for each platform, but unfortunately due to the way the UI toolkits for each platform works it means that specific styling has to be used to make things look about similar, and even then people historically tend to prefer something that at least somewhat integrates nicely with their OS.

As I've mentioned before, if you don't like this change you can always change it back using the userstyle I posted. There is no "my way or the highway" here considering it's all using configurable CSS anyway.

Pale Moon forum

[Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks

Re: [Release] Various theme ports/forks