View Issue Details
ID | Project | Category | View Status | Date Submitted | Last Update |
---|---|---|---|---|---|
0008494 | Taler | wallet (WebExtension) | public | 2024-02-22 22:45 | 2024-04-15 21:32 |
Reporter | Florian Dold | Assigned To | sebasjm | ||
Priority | normal | Severity | minor | Reproducibility | have not tried |
Status | closed | Resolution | fixed | ||
Target Version | 0.10 | Fixed in Version | 0.10 | ||
Summary | 0008494: improve usability of QR code scanning page | ||||
Description | When testing with a user, they got very confused by the dialog, and did not know that "open" would do something with the URL after opening it. They also tried to "read QR from file", expecting it would somehow receive the payment. Possible approaches: * only show the "read QR from file" in dev mode * when a URI is scanned/pasted, the "open" button could contain the name of the contextual action ("open invoice", "open payment link") or something like that | ||||
Tags | No tags attached. | ||||
|
I think if a QR code is successfully scanned with a taler://-URI, we should auto-open it, not ask for the user to explicitly press "Open". When a user enters a QR code by hand, we could put the "OPEN" button on the right of the text entry bar and maybe label it "confirm" or "enter". And yes, remove the "open from file" except in dev mode, that's too unusual. |
|
86e02c6ec |
Date Modified | Username | Field | Change |
---|---|---|---|
2024-02-22 22:45 | Florian Dold | New Issue | |
2024-02-22 22:45 | Florian Dold | Status | new => assigned |
2024-02-22 22:45 | Florian Dold | Assigned To | => Florian Dold |
2024-02-27 13:18 | Florian Dold | Assigned To | Florian Dold => sebasjm |
2024-03-05 23:22 | Christian Grothoff | Note Added: 0021704 | |
2024-04-10 00:55 | sebasjm | Status | assigned => resolved |
2024-04-10 00:55 | sebasjm | Resolution | open => fixed |
2024-04-10 00:55 | sebasjm | Note Added: 0022187 | |
2024-04-12 01:50 | Christian Grothoff | Fixed in Version | => 0.10 |
2024-04-15 21:32 | Christian Grothoff | Status | resolved => closed |