FireMonkey 3.0 Beta for testing

[erosman]

Here is the latest beta for testing.
Please read the Changelog & Help as there are a few breaking changes.
Feedbacks are welcomed.

See: Beta Installation Guide

firemonkey.3.0-beta2.zip

firemonkey.3.0-beta3.zip

• Beta 3 added Diff Viewer, and uses the slimmer ESLint 10.0.0-beta.0 (until v10 comes out)
• Fixed Firemonkey 3.0 beta-2: "Error: An unexpected apiScript error occurred" for GM.getValue() #30

firemonkey.3.0-beta4.zip

• Added "GM cookie" support

firemonkey.3.0-beta5.zip

• ESLint 10.0.0
• Fixed shadow DOM userCSS insertion (Firefox 144) (Apply CSS to Shadow DOM #37)

[Sznymo]

Any ETA on the 3.0 stable release? Looking forward to it!

[CormacZ]

For some reason the script I updated to work with Firemonkey 3.0 suddenly gone, they in the list appear to show working in the website I set to. But the script does not run nether i can edit it anymore. the v2.0 one still working and editable.

[erosman]

Any ETA on the 3.0 stable release? Looking forward to it!

More feedbacks and beta testing is needed to make sure it is running smoothly.

For some reason the script I updated to work with Firemonkey 3.0 suddenly gone, they in the list appear to show working in the website I set to. But the script does not run nether i can edit it anymore. the v2.0 one still working and editable.

Does the Developer Tools (F12) -> Console show any errors on the Options page?

[CormacZ]

Does the Developer Tools (F12) -> Console show any errors on the Options page?

Oh yeah it does, here:
1st script

Uncaught TypeError: can't access property 0, (intermediate value)[id].antifeatures is undefined
    showScript moz-extension://88e6c90e-1a78-4ce4-80df-441045f66c41/content/options.js:596
    addScript moz-extension://88e6c90e-1a78-4ce4-80df-441045f66c41/content/options.js:539
[options.js:596:5](moz-extension://88e6c90e-1a78-4ce4-80df-441045f66c41/content/options.js)
    showScript moz-extension://88e6c90e-1a78-4ce4-80df-441045f66c41/content/options.js:596
    addScript moz-extension://88e6c90e-1a78-4ce4-80df-441045f66c41/content/options.js:539

2nd script

Uncaught TypeError: can't access property 0, (intermediate value)[id].antifeatures is undefined
    showScript moz-extension://88e6c90e-1a78-4ce4-80df-441045f66c41/content/options.js:596
    addScript moz-extension://88e6c90e-1a78-4ce4-80df-441045f66c41/content/options.js:539
2 options.js:596:5
    showScript moz-extension://88e6c90e-1a78-4ce4-80df-441045f66c41/content/options.js:596
    addScript moz-extension://88e6c90e-1a78-4ce4-80df-441045f66c41/content/options.js:539

[erosman]

@CormacZ (intermediate value)[id].antifeatures line belongs to FM2.74 (and older). It was removed in FM3.0.

firemonkey/src/content/options.js

Line 596 in da8e9a1

pref[id].antifeatures[0] && this.legend.classList.add('antifeature');

Are you using a database saved in FM3.0 on FM2.74?

[CormacZ]

Are you using a database saved in FM3.0 on FM2.74?

Probably, I mean I only update the extension but never really do any backup on the script, some of them work. Do I need to use fresh instance instead?

[erosman]

Probably, I mean I only update the extension but never really do any backup on the script, some of them work. Do I need to use fresh instance instead?

When you install FM3.0, it automatically saves a back-up e.g. FireMonkey_2026-01-09.json.
If you go back to FM2.74, you can import this backup.

Another method is to export all scripts in FM3.0 (or even in FM2.74) and then re-import them in FM2.74. Only individual scripts will be imported (without their storage).

When importing, you can select all scripts together (no need to import them one by one).

[CormacZ]

Aaah, alright thanks. It works now.

[CrendKing]

I notice that ESLint reports Irregular whitespace not allowed. (no-irregular-whitespace) to the @match when there is */ in it. I'm not completely sure if something like *://www.example.com/*/foobar is valid (which ESLint marks with red), but I'm sure https://*/* should be valid, as it is shown as example in your Help page and example patterns in Match patterns, but it is still marked.

It seems only an editor issue. Even *://www.example.com/*/foobar would perfectly inject into a page with https://www.example.com/upload/foobar.

Steps to reproduce:

1. Paste this into editor

/*
==UserScript==
@name           Script
@match          https://*​/*
==/UserScript==
*/

(function () {
    
})()

2. Notice the red mark between the first * and following /.