Is "clipboard" permission replaced by "clipboard-read" and "clipboard-write"?

[saschanaz]

The Permissions spec still mentions "clipboard" but it seems it's removed from the Clipboard spec. Should the Permissons spec be updated to use the new permission names?

[marcoscaceres]

I think this is w3c/permissions#155 ?

[saschanaz]

@marcoscaceres Kinda, but that seems outdated. It still uses "clipboard" instead of "clipboard-read" and "clipboard-write", which doesn't match this spec.

Edit: aa1f8ac added those to the spec.

[nickalbrecht]

Any traction on this one?

[saschanaz]

Can somebody confirm this please so that I can open a PR there?

[marcoscaceres]

A PR would be good. I know what the implementation status of any of this is, however. @saschanaz, would you mind investigating a little bit?

[saschanaz]

Firefox Nightly: No support
Chrome (as of 80 stable): Support for clipboard-read and clipboard-write, while no clipboard.
Epiphany (WebKit): No navigator.permissions support at all

[marcoscaceres]

Much sadness... let me see if I can find who owns clipboard on the Gecko side.

[saschanaz]

Related Firefox bug: https://bugzilla.mozilla.org/show_bug.cgi?id=1560373

[marcoscaceres]

Good find! thank you!

[saschanaz]

Does that mean there is no owner? Should I wait until someone takes it?

[annevk]

Yeah, it's not clear to me how much buy-in the current setup has here so I'd definitely hold off a bit for now.

[rniwa]

FWIW, Safari will likely never support non-gesture based copy & paste permission (as in we'd likely always require a new gesture for each copy & paste). As such, we don't see this permission ever being implemented / supported in Safari.

[wandyezj]

What is really annoying is that browsers have gone ahead with their own implementation for a critical feature. This ends up forcing developers to use commands to read and write to the clipboard to work around this nonsense.

This seems like a people problem and not a technical problem.