[dolphin] [Bug 441011] New: Strange wording on the bluetooth file sharing dialog; "Back" instead of Cancel et al
Rick Kerkhof
bugzilla_noreply at kde.org
Sun Aug 15 18:46:38 BST 2021
https://bugs.kde.org/show_bug.cgi?id=441011
Bug ID: 441011
Summary: Strange wording on the bluetooth file sharing dialog;
"Back" instead of Cancel et al
Product: dolphin
Version: unspecified
Platform: Fedora RPMs
OS: Linux
Status: REPORTED
Severity: normal
Priority: NOR
Component: general
Assignee: dolphin-bugs-null at kde.org
Reporter: rick at nanosector.nl
CC: kfm-devel at kde.org
Target Milestone: ---
Created attachment 140753
--> https://bugs.kde.org/attachment.cgi?id=140753&action=edit
The dialog in question
SUMMARY
The bluetooth file sharing dialog (right-click a file, Share -> Share via
Bluetooth) has strange wording on the dialog's actions. The bottom two options
are Run and Back, neither of which makes sense in this context.
Run does not make sense because what are you supposed to "run"? An action like
"Share with device" would make more sense here, as you are supposed to select a
device to share with in the context of this window.
Back does not make sense because the window is separate from the main Dolphin
context. I have assumed this is named the way it is because of mobile file
sharing being more common, but "Cancel" seems more appropriate in either
scenario.
STEPS TO REPRODUCE
1. Right-click a file
2. From the Share menu, select Share via Bluetooth
3. Observe the dialog wording
OBSERVED RESULT
The wording on the action buttons does not make sense in the context.
EXPECTED RESULT
The wording on the action buttons should make sense in the context.
SOFTWARE/OS VERSIONS
Operating System: Fedora 34
KDE Plasma Version: 5.22.4
KDE Frameworks Version: 5.83.0
Qt Version: 5.15.2
Kernel Version: 5.13.9-200.fc34.x86_64 (64-bit)
Graphics Platform: X11
Processors: 4 × Intel® Core™ i5-5200U CPU @ 2.20GHz
Memory: 15,4 GiB of RAM
Graphics Processor: Mesa Intel® HD Graphics 5500
ADDITIONAL INFORMATION
N/A
--
You are receiving this mail because:
You are on the CC list for the bug.
More information about the kfm-devel
mailing list