w3c/csswg-drafts

[cssom-view] screenX/Y are being redefined as double, should movementX/Y as well?

Open

#1,634 opened on Jul 20, 2017

View on GitHub
 (3 comments) (0 reactions) (0 assignees)HTML (3,546 stars) (545 forks)batch import
Help Wantedcssom-view-1

Description

CSSOM View Module ED extends MouseEvent's screenX to a double.

Pointer Lock REC extended MouseEvent by adding readonly attribute long movementX.

Should CSSOM View Module also extend movementX to double? Or, should this be updated only in Pointer Lock 2? (This was initially raised in https://github.com/w3c/pointerlock/issues/24)

Contributor guide

Tech stack
htmljavascript
Domain
apifrontend
Issue type
research
DifficultyEstimated implementation difficulty for a new contributor, from 1 for very small changes to 5 for expert-level work.
3
Estimated timeA rough time range for an experienced contributor to investigate, implement, test, and prepare a pull request.
under 1 hour
Activity statusHow available the issue appears right now: fresh, active, stale, blocked, or waiting on maintainer input.
stale
ClarityHow clearly the issue explains the expected change, acceptance criteria, and next step.
clear
Prerequisites
Understanding of CSSOM View specFamiliarity with Pointer Lock API
Newbie friendlinessA 1-100 score estimating how approachable this issue is for first-time contributors.
25
Research direction
Investigate the current definitions of screenX/Y and movementX in CSSOM View and Pointer Lock specs. Review the discussion in pointerlock issue #24 and decide if movementX should be updated to double. Comment with a proposal and rationale.