increased security in greasemonkey, gradual removal of __exposedProps__ as expected
as expected, newer releases of greasemonkey are gradually removing less secure functions in favor of more efficient functions considered to be "light weight" whatever that is suppose to mean, anyone working on new scripts or updating current ones need to be aware of these security changes to prevent scripts from failing in newer versions of firefox and greasemonkey as both are implementing these changes over time. source information in link below, including a sublink from github:
increased security in greasemonkey, gradual removal of __exposedProps__ as expected
as expected, newer releases of greasemonkey are gradually removing less secure functions in favor of more efficient functions considered to be "light weight" whatever that is suppose to mean, anyone working on new scripts or updating current ones need to be aware of these security changes to prevent scripts from failing in newer versions of firefox and greasemonkey as both are implementing these changes over time.
source information in link below, including a sublink from github:
Main: https://github.com/greasemonkey/greasemonkey/issues/2033
Sub: http://codeverge.com/mozilla.dev.b2g/notice-do-not-add-new-instances-of-exposedpro/1992161
whether or not __exposedProps__ is ever completely removed is unclear from either greasemonkey devs or firefox devs as of yet.