https://bugs.kde.org/show_bug.cgi?id=470211
`{third: "Beedell", first: "Roke"}`{.JSON5}
<4wy78...@rokejulianlockhart.addy.io> changed:
What|Removed |Added
CC|
https://bugs.kde.org/show_bug.cgi?id=470211
Nate Graham changed:
What|Removed |Added
Latest Commit|https://invent.kde.org/plas |https://invent.kde.org/plas
https://bugs.kde.org/show_bug.cgi?id=470211
fanzhuyi...@gmail.com changed:
What|Removed |Added
Resolution|--- |FIXED
Version Fixed In|
https://bugs.kde.org/show_bug.cgi?id=470211
Bug Janitor Service changed:
What|Removed |Added
Status|CONFIRMED |ASSIGNED
--- Comment #5 from Bug Janitor
https://bugs.kde.org/show_bug.cgi?id=470211
--- Comment #4 from fanzhuyi...@gmail.com ---
IMO from a UX perspective it might be reasonable to always make double click
select the current item and confirm (with just the current item selected), even
when multi-selection is allowed.
--
You are
https://bugs.kde.org/show_bug.cgi?id=470211
fanzhuyi...@gmail.com changed:
What|Removed |Added
CC||fanzhuyi...@gmail.com
--
You are
https://bugs.kde.org/show_bug.cgi?id=470211
--- Comment #3 from Nate Graham ---
For the screen chooser dialog, multi-selection can be allowed, and I think it
might be awkward to have the buttons react differently depending on the
implementation detail of whether the app allows multi-selection.
https://bugs.kde.org/show_bug.cgi?id=470211
--- Comment #2 from iodream...@gmail.com ---
Alternatively, the buttons could behave like buttons requiring only one click.
But i'm not sure if this wouldn't increase accidental misclicks and lower
security. And also how easy single click would be to
https://bugs.kde.org/show_bug.cgi?id=470211
Nate Graham changed:
What|Removed |Added
Keywords||junior-jobs
--- Comment #1 from Nate Graham ---
https://bugs.kde.org/show_bug.cgi?id=470211
Nate Graham changed:
What|Removed |Added
Ever confirmed|0 |1
Status|REPORTED
10 matches
Mail list logo
