Re: [w3ctag/design-reviews] Captured Surface Control (Issue #962)

@jyasskin, @hober, and I discussed this today.

Thank you for bringing this to us. We think this seems like a generally useful feature, but we have some questions and suggestions for the explainer:

The explainer should discuss the alternative design of having the page cooperate, and accept dedicated events from the capturing process. We think there are both upsides and downsides to that option that deserve exploration.

The two interactions that are considered are scrolling and zooming.  Is that list exhaustive?  Are these uniformly safe to do?  Are there not occasions where scrolling results in changes to things like form elements?  That could require a change of focus before sending the events in, maybe, though with precise X and Y on events, that might still engage the element that is targeted.  We're inferring that this is limited to those two actions because "spoofing" those events is safe, but the explainer doesn't give enough details to show that that's true.
  
There seems to be some heightened permissions UX being contemplated here.  It's not clear to us what would be different from a regular screen capture.  It would be helpful if the explainer could show a proof of concept that highlights those differences.


-- 
Reply to this email directly or view it on GitHub:
https://github.com/w3ctag/design-reviews/issues/962#issuecomment-2327555698
You are receiving this because you are subscribed to this thread.

Message ID: <w3ctag/design-reviews/issues/962/2327555698@github.com>