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
Describe the bug:
Appearantly since 7.14 a decision has been made to remove the option to pin the menu on the left to keep it open all te time (instead of sliding in and out). This led to several complaints from my users. Some people just want to be able to set it the way the stack mgt menu is presented, fixed.
I was hoping I could change this behaviour by altering the theme (v7 vs v8) setting or the disable animations setting, but both actually seem to to nothing.
Steps to reproduce:
Logon to Kibana
open main menu
Find a way to pin it
Repeat until freaking out
Expected behavior:
find an icon somewhere which prevents the menu from sliding back and which positions the left border of the main area's next to it (usually when sliding, the menu covers part of the page. You don't want that with a permanently visible menu)
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
The text was updated successfully, but these errors were encountered:
tuckson
added
the
bug
Fixes for quality problems that affect the customer experience
label
Sep 9, 2021
This is not a bug as this capability was intentionally removed when the solution side nav was introduced. Ongoing feedback is being tracked here: #77072 so closing this issue as a duplicate.
Kibana version:
7.14 , 7.14.1
Describe the bug:
Appearantly since 7.14 a decision has been made to remove the option to pin the menu on the left to keep it open all te time (instead of sliding in and out). This led to several complaints from my users. Some people just want to be able to set it the way the stack mgt menu is presented, fixed.
I was hoping I could change this behaviour by altering the theme (v7 vs v8) setting or the disable animations setting, but both actually seem to to nothing.
Steps to reproduce:
Expected behavior:
Screenshots (if relevant):
Errors in browser console (if relevant):
Provide logs and/or server output (if relevant):
Any additional context:
The text was updated successfully, but these errors were encountered: