Open Wei-Winter opened 2 weeks ago
It appears to be similar to #656
It is somewhat similar 🤔 but still a bit different from the Android Firefox browser. I tried it on an Android device, and installing the script didn't have any response. Attempting to directly copy and add the script can indeed run. However, when using the iOS Orion browser to install the script, there is a prompt for "confirm installation," but there is no response after clicking. Additionally, I tried to copy and add the script using the Orion browser, but it couldn't run. Orion is a browser on the Apple platform, should you correct the tags?
Mobile platforms have slightly different and limited API support which results in incompatibility. The "android" tag was meant for Firefox for Android.
FireMonkey uses a Firefox exclusive API and unless Orion is based on Firefox code, it wont work on it.
Do the userscripts function when using FireMonkey on Orion?
I am not a developer, so I may not be certain about some questions. Orion scripts do not work with FireMonkey, but they are effective with Violentmonkey. Do they use the same API?
Do they use the same API?
FireMonkey was the only userscript manager that used the dedicated userScripts
API in MV2. Tampermonkey recently added the option to use the above on Firefox but it is not the default behaviour.
If Orion does support the userScripts
API, then FireMonkey wont work on in MV2.
The new MV3 format (introduced by Google a couple of years ago) aims to harmonise the behaviour between different platforms. The userscript & userstyle support in MV3 is still work in progress.
This is their API support documentation https://kagi.com/orion/WebExtensions-API-Support.html However, as far as I know, the Orion browser documentation seems to mention that it is not subject to MV3 restrictions.
They appear to have partial support but they don't support onBeforeScript which would make it incompatible with most userscripts.
I have installed FireMonkey on iOS Orion browser, you may not have heard of this browser, but it does achieve compatibility with a few extension APIs. The current issue is that the UI can be displayed normally, but scripts cannot be installed directly from script websites. New JavaScript files can be saved correctly. However, the saved scripts cannot be executed.