Pale Moon forum

Is it just me or is the text cursor thicker, almost "bold", in the 2018-01-03 build?

The same thick text cursor is in the 2018-01-05 build.

I'd like to know if this is intentional or not, because if it is I'd appreciate for there to be a way to revert it to the original width that is currently still present in the latest proper release (27.6.2).

I'm not sure what you mean. I see no difference in the text cursor between current release and current unstable on my system.

trava90 wrote:I see no difference in the text cursor between current release and current unstable on my system.

Would you mind telling me what desktop environment and window theme you use? I'm on the Cinnamon desktop (which was forked from the GNOME 3 desktop) with the Vertex-Light window theme.

I am using XFCE with the Vertex-Maia-Dark theme.

Here's what the text cursor looks between the two browser versions: 27.6.2 vs 27.7.0a2 (18-01-05). As you can see, the unstable build's cursor looks bold.

Yes, I see the same "bold" cursor also, on the last two unstable builds. Not a big issue for me...

When clicking on the address bar I can see the difference now. Not sure offhand what has caused this change however.

Could it be this?

Holidays are over and it's Monday again. The latest 32-bit unstable linux build tarball is available for download at URL

ftp://contrib:get@ftp.palemoon.org/32bit-unstable-Linux/palemoon-27.7.0a2_180108.linux-i686.tar.bz2

Note for the developers. On web page http://www.palemoon.org/unstable/releasenotes.shtml under Current trunk progress since release (major changes only): are 2 entries...

1. Removed referrers when opening links in a new private window.
   Removed the sending of referrers when opening a link in a new private window.

SpockMan02 wrote:Could it be this?

I'm genuinely curious as to why that change was made, because from what I can tell all it did was make some UI things unnecessarily thicker.

hobbledehoy899 wrote:

SpockMan02 wrote:Could it be this?

I'm genuinely curious as to why that change was made, because from what I can tell all it did was make some UI things unnecessarily thicker.

Browser-parity apparently.. Not sure how I feel about this.

Perhaps the affected UI elements can just be made 1 pixel instead of 1.whatever (rounded up to 2)? That way, things would display the same as in other browsers, but the UI wouldn't change. Someone would have to find all of the little things, though, and change them.

I'm not sure I really what the problem is if the cursor is a little bit more prominent? (I like the change, and I usually don't like change. )

gracious1 wrote:I'm not sure I really what the problem is if the cursor is a little bit more prominent?

Not only is it not uniform to the rest of the operating system's text fields, but it also makes reading the two letters that the cursor are next to harder.

I like the change, and I usually don't like change.

I'm not going to lie, I think you have a poor taste in changes.

New Tobin Paradigm wrote:Browser-parity apparently.. Not sure how I feel about this.

Not just browser parity.
Everything else in the CSS world is rounded to the nearest pixel for display rendering (to keep crisp edges), but in the Mozilla world, borders are treated differently and always rounded down. That's incorrect and leads to improperly-thin borders on elements, especially when scaled/zoomed/on different DPI than 1:1

The cursor is treated like a border, internally (don't ask me why Mozilla chose this approach). If that's not what people want, then I'll adjust the implementation to separate the algorithms out for borders and caret.

hobbledehoy899 wrote:I'm not going to lie, I think you have a poor taste in changes.

Just because you don't like it, doesn't mean it's necessarily something to tell someone else off for "having poor taste".

@hobbledehoy899

Your first point is well received and totally understandable and quite valid.. Your second, not so much.. But fear not, despite your less than constructive criticism on Point 2.. Point 1 shall be looked into.

Fact is, the change was the proper thing to do.. That it has a side-effect elsewhere is just something to be evaluated and resolved one way or another. Please consider this for the next time for no reason other than.. No one wants to do things for people when they act that way... Alright?

It's Monday again. The latest 32-bit unstable linux build tarball is available for download at URL

ftp://contrib:get@ftp.palemoon.org/32bit-unstable-Linux/palemoon-27.7.0a2_180115.linux-i686.tar.bz2

I have took it upon myself to add the x86_64 unstable builds of Pale Moon to the Arch User Repository, here's the link.