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.

Sign up for GitHub

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

DeviceOrientationEvent: Define absolute's value on error #139

Merged
merged 2 commits into from
Feb 14, 2024
Merged

DeviceOrientationEvent: Define absolute's value on error #139

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
06cbad3
DeviceOrientationEvent: Define absolute's value on error
Feb 13, 2024
1607c06
Fix typos
Feb 14, 2024
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 2 additions & 4 deletions index.bs
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -388,10 +388,9 @@ Whenever a <a>significant change in orientation</a> occurs, the user agent must

<!--
* https://github.com/w3c/deviceorientation/issues/118: Does this mean a single event should be fired?
* https://github.com/w3c/deviceorientation/issues/119: Should absolute's value be set here too?
* Should this be a proper <dfn> in an algorithm?
-->
If an implementation can never provide orientation information, the event should be fired with the {{DeviceOrientationEvent/alpha}}, {{DeviceOrientationEvent/beta}} and {{DeviceOrientationEvent/gamma}} attributes set to null.
If an implementation can never provide orientation information, the event should be fired with the {{DeviceOrientationEvent/alpha}}, {{DeviceOrientationEvent/beta}} and {{DeviceOrientationEvent/gamma}} attributes set to null, and the {{DeviceOrientationEvent/absolute}} attribute set to false.

<h3 id="deviceorientationabsolute">deviceorientationabsolute Event</h3>

Expand All @@ -418,10 +417,9 @@ Whenever a <a>significant change in orientation</a> occurs, the user agent must

<!--
* https://github.com/w3c/deviceorientation/issues/118: Does this mean a single event should be fired?
* https://github.com/w3c/deviceorientation/issues/119: Should absolute's value be set here too?
* Should this be a proper <dfn> in an algorithm?
-->
If an implementation can never provide absolute orientation information, the event should be fired with the {{DeviceOrientationEvent/alpha}}, {{DeviceOrientationEvent/beta}} and {{DeviceOrientationEvent/gamma}} attributes set to null.
If an implementation can never provide absolute orientation information, the event should be fired with the {{DeviceOrientationEvent/alpha}}, {{DeviceOrientationEvent/beta}} and {{DeviceOrientationEvent/gamma}} attributes set to null, and the {{DeviceOrientationEvent/absolute}} attribute set to true.

<h3 id="devicemotion">devicemotion Event</h3>

Expand Down
Loading