Viewing last 25 versions of post by stsyn in topic Report site bugs here

"[@Marker":](/meta/report-site-bugs-here/post/4356639#post_4356639
)  
Probably it leads to two general ways of workarounds:
 
1) While CSP-extensions isare generally unstable on Chrome, it's relatively easy to make scripts work with CSP;
 
2) From what I heard, there is no big deal in configuring CSP bypassing on Firefox, but userscripts extensions cannot do it by themselves. If code from 1) is not strictly tied to Tampermonkey/Chrome features, you may probably use the same code in scripts?

"@Marker":/meta/report-site-bugs-here/post/4356639#post_4356639
Probably it leads to two general ways of workarounds:
1) Whilen CSP-extensions is generally unstable on Chrome, it's relatively easy to make scripts work with CSP;
2) From what I heard, there is no big deal in configuring CSP bypassing on Firefox, but userscripts extensions cannot do it by themselves. If code from 1) is not strictly tied to Tampermonkey/Chrome features, you may probably use the same code in scripts?

"@Marker":/meta/report-site-bugs-here/post/4356639#post_4356639
Probably it leads to two general ways of workarounds:
1) When CSP-extensions is generally unstable on Chrome, it's relatively easy to make scripts work with CSP;
2) From what I heard, there is no big deal in configuring CSP bypassing on Firefox, but userscripts extensions cannot do it by themselves. If code from 1) is not strictly tied to Tampermonkey/Chrome features, you may probably use the same code in scripts?