Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Make "Converting..." section normative #410

Merged
merged 1 commit into from Sep 29, 2021

Conversation

patrickhlauke
Copy link
Member

@patrickhlauke patrickhlauke commented Sep 13, 2021

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?

x-ref #405 https://www.w3.org/2021/09/01-pointerevents-minutes.html#t02


Preview | Diff

- 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?
@patrickhlauke patrickhlauke merged commit a76a7cd into gh-pages Sep 29, 2021
@patrickhlauke patrickhlauke deleted the patrickhlauke-notes-vs-normative branch September 29, 2021 15:10
@mustaqahmed
Copy link
Member

This is covered by the WPT pointerevent_tiltX_tiltY_to_azimuth_altitude.html.

@mustaqahmed mustaqahmed removed the wpt label Dec 20, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants