How capturer web applications can know whether forwarding is working/useful

[youennf]

When trying to use google maps via capture control, it was clear to me that forwarding can lead to poor user experience.
Maybe this is due to the prototype and improvement to capture control forwarding will fix the issue.
Or maybe not.

This begs the question of how a web application can know whether enabling forwarding is useful or not.
Is it purely a user's decision or is there a way for web pages to get more insight into when to enable forwarding?

[eladalon1983]

Maybe this is due to the prototype

We timeboxed the development of the demo. It was not intended as a professional product, and we intentionally chose to only implement very rudimentary UX.

The demo does know when forwarding works, and it's even easier after the transition to captureWheel(). (I am not sure which part was confusing. If you tell me, I could possibly fix the demo.)

The app can trivially track the forwarding state as follows:

• Forwarding starts after the promise returned by captureWheel() resolves.
• Forwarding stops if:
  • The app calls captureWheel(null).
  • The app programmatically stops the capture.
  • Anything else stops the capture (e.g. the user stops the capture or closes the captured tab). The app knows this through the pre-existing onended event handler.

Is this not sufficient?

[eladalon1983]

Issue transferred; heads up to those discussion participants who might otherwise be looking for it elsewhere: @jan-ivar, @youennf