-
-
Notifications
You must be signed in to change notification settings - Fork 17
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
[FR] Hide header on iframe page #319
Comments
Hi @chriexpe, |
So that "AgentDVR" header with HA buttons like Search/Assistant/Edit are over the iframe? I tried inspecting the element and even if I remove it, there's still a bar behind that can't be separated from the iframe... |
The regular header (the one with the views and with the buttons to search and assist) is an element that belongs to the main document. It will be there even if you don't have any iframe.
Most probably. When I mentioned that you would need to remove it in the origin that is serving the page, I was referring to do it manually in the source code. I don't think that the developers will accept to remove a header just to match your use case, but at least you can ask how to do it by yourself. |
Hi @chriexpe, Most probably some hack can be done with |
Hi @chriexpe, Using a card-mod theme. Supposing that the height of that header is
card-mod-theme: the-name-of-your-theme
card-mod-view-yaml: |
hui-panel-view$:
hui-iframe-card$: |
iframe[src*="something"] {
height: calc(100% + 100px);
margin-top: -100px;
} |
First of all I'd like to thank you for continuing the kiosk-mode project, it works like a charm!
My situation is the following about iframe: I have one tablet dedicated to Home Assistant on Kiosk Mode, and one of the tabs I also added my NVR webpage, so I can check the cameras and recordings without leaving Fully Kiosk Browser app, but I find hideous that huge header that has no use whatsoever and only occupies valuable space, especially on smaller screens.
So I wonder, is it possible to hide it?
The print above is the iframe of NVR page and that header showing up.
The text was updated successfully, but these errors were encountered: