You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
After ~4 hours of trying to understand why my script started throwing errors in the past couple of days I finally discovered that the problem lied with the new Greasemonkey version and beta as well; The addon is ignoring the @noframes rule.
I don't know yet if this was by design or if it was overlooked and I don't see it mentioned in the changelog, but all scripts will now run in iframes despite having @noframes declared.
Sample script:
// ==UserScript==// @name Test// @namespace Test// @version 1// @run-at document-start// @match https://www.youtube.com/*// @grant none// @noframes// ==/UserScript==if(self===top){console.info('I am not an iframe');}elseif(self!==top){console.info('I am an iframe');}
This fix is now included in version 3.1beta1. Please browse to Greasemonkey's AMO page and open "Development Channel" near the bottom to install the beta version. Can you confirm the fix? Thank you.
After ~4 hours of trying to understand why my script started throwing errors in the past couple of days I finally discovered that the problem lied with the new Greasemonkey version and beta as well; The addon is ignoring the
@noframes
rule.I don't know yet if this was by design or if it was overlooked and I don't see it mentioned in the changelog, but all scripts will now run in iframes despite having
@noframes
declared.Sample script:
Open https://www.youtube.com/watch?v=8pRJn77UeOM, for example, and observe the console.
The 3 iframe related strings show that the script is running inside iframes.
The text was updated successfully, but these errors were encountered: