The WebBrowserComponent hosts a native webbrowser. the web browser itself is NOT juce code, so what ever that page loaded into the browser contains will behave as it normally does.
It seems like you have just repeated your question. Could you attempt to be more specific? maybe describe exactly what it is you want to do?
I think he’s asking about communication between the juce app and whatever’s executing inside the browser…
Correct me if I’m wrong, but I think the browser would be its own self-contained process, so I think you’d have to load some web app you’ve created that can respond to external events, perhaps via OSC or gRPC, then you can send those commands from your Juce app
Yes, that was the answer I was trying to give. it is a stand alone component. you can also communicate from the browser to your app by opening a socket in your app, which listens to a specific port, and have the web page communicate via localhost with that port. I have done experiments with that a few years ago, and it worked like a champ. although I was worried about firewalls, etc getting in the way.