-
Notifications
You must be signed in to change notification settings - Fork 49
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
hide_toolbar only works on initial view #307
Comments
Glad you like wallpanel! |
Hi Jan, |
I experience the same problem. When I click on a back button which I made with bubble-card and simply navigates to the dashboard URL, the toolbar isn't hidden anymore. When I use the toolbar, it navigates to the view I clicked on, but then it does hide the toolbar. |
Please check if wallpanel 4.33.0 fixes the problem. |
Hi, for me it does not fix the issue. Whenever I switch to a different dashboard, wallpanel isn't active. The screensaver doesn't work either. Upon clicking one of the views on the top bar, wallpanel is active again. Embedding wallpanel in the url in the button I use, does not work either. Only reloading the page or switching to a different tab on the top bar works. |
Hi Jan, |
First, thanks for this project! I love it. So many cool things are possible with this.
I have the wallpanel setup with this config:
The wallpanel is only enabled for my tablet. As recommended I use the
browser_mod
for that.It all works fine when the dashboard gets loaded initially in Fully Kiosk Browser. The sidebar and the toolbar are hidden on the tablet.
When I then navigate to a subview on the dashboard, the top toolbar appears (which is necessary and good I guess because otherwise you wouldn't be able to go back). But when I then navigate back to the main view (with the arrow in the top left corner) the top toolbar stays activated and visible. Is this expected behaviour? I would expect that the toolbar would then be hidden again. Not sure if this is fixable or that once any navigation started the toolbar has to be visible for some reason.
The only way to get it working again for me is to refresh the browser or restart FKB.
The text was updated successfully, but these errors were encountered: