Live data from Hacker News

Don't fuck with paste

github.com

61–70 of 397 posts

Re: Don't fuck with paste

#61

How about an extension that STOPS websites from NOT letting me right-click. When a site forceS me to go through the stupid Chrome menu to laboriously drill down and find Developer Tools manually I want to throw it out the window.

There’s a stackoverflow question with some bookmarklets.

https://stackoverflow.com/questions/21335136/how-to-re-enabl...

Re: Don't fuck with paste

#62
post #5

Right up there with hijacking Ctrl-F.

There's a lot of keyboard shortcuts that mean one thing in the browser but something totally different in another application. Now that it is common for many of these other applications to now be a web app, these keyboard short cuts are possible to start colliding. Take GoogDocs as an example. Do you want the browser's find or the app's find if you hit ctrl-f in a Doc/Sheet/etc? The vast majority of the users want th…

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.

Re: Don't fuck with paste

#63

Earlier quoted context omitted.

isn't ctrl-g common for "find next" with shift-ctrl-g "find previous"? maybe i live too much in my IDE/text editors?

Almost certainly, but It's one of of these "I can't believe I never knew this, it's so obvious!" things.

In that case, I'd highly recommend browsing through the drop down menus for any of your apps. It is very common* for the keyboard shortcut to be listed, and very frustrating when it is not. This is my primary source for finding these shortcuts for a new app.

* maybe it's a Mac thing???

Re: Don't fuck with paste

#64

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

Brave has a "force paste" that I use now instead of Chrome and the linked plugin. I assume the motivation was the same. (What a*hole thinks blocking paste is reasonable??)

Good on you for solving this too. It's a nonsense bit of functionality.

Re: Don't fuck with paste

#65

> 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".

You need to detect and stop sound. You swap out active memory.

Re: Don't fuck with paste

#66

Thanks for this! Also related, Who t.f. thought that * Ctrl-V should be "paste with format" * Meta-Shift-Whatever-Ctrl-V should be "paste without format" I've never EVER had the need to copy some text and paste it with a different font face, color and ffs background color ... Who is the genius UX expert that decided on this abhorrent behavior?

It’s beyond aggravating. I use a clipboard manager (PasteBot on macOS) set to paste plain text by default. I can pop open the history and do command+enter to paste the rich text version.

Re: Don't fuck with paste

#67

Earlier quoted context omitted.

There's a lot of keyboard shortcuts that mean one thing in the browser but something totally different in another application. Now that it is common for many of these other applications to now be a web app, these keyboard short cuts are possible to start colliding. Take GoogDocs as an example. Do you want the browser's find or the app's find if you hit ctrl-f in a Doc/Sheet/etc? The vast majority of the users want th…

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.

why is all of the sudden ctrl-s wrong by the browser?? you make no sense here. you've never needed to save a web page? i guess i'm showing my age, while i don't use it daily, it has been a valuable feature for many reasons before.

Edit: >Then the vast majority of users are wrong.

I strongly disagree, and people unwilling to be flexible ruins the experience as those people tend to be the minority

Re: Don't fuck with paste

#68

Earlier quoted context omitted.

isn't ctrl-g common for "find next" with shift-ctrl-g "find previous"? maybe i live too much in my IDE/text editors?

On macOS cmd+g is a standard shortcut most apps implement.

yeah, i substituted to ctrl from my normal cmd to not confuse people

Re: Don't fuck with paste

#69
post #5

Right up there with hijacking Ctrl-F.

There are semi-legitimate cases where this is warranted. For instance when looking at a Notion database, standard Ctrl-F is almost useless, and document search needs to go through the notion API to return results, sometimes even related to the entries that are displayed on screen.

I say "semi-legitimate" because I actually wish they'd map to a different shortcut, but can see the case for user wanted the remapping.

This of course stems from earlier decisions to have that document handling style in the first place. IMHO it becomes a complex debate when on line between an online application and a webpage.

Re: Don't fuck with paste

#70

Earlier quoted context omitted.

There's a lot of keyboard shortcuts that mean one thing in the browser but something totally different in another application. Now that it is common for many of these other applications to now be a web app, these keyboard short cuts are possible to start colliding. Take GoogDocs as an example. Do you want the browser's find or the app's find if you hit ctrl-f in a Doc/Sheet/etc? The vast majority of the users want th…

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 ...
Post reply on HN