Not right now. I can play with making it an action but the library is picky about the vet being fired while wrapped in a click listener. That said, I think I can mimic the click event. Keep checking back. I’ll post more next week on this topic!
I’m not sure on the actual system impact. I guess it’s more of a courtesy to let someone know you’ll be implementing a screen lock is all. What anyone does when they use this plugin in that regard though, is out of my hands. I did my due diligence
If you use the element and element action, there’s no exposed states. Just a toggle.
If you add the element, you’ll have states to designated active vs not active BUT you need to use a clickable item to activate. (Really any element you can click that has an ID)
Next up, add the element but no button I’d required!
I think that for NoSleep to work on iOS, NoSleep must be started through a workflow initiated by the user tapping or otherwise interacting with the page.
I believe you can not have NoSleep start on Page Load (before user taps the screen) and can not have NoSleep start from an event that is not a user interaction.
Apple puts this restriction on playing of videos (which is how NoSleep works) similar to how they restrict playing of audio without interaction.