Being able to take an image from the web page and place it on the clipboard is not 'the website having access to my clipboard'. It's the _browser_ having access.

Going in the reverse direction, placing data from the clipboard into the web page, is more tricky, but Firefox already does a good job of blocking clipboard accesses unless they're the direct result of user action (keyboard shortcut or button press).

The question is whether the website should be able to push images to the clipboard by itself, which it shouldn't. Firefox already supports doing what you're talking about.

I don't like the way clipboard access is handled in browsers either, but the fact remains that if I'm using an in-browser image editor, select a part of the image and press CTRL+C, I want that portion of the image in my clipboard. How it gets there is an implementation detail that the average user doesn't and, if it doesn't affect security/privacy, shouldn't have to care about. And since it's write-only, there's no security/privacy concern.

Having a feature that breaks user's security is not a feature.

Anyways, this is far more time than I'm willing to spend talking to someone who thinks their PoV is the only correct one (I just now recognize your username from a few other threads under this post). Cheeers!

You can be right, but the market has a final word.

Today, many people enjoy using advanced apps, that can be "installed" and "uninstalled" in one second (by opening and closing a website), without leaving any track (mess) in your computer.

Why shouldn’t I be allowed to put a bookmark as an icon? That’s essentially what a PWA is anyways. A fancy bookmark that behaves like a native app. Why are you the arbitrator of what I can do?

What happened to giving users control?

What if "literally what I want" is to edit a photo without installing any software?