It's fine. This is just stupidity dressed as on-purpose bad UX. Yes, I consider whoever makes that decision ("Yeah, we should totally make it not do what the us

It's fine. This is just stupidity dressed as on-purpose bad UX. Yes, I consider whoever makes that decision ("Yeah, we should totally make it not do what the user wanted it to do!") utterly stupid, and a sad presence in the gene pool. There are file management apps, graphic design apps (figma), etc., that use both the clipboard and the <c-c> / <c-p> binds to work. Neither blocking the bind of <c-c> events, nor of the clipboard are going to happen. We all have different needs and different pains. Sure, around here, we care about user experience, privacy, performance and optimizations, but let's not forget that we're in a bubble. The regular less-powered users are just as important as us, and their needs may outweight ours. I wish there was truly open browser that was not crap, there isn't. I wish better privacy controls were available out-of-the box. I wish there could be a feature matrix backed by a default profile so that I can only give access to the clipboard / other APIs manually, but with a prompt on access attempt. I wish so much. If I don't like my job runner, or my window manager, or even my password manager, I can go ahead and try with at least moderate success to make my own. Browsers are made by large groups of competent (most of them) polyglots, that work countless hours, willing to drill through the shit that has accumulated over the years into what we call the web. I don't have what's required to make my own browser.