Make "Converting..." section normative#410
Merged
Merged
Conversation
- remove first note of https://w3c.github.io/pointerevents/#dom-pointerevent-getpredictedevents - salvage useful parts and move them to "Converting..." section https://w3c.github.io/pointerevents/#converting-between-tiltx-tilty-and-altitudeangle-azimuthangle - make "Converting..." normative, after tweaking sentence to clarify that UAs MUST use the algorithm https://w3c.github.io/pointerevents/#converting-between-tiltx-tilty-and-altitudeangle-azimuthangle However, note that with this approach, while we have the `Math.round` SHOULD, the algorithm doesn't actually use it. Does the algorithm need changing?
10 tasks
mustaqahmed
reviewed
Sep 29, 2021
Member
|
This is covered by the WPT pointerevent_tiltX_tiltY_to_azimuth_altitude.html. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
However, note that with this approach, while we have the
Math.roundSHOULD, the algorithm doesn't actually use it. Does the algorithm need changing?x-ref #405 https://www.w3.org/2021/09/01-pointerevents-minutes.html#t02
Preview | Diff