Open Bug 1777197 Opened 2 years ago Updated 2 years ago

Collect UX feedback about showing the "Paste" button

Categories

(Core :: DOM: Copy & Paste and Drag & Drop, task)

task

Tracking

()

People

(Reporter: mbrodesser-Igalia, Unassigned)

References

(Blocks 1 open bug)

Details

To test, with current Nightly:

  1. Flip the pref "dom.events.asyncClipboard.readText" to true.
  2. Open https://jsfiddle.net/68hng59s/.
  3. Click the "X" button.

A "Paste" button should occur. Be aware of bug 1766803 though.

What's UX-people's view on this? See https://bugzilla.mozilla.org/show_bug.cgi?id=1578321#c8 for the rationale behind showing a "Paste" button. Be aware that Safari shows such a "Paste" button too.

See Also: → 1776829
See Also: → 1774163

Thanks for sharing this, my questions center around why we're showing a paste option on a button. A button is an action that a user wants to take, typically to go somewhere, so it seems like an unexpected behavior. Can you outline what the goals of the paste action are, as well as what type of feedback you're looking for from UX?

(In reply to Jane Wolf from comment #2)

Thanks for sharing this, my questions center around why we're showing a paste option on a button. A button is an action that a user wants to take, typically to go somewhere, so it seems like an unexpected behavior. Can you outline what the goals of the paste action are

The goal is to allow a website to ask the user for permission to paste their clipboard content to that website. That already requires user interaction (e.g. clicking somewhere on the website).
The new "Paste" button can be seen as a stripped down version of the right-click menu, which also includes a "Paste" menu item.

, as well as what type of feedback you're looking for from UX?

Just a sanity check, a different viewpoint than the software-developer's one; to ensure the UX is pleasing. Please see also bug 1774163 and comment there, in case you've thoughts about that topic.

I am ok with the paste option, but can we hide the paste option once the user has already allow the permission?

You need to log in before you can comment on or make changes to this bug.