We will soon add native support for userstyles/userscripts
Violentmonkey do not work properly
Vlad Hello, is this still in development?
korboybeats yes expected to hit with v.125
- Edited
Hi there, I'm new to Orion, thanks you guys in advance.
Steps to reproduce:
I've imported all the scripts from Chrome, and tried to reinstall some scripts.
On any sites there are scripts that are expected to be enabled on, it does show an enabled icon, however nothing changes on the sites at all.
Twitter as an example:
There some scripts for twitter, all of them shows enabled on the site however my Trends & other annoying twitter features are still there.
Expected behavior:
Scripts run normally.
Orion, OS version; hardware type:
Latest Orion on MacOS Sonota.
Image/Video:
<Copy/paste or drag and drop to upload images or videos (up to 20MB)>
Please note that Violentmonkey is now supporting Orion, although not 100% ready.
(Since last CI build released on Dec 1, 2023)
More than half of the scripts shall be able to run without issue.
cyfung1031 Thanks for reporting and sharing detailed steps to reproduce the same. We found that, we had an issue related to injections on youtube pages fo some reason. But now fixed that, so should be working fine in next release
- Edited
cyfung1031 Can confirm. The version with this change is now in the Beta version in the Chrome Web Store. https://chrome.google.com/webstore/detail/violentmonkey-beta/opokoaglpekkimldnlggpoagmjegichg
jp06 With the latest version of Orion and Violentmonkey BETA, the userscripts can be used without issue.
cyfung1031 When will it change to stable?
Note: If the script use setInterval / setTimeout to perform the endless loop checking (common in userscript design),
it might break the page rendering of Orion. See https://orionfeedback.org/d/6906-performance-defect-on-setinterval-and-settimeout/
Vlad The stable version (2.17.0) is now published to the store.
cyfung1031 So we can change this to done for Violent money at least? Did anyone else confirm?
- Edited
Vlad The topic title is for both TamperMonkey and Violentmonkey. I only solved the issues for Violentmonkey
TamperMonkey is closed-source and it seems difficult to find the the root cause without the participation from its owner. I don't think he would be interested in this beta ("experimental") browser.