This was one of those things that frustrated me so much that we ended building this natively into Orion browser (Tools menu -> Allow Copy & Paste). [1] One of the joys of building your own browser. [1] https://kagi.com/orion
Why allow pages to disable copy & paste at all?
It's kind of a misfeature, but the non-evil idea was probably to provide hooks for customizing copy and paste (or other standard command functionality) in beneficial ways, for example seamlessly copying and pasting custom data formats between web apps, or between web and desktop apps.
It is a law of the web that any potentially beneficial browser feature will immediately be (mis)used in an abusive, user-hostile manner.
This was one of those things that frustrated me so much that we ended building this natively into Orion browser (Tools menu -> Allow Copy & Paste). [1] One of the joys of building your own browser. [1] https://kagi.com/orion
Why allow pages to disable copy & paste at all?
It's not about disabling it, it's about intercepting it by telling the browser that you're directly handling paste events and then doing nothing. The extensions just forces the browser default handler.
Then the vast majority of users are wrong. The correct answer is for it be the browser's find. Maybe apps could bind their find/search to ctrl-s since it is incorrect for browsers to bind this to save-page anyway.
The browser's control-f won't find you text draw onto a canvas element so those users really aren't wrong ...
It's also trivial to use Ctrl+F on such pages if you so choose by clicking into the URL bar and then doing the keyboard combo. (Or just make two clicks in the browser menu.)
> In order to provide the smoothest experience as possible, the extension needs to know when you change active tabs. In order for the extension to know about that event, it needs the tabs permission, which Chrome describes as "can read and change all your data on websites you visit." That description is very scary, and is certainly not what this extension is doing. Being an open-sourced project, you can always read a…
It is also not at all clear to me why it "needs to know when you change active tabs".
I just read through the 65LOC source, and it's because it swaps out an active or inactive extension icon based on your active tab.
I get around that by downloading the extension source and then using Chrome extension developer mode to “load unpacked extension”. Then I’m confident the extension won’t change on me. (But for this extension I don’t give it all site permissions anyway. I just enable on site by site basis)
That's terrible for security, but great for convenience :)
It is also not at all clear to me why it "needs to know when you change active tabs".
I just read through the 65LOC source, and it's because it swaps out an active or inactive extension icon based on your active tab. https://github.com/aaronraimist/DontFuckWithPaste/blob/8cb68...
Huh. That seems not super important to me. Presumably he could make a option/version where the icon didn't change?
Agreed. It doesn't offend me personally, but it's considered NSFW language in most workplaces. I would never name a project like that
> NSFW language in most workplaces It would have been fine literally everywhere I've worked. I'm not saying there aren't places where this can be an issue. Partly this seems to depend on the region – in the US, in particular, it seems to be a big no-no, which I find odd considering how fucking often fuck is in fucking American media – the fuck is up with that? But outside of that? It seems to be mostly a non-issue.
Probably because the US does have a pretty wide diversity, particularly when it comes to religion. In some areas you'll find a lot of Mormons (who are greatly offended by "fuck"), and in some Christians (where some denonimations don't even like the word "crap" let alone "fuck"), in some Catholics who generally don't seem to care (I've heard some Catholic priests let loose some pretty blue streaks lol), and all kinds of others. Then there are people who aren't offended, but don't want to talk that way in front of their kids and don't allow their kids to talk that way. In a workplace in the US (where you can't discriminate based on religion as it's a protected class), it's a very bad idea to use that kind of language unless you know everyone around and you know that they don't mind. Even then, be aware of who might be nearby enough to hear. Getting an HR complaint against you for dropping an f-bomb is embarrasing and not very fun.