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
When I have closed or opened the sidebar menu, I would expect it to keep that state when I reload the page or go to another page. Currently, AdminLTE does not store the state anywhere.
Due to this being a template, there is a lack of options on where to store this state and the one that makes sense is the browser. If we store it in the browser then we have to decide what storage to use, local or session. I would expect this state to be there the next time I open the site, so it makes sense to me to store it in the local storage as the session storage would be gone the next time we open the browser and create a new session to the site.
The alternatives would be to store it in an xml or Json file but that would not really be good of decision as we would have to keep one per user and somehow maintain that. Since we have no database in the template there is no way to tie it to table.
Others in the comments have expressed interest in this feature and adding it will give the users a much-needed functionality that is missing and causes the user to constantly have to close the menu anytime the page refreshes or the window size is adjusted.
The text was updated successfully, but these errors were encountered:
When I have closed or opened the sidebar menu, I would expect it to keep that state when I reload the page or go to another page. Currently, AdminLTE does not store the state anywhere.
Due to this being a template, there is a lack of options on where to store this state and the one that makes sense is the browser. If we store it in the browser then we have to decide what storage to use, local or session. I would expect this state to be there the next time I open the site, so it makes sense to me to store it in the local storage as the session storage would be gone the next time we open the browser and create a new session to the site.
The alternatives would be to store it in an xml or Json file but that would not really be good of decision as we would have to keep one per user and somehow maintain that. Since we have no database in the template there is no way to tie it to table.
Others in the comments have expressed interest in this feature and adding it will give the users a much-needed functionality that is missing and causes the user to constantly have to close the menu anytime the page refreshes or the window size is adjusted.
The text was updated successfully, but these errors were encountered: