Qliksense layout container weird behavior when navigating inside using keyboard

[ol_dev]

Hi, 

First of all I'd like to say that the layout container is absolutely amazing, and it is now possible to stack two UI objects on each other as well as selectively hide one or another. It solves a lot of problems that we have had no solutions in the past. 

However, there seems to be a very strange behavior when navigating inside the container's UI Objects using keyboard. As we navigate inside the container's objects by pressing the 'Enter' button, the navigation always starts at the end of the container rather than the beginning. I've attached two screenshots to demonstrate this behavior, in which the first screenshot displays that the parent layout container is selected using keyboard, and the second screenshot shows what happens when 'Enter' key is pressed to navigate inside. The desired behavior should be that navigation begins on the first object(left object), but the actual behavior is that navigation begins on the last object(right object). 

Screenshot 1: The parent container is selected.

Screenshot 2: When 'Enter' is pressed, it defaults to the last object(right object). 

I wonder, is this a bug or intended? Is there a workaround for the problem? I understand that the layout container JS code is possible to modify in the extensions folder, in this case can someone show me where the code is that determines which UI object is selected inside the layout container when 'Enter' key is pressed? Thanks. 

[ol_dev]

Any comments? Or am I the only one experiencing the issue? 

[ol_dev]

It is been several days and why is there still no response from the Qlik dev team? I just want to confirm if this behavior is intended or it is a bug, and if it is a bug I may be able to edit the JS file for layout container to mitigate it. Is it so hard for someone to take a look at it? 

[ol_dev]

Hello, why is there still no response from Qlik dev team? 

[David_Friend]

@Sebastian_Linser any thoughts on this? Is this working as designed or possibly a bug?

[ol_dev]

@David_Friend @Sebastian_Linser 

It has been 3 weeks and still no update on the issue? I just want to know if Qlik dev team is aware of the issue, and whether it will be addressed anytime soon. And if not, can we roll our own fix? Thanks. 

[ol_dev]

The issue appears fixed in latest version Qliksense May 2025 for windows desktop/enterprise release, though strangely enough it was not documented anywhere.