Mailinglist Archive: opensuse-bugs (4661 mails)

< Previous Next >
[Bug 1045798] [Build 20170622] Next button has wrong shortcut on Network Settings page of KDE_Live
  • From: bugzilla_noreply@xxxxxxxxxx
  • Date: Mon, 26 Jun 2017 13:47:41 +0000
  • Message-id: <bug-1045798-21960-ZkfWytaYy4@http.bugzilla.suse.com/>
http://bugzilla.suse.com/show_bug.cgi?id=1045798
http://bugzilla.suse.com/show_bug.cgi?id=1045798#c2

Stefan Hundhammer <shundhammer@xxxxxxxx> changed:

What |Removed |Added
----------------------------------------------------------------------------
Status|NEW |RESOLVED
Resolution|--- |INVALID

--- Comment #2 from Stefan Hundhammer <shundhammer@xxxxxxxx> ---
There is no such thing as a "wrong shortcut" for those buttons. A button has a
shortcut, and it might change between wizard steps.

Your base assumption that those shortcuts have to be static is wrong. They are
not, and they are not meant to be.

Here is an explanation why not and how this works in YaST:

https://github.com/libyui/libyui/blob/master/src/YShortcutManager.h#L65

I suggested to your QA colleagues numerous times that we could introduce a much
more stable mechanism for openQA to activate YaST buttons: All buttons have a
unique widget ID ("next" in this case) that is much more suitable for that
purpose. We could add a mechanism to the YaST UI to easily send such a widget
ID to activate a widget (not only limited to buttons, but also setting the
keyboard focus to input fields and selection lists etc).

But if you prefer to do it the old-fashioned way by using keyboard shortcuts,
you'll just have to live with some of them changing between wizard steps.

Remember that the focus for the product is the user, not testing tools; we have
to give the user a chance to use the application reasonably well with only the
keyboard if using the mouse is not an option (mouse driver not working etc.).

--
You are receiving this mail because:
You are on the CC list for the bug.
< Previous Next >