🌐🎓 Web dialogs (inspect layout, better support)

1. Automate Community
2. Tutorials & Examples

Let us look at web dialogs and improve a flow i came across browsing. This edit should be able to communicate from the web dialog to automate without closing the dialog to control the flow behavior.

My first attempt was the consol log in Javascript and reading the debugging log with logcat. This works on my Android 12 tablet but not on my Android 10 phone.
This is an alternative solution i developed to support more devices. It uses the title to determine which fiber should receive the message and the url to share the data from the web dialog.

The url has the following data as get query parameter:
c - this is a counter that will increase by 1 each time the web dialog wants to send something. This is needed to update the dialog in order to trigger the inspect block as well as prevent receiving the same data transfer twice.
a - an keyword indicating what action was triggered.
p - additionall data payload that might get evaluated by the action fiber, default is empty.

There still are a lot of things we can improve here.
- We don't actually need a counter from 1 to n. Just something alternating (single changing bit 0,1) could be enough. But i have not testet it so i kept the counter.
- reduce block size
- rewrite html page to make it easier to understand
...

Thanks Danny Hpy for their flow.
https://llamalab.com/automate/community/flows/28839

Web pages are not really used by the community. But it could reduces significantly the amount of used blocks in a flow and have a lot of advantages. (like ability to make games, display any image/ any video or any content like in an app, make dynamic webpages with HTML,CSS,JS, and more...)

This flow is just a demonstration on how to interact with Automate within a webpage. Good luck, people.