Justin Wasack

@MPThLee Thank you for the suggestion. Are you willing to make a PR for this or do you have an example implementation I could look at?

@MPThLee thanks for the links. If anyone wants to help out with this issue, please let me know. Time is limited for me, and this would be important to implement.

I took a look at the links above, I am not sure it is even possible to implement `unsafeWindow` in the way they are done above. Safari does not have...

@ACTCD I agree with what you are saying here. I am unaware of a method of exposing the page context's window object to the content script context and thus allowing...

@ACTCD I agree with what you've written, especially: > In fact, I don't think properly designed scripts should use unsafeWindow I very rarely use userscripts written by other individuals, partially...

@fyy99 > Script managers should be generic, leaving the security settings to the user to choose, rather than simply desupporting a feature. It sounds like you did not read through...

@DBa2016 My suggestions would be to use the following metadata in your userscripts: ```js @inject-into page @run-at document-start ``` This will ensure your script run in the `page` context and...

@DBa2016 You absolutely need to inject into the `page` context as well? If you can avoid that, then obviously you can use all the `GM` apis you'd like. If you...

Yeah, it's not exactly pretty. On the flip side, using the method does raise security concerns so it should probably be avoided.

> some scripts that were closed (greyed out) were all opened. Can you give more detail about this? What does greyed out / closed mean in this context?