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
HA 2023.4 Hide header not working #566
Comments
I am seeing this as well |
Also seeing the same with hiding the sidebar |
Put me on the list. For Sidebar as well. |
Sidebar and header not hiding this side |
I found the same issue. It also affect the HACS kioskmode hide header functions. |
same here! |
Same here for sidebar (i'm not using header) since 2023.4 update |
ah, ok, yeah, i was using kiosk mode, but it was broken, wanted to try out this one instead, but it doesnt work indeed, now i know its not me |
Samen for me. Tha whole Lovelace seemed top be changed, as all my themes don't have any background anymore. |
with 'wallpanel lovelace' work well, hiding by CSS.. |
same here! |
same here! |
Instead of all saying "Same", just thumbs up the first post to keep this thread clean. |
Hello, if this issue is blocking, you can try my workaround: Just replace the one in your config folder: and delete the gzip version: /config/custom_components/browser_mod/browser_mod.js.gz Then restart your HomeAssistant: Developer Tools > Check and Restart > Restart Attention: this workaround works only in 2023.4+ Let me know if it works for you! |
Nope Doesn't work here. |
Didn't work for me either |
Maybe a cache issue? When you download the file on your http[s]://[ha]/browser_mod.js |
Yes of course it was caching, I feel so stupid now!!.. |
No worries, I hope we will soon have an official release with the fix 😉 |
Same issue here. Sidebar is not hide. |
This solution only works in browser, not in apk ??? |
Not working! |
Thanks I can confirm this works for me on iOS and Desktop after clearing cache. |
seems kiosk mode integration fixed it. |
@olibos I followed your workaround and refreshed my browser. The header background is now gone, however a small portion (bottom half) of the header title is visible/protruding from the top of screen. Is there any other configuration I need to adjust for removing the header title completely? |
Hello @vhardono , I think it's a limitation of my workaround. |
thanks for your effort anyway! :) |
This still seems to be broken for me after your fix. HA 2023.4.1 |
Not sure if this applies to you but I thought it wasn't working with FullyKiosk but then I cleared the cache (in FullyKiosk) and all was well. |
Def clear cache, that should work. |
Clearing the Fully Kiosk cache worked thanks! Thought restarting the app would be enough, but I guess not. |
The fix is not working correctly. |
Do you mean the button to reveal the sidebar - which is in the header - is not vissible when you've chosen to hide the header? |
Same here. |
@thomasloven However, I was always able to see the side panel by swiping right on the screen. The side panel will momentarily appear and then hide again. Right now that's not possible. I.e. the side panel is fully locked and can't be accessed. The only way is to disable the 'hide title' option |
This is not related to Browser mod, they changed something in frontend: |
My Home Assistant version: 2023.4
What I am doing:
I updated to HA 2023.4
What I expected to happen:
Header should be hidden.
What happened instead:
Header are not hidden.
Minimal steps to reproduce:
I just updated.
Error messages from the browser console:
Nothing
By replacing the space in the checkboxes ([ ]) with an X below, I indicate that I:
Understand that this is a channel for reporting bugs, not a support forum (https://community.home-assistant.io/).
Have made sure I am using the latest version of the plugin.
Have followed the troubleshooting steps of the "Common Problems" section of https://github.com/thomasloven/hass-config/wiki/Lovelace-Plugins.
Understand that leaving one or more boxes unticked or failure to follow the template above may increase the time required to handle my bug-report, or cause it to be closed without further action.
The text was updated successfully, but these errors were encountered: