Bug 23605

Summary: Mageia Welcome app screens are not displayed correctly when using the Tab key to move between buttons
Product: Mageia Reporter: Andrew Brewster <ab.kde>
Component: RPM PackagesAssignee: Mageia tools maintainers <mageiatools>
Status: RESOLVED WONTFIX QA Contact:
Severity: normal    
Priority: Normal CC: marja11, napcok, python, yvesbrungard
Version: 6   
Target Milestone: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Source RPM: mageiawelcome CVE:
Status comment:
Attachments: Transition from screen 1 to 2
Blank screen using hyperlink after using tab key
Video of steps to reproduce

Description Andrew Brewster 2018-09-24 23:35:10 CEST
Theme name: Adwaita
Kernel version = 4.14.70-desktop-2.mga6
Distribution=Mageia release 6 (Official) for x86_64
CPU=AMD FX-8320E Eight-Core Processor

How reproducible

Every time

Steps to reproduce

Checking usability/accessibility of app with Tab key and ability to move between buttons, I pressed the tab key after opening. After 26 presses, the second screen is only partially shown, after moving from the 'Join Us' button, to the 'Documentation' button and the first screen hyperlink remains selected.
This happens with the transitions from screens 2 to 3 ('Documentation' button to 'Mageia Control Centre' button), and 3 to 4 ('Check system updates' button to 'read more (wiki)' button too), and at each transition the first screen hyperlink remains selected.
The last transition for 4 to 1 doesn't happen from the 'Terminal' button until the focus is on the first button (Forums) in the column labelled 'Support'
The same things happen reversing the sequence using using Ctrl + Tab

Plus 

After using the tab button to cycle through the app buttons, if you click on the hyperlink to the second screen for Mageia Control Centre, the hyperlink underline is correctly updated, but the screen is blank, and also for  screens 3, and 4, or
After using th etab button to cycle through a couple of screens, using the hyperlinsk only moves half a screen one way or the other, giving the same effect as using the tab key.

Plus

I discovered while doing this that the blue focus blur around the buttons is difficult to see (using this theme?) aginst the blue application background colour, which made it hard to figure out what is going on.
Comment 1 Andrew Brewster 2018-09-24 23:43:13 CEST
Created attachment 10386 [details]
Transition from screen 1 to 2
Comment 2 Andrew Brewster 2018-09-24 23:43:59 CEST
Created attachment 10387 [details]
Blank screen using hyperlink after using tab key
Comment 3 Andrew Brewster 2018-09-24 23:53:00 CEST
Created attachment 10388 [details]
Video of steps to reproduce

First few seconds is tabbing through keys, watch very carefully for focus blur, second part is using hyperlinks afterwards and getting blank screens. There is no sound.
Marja Van Waes 2018-09-25 07:55:36 CEST

CC: (none) => marja11, napcok, python
Source RPM: drakconf-13.16-1.mga6 => mageiawelcome
Assignee: bugsquad => mageiatools

Comment 4 papoteur 2018-09-26 15:15:36 CEST
Thanks Andrew for reporting.
This is bad, indeed.
I wonder from when this is so bad.

Papoteur

CC: (none) => yves.brungard_mageia

Comment 5 Andrew Brewster 2018-09-26 21:10:24 CEST
I don't know anything about how the app is created or how it works, but I'm willing to bet, from the first edition!
I've referenced 'screens' for want of better application specific jargon, but I don't think there's any kind of self-aware 'container' that has such boundaries within it.
Its analagous to a single web page app with in-page links: you can tab through all the links and the page 'viewport' or 'screen' will only change, by a whole 'viewport' height (or in this case, width), when the next link is within a new 'viewport'. The hyperlinks actually take you to the top (or in this case the side) of the next 'viewport'.
As for the mixed behaviours that depend on where and when you use tabs between buttons or hyperlinks, it appears that the hyperlinks take you 1 full 'viewport' either way, regardless of whether the viewport contents are reasonable or not, because they have no references for what the boundaries should be.
As for blank screens, well, that's just a mystery.
Comment 6 papoteur 2018-12-28 19:18:50 CET
The application is now rewritten in QML techno. The above remarks are no more valid against it.

Resolution: (none) => WONTFIX
Status: NEW => RESOLVED

Comment 7 Andrew Brewster 2019-01-02 23:10:54 CET
Great, thanks for your efforts; I look forward to using it in Mageia 7