-
-
Notifications
You must be signed in to change notification settings - Fork 64
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
A way to toggle the Fullscreen mode with a service. #237
Comments
I'm afraid I think this is technically not feasible. The Javascript fullscreen API can only be activated by a human action. You can imagine the amount of abuse/spam there'd be if this protection was not present (e.g. visit a site and the spam/ad is instantly fullscreen). I did a quick test of going to fullscreen without a human interaction, and Chrome logs:
A [totally untested] trick could be to make a new dashboard in panel mode with a single instance of the card. That could be independently navigated to, and you could use something like browser-mod to control the navigation. |
Closing as not implementable for the reasons described. |
Sorry! Thought my answer has been sent. I will try to find a way to keep a conditional card pre-loaded! |
Is your feature request related to a problem? Please describe.
I currently switched to using this card to stream on multiple displays.
And in many instances, I want those displays to display the fullscreen mode in certain moments.
For instance when someone is at the door, or motion is detected at the back door!
I currently use conditionals cards, but with the initial loading time, the use is not ideal.
Describe the solution you'd like
A way to trigger the fullscreen action from somewhere else.
Or even based on conditions using templating
Describe alternatives you've considered
The use of the Conditional card was acceptable until the introduction of the "disableWebAssembly" fix, which seems to add an initial loading time
Additional context
Nothing more, but amazing work, and thanks a lot for the support!
The text was updated successfully, but these errors were encountered: