| Bug ID |
11714
|
| Summary |
Tab navigation/Enter is not working in UAT dialogs
|
| Product |
Wireshark
|
| Version |
Git
|
| Hardware |
All
|
| OS |
All
|
| Status |
UNCONFIRMED
|
| Severity |
Major
|
| Priority |
Low
|
| Component |
Qt UI
|
| Assignee |
[email protected]
|
| Reporter |
[email protected]
|
Build Information:
v2.1.0rc0-568-g974a9e3 from master, Qt 5.5.1 on Arch Linux x86_64.
--
Now that the UAT dialog does not crash anymore, the other UX bugs mentioned in
https://bugs.wireshark.org/bugzilla/show_bug.cgi?id=11031#c6 are still present:
The UAT dialog implementation in Qt has some changes/regressions from Gtk:
- Using Tab/Enter to switch between fields does not work. (Enter always
focuses the first column when not editing and does nothing when already
editing)
Expected behavior: Enter stops editing, tab moves to the next field
- Empty values can be entered which will then be accepted (Try "Add" in the
SSL keys dialog without modifying fields).
Expected behavior: empty values should be discarded. What about missing
values? Should those rows also be discarded?
The comments in uat_dialog.cpp suggest to make a UatModel. Maybe that could be
done to avoid re-implementing the focus functionality in
https://doc.qt.io/qt-5/focus.html. On the short term, we could try intercepting
Tab and Shift+Tab though.
You are receiving this mail because:
- You are watching all bug changes.