You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Can't navigate down from the side widget "Close" within settings if the secondary side menu setting (see picture) is set to "Contextual".
First noticed in version v6.26 and still happening in v6.27. However, you can navigate down from Close if the secondary side menu is set to Menu or Options.
Only happens within settings. Not home page.
Only way to get to Settings button is to first scroll down to around Furniture in the middle column and the click over to the left.
Kodi Omega nightly
nVidia Shield
Expected Behavior
To be able to scroll down from the Close button.
Steps To Reproduce
Go to settings Skin settings
navigate to Menus and then Side menu >Minimise > Secondary.
Change setting to Contextual
Scroll left to "close" button
Click down on remote, can't do it
Screenshots and Additional Info
Checklist
I have made a separate issue for each bug that I am reporting.
I have searched the issues and this bug has not been reported.
I am using the most recent skin version.
I have confirmed that this bug does not occur in the default skin.
The text was updated successfully, but these errors were encountered:
Skin section
Widgets
Current Behavior
Can't navigate down from the side widget "Close" within settings if the secondary side menu setting (see picture) is set to "Contextual".
First noticed in version v6.26 and still happening in v6.27. However, you can navigate down from Close if the secondary side menu is set to Menu or Options.
Only happens within settings. Not home page.
Only way to get to Settings button is to first scroll down to around Furniture in the middle column and the click over to the left.
Kodi Omega nightly
nVidia Shield
Expected Behavior
To be able to scroll down from the Close button.
Steps To Reproduce
Screenshots and Additional Info
Checklist
The text was updated successfully, but these errors were encountered: