Add-on "LessChrome HD" not working since 28.7.0

[MonoS]

Hi, after updating to the latest version of Pale Moon (28.7.0) the add-ons LessChrome HD is not working anymore. Could someone give me the information or the help necessary to fix this and make it work with the latest version?

Regards.

[moonbat]

The link you posted indicates that the addon is gone, and indeed it does not exist either on AMO or CAA.

[MonoS]

The link you posted indicates that the addon is gone, and indeed it does not exist either on AMO or CAA.

You are right, my apologies, i've attached to this post the .xpi i'm using (it should already have the GUID fix)

[moonbat]

Generally, posting XPIs as attachments here is frowned upon. At any rate, the last thing you should expect to work (miracle that it even did) is anything to do with the UI since Firefox introduced Australis. If you're unable to find a link to the XPI anywhere, that itself should tell you how well supported or compatible this is even with Firefox itself, let alone PM which was forked and developed independently ages ago.

[Moonchild]

Since the extension isn't available anywhere else it's OK as an exception.

Do note that this is a "Mozilla Labs" experiment, and not actually meant as something to use in production.

Prospector is a series of experiments from Mozilla Labs focused on analyzing, experimenting and prototyping enhancements for how you search and discover content with Firefox.

[MonoS]

Generally, posting XPIs as attachments here is frowned upon. At any rate, the last thing you should expect to work (miracle that it even did) is anything to do with the UI since Firefox introduced Australis. If you're unable to find a link to the XPI anywhere, that itself should tell you how well supported or compatible this is even with Firefox itself, let alone PM which was forked and developed independently ages ago.

The addons worked until the latest pale moon update, i don't expect it work in current version of firefox due to australis and whatnot.
I've tried to find a more "official" release, but all i could find was the github repository https://github.com/mozilla/prospector/releases/tag/lessChromeHD9

I don't even know if there is a different addon that do the same as i've used LessChrome HD since it came out (i've also opened an issue in 2011)

[billmcct]

Classic add-ons archive:

caa:addon/prospector-lesschrome-hd

[JustOff]

You need to get rid of the reserved keyword "async" in variable and function names, for example like this.

[MonoS]

You need to get rid of the reserved keyword "async" in variable and function names, for example like this.

Thank you JustOff, if i may ask how have you noticed that such a change was required?

[JustOff]

Error Console shows this error:

Code: Select all

Error loading bootstrap.js for lessChrome.HD@prospector.labs.mozilla: SyntaxError: expected property name, got ',' (resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///D:/PaleMoonPortable28.7.0/User/Palemoon/Profiles/Default/extensions/lessChrome.HD@prospector.labs.mozilla.xpi!/bootstrap.js:50:12) JS Stack trace: @XPIProvider.jsm:4340:1 < XPI_loadBootstrapScope@XPIProvider.jsm:4340:7 < XPI_callBootstrapMethod@XPIProvider.jsm:4419:9 < AI_startInstall/<@XPIProvider.jsm:5902:11

In particular, at bootstrap.js line 50, column 12:

Code: Select all

 let {async, change} = makeWindowHelpers(window);

"SyntaxError: expected property name, got ','" means that JS lexical parser did not recognize "async" as a property.

This new behavior in Pale Moon 28.7 is most likely caused by the following changes (see also the release notes: "Landed a large JavaScript parser tune-up, which as a targeted goal brings our ES6 stringification fully in line with the ES2018 revision for classes, and implements rest/spread parameters for object literals").

[Moonchild]

async and await are reserved keywords, and more strictly enforced now because of the changes to destructuring patterns.
So yes, it's because of the change indicated. the release notes also warned about breaking changes because of behavioral changes in the parser.

[MonoS]

Error Console shows this error:

Code: Select all

Error loading bootstrap.js for lessChrome.HD@prospector.labs.mozilla: SyntaxError: expected property name, got ',' (resource://gre/modules/addons/XPIProvider.jsm -> jar:file:///D:/PaleMoonPortable28.7.0/User/Palemoon/Profiles/Default/extensions/lessChrome.HD@prospector.labs.mozilla.xpi!/bootstrap.js:50:12) JS Stack trace: @XPIProvider.jsm:4340:1 < XPI_loadBootstrapScope@XPIProvider.jsm:4340:7 < XPI_callBootstrapMethod@XPIProvider.jsm:4419:9 < AI_startInstall/<@XPIProvider.jsm:5902:11

In particular, at bootstrap.js line 50, column 12:

Code: Select all

 let {async, change} = makeWindowHelpers(window);

"SyntaxError: expected property name, got ','" means that JS lexical parser did not recognize "async" as a property.

This new behavior in Pale Moon 28.7 is most likely caused by the following changes (see also the release notes: "Landed a large JavaScript parser tune-up, which as a targeted goal brings our ES6 stringification fully in line with the ES2018 revision for classes, and implements rest/spread parameters for object literals").

Thanks for the information, next time i'll take a look at the console .

[Goodydino]

If you do not like the normal parts of the interface to be visible, why not just use full-screen mode?

[MonoS]

If you do not like the normal parts of the interface to be visible, why not just use full-screen mode?

Because i have an ultrawide monitor and i do often multitask, having all in fullscreen will be a waste of screen real estate for me (it has happened in the past that i had pale moon, and RDP session and two chat program opened and used at the same time)

[Moonchild]

If you have that much screen real estate, I don't understand why you want to hide the UI; it'd be something important for small screens.

[MonoS]

If you have that much screen real estate, I don't understand why you want to hide the UI; it'd be something important for small screens.

The UI occupies vertical space, which is less than the horizontal, without this plugin the UI occupies about 12% of the vertical space compared to the 5%.