W3C home > Mailing lists > Public > public-apa@w3.org > July 2016

Fwd: API mapping for pointerlockchange event?

From: Michiel Bijl <michiel@agosto.nl>
Date: Wed, 6 Jul 2016 18:49:33 +0200
To: W3C WAI Accessible Platform Architectures <public-apa@w3.org>
Message-Id: <BFE4046F-3E5E-4B95-8782-ADE387DE96F5@agosto.nl>


—Michiel

> Begin forwarded message:
> 
> From: Léonie Watson <tink@tink.uk>
> Subject: API mapping for pointerlockchange event?
> Date: 5 July 2016 at 15:57:28 GMT+2
> To: public-aria@w3.org
> Resent-From: public-aria@w3.org
> Reply-To: tink@tink.uk
> 
> Hello API people,
> 
> Pointer Lock is an API that provides scripted access to mouse movement data, locks mouse events to a single target, and removes the on-screen cursor [1].
> 
> The pointerlockchange DOM event is fired to indicate when a pointer lock has been engaged/disengaged. Per an issue raised on behalf of APA, this has implications for ATs - in particular screen magnifiers [2].
> 
> The Pointer Lock spec includes a note that acknowledges the need for browsers to communicate to ATs when a pointerlockchange event is fired [3]. The next logical step seems to be to find a place in the APIs for this to be handled - but I'm not sure of the process for doing this, so over to you for thoughts!
> 
> Thanks.
> 
> Léonie.
> [1] https://www.w3.org/TR/pointerlock/
> [2] https://github.com/w3c/pointerlock/issues/1
> [3] https://w3c.github.io/pointerlock/#dfn-pointerlockchange
> 
> -- 
> @LeonieWatson tink.uk Carpe diem
> 
Received on Wednesday, 6 July 2016 16:50:07 UTC

This archive was generated by hypermail 2.3.1 : Wednesday, 6 July 2016 16:50:07 UTC