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

Jump to bottom

Add deviceorientation and devicemotion feature detection conformance requirement #12

Closed
wants to merge 1 commit into from
Closed

Add deviceorientation and devicemotion feature detection conformance requirement #12

Changes from all commits
Commits
Show all changes
1 commit
Select commit
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
10 changes: 10 additions & 0 deletions spec-source-orientation.html
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -205,6 +205,16 @@ <h2 id="conformance-requirements"><span class=secno>1 </span>Conformance require
<a href="#ref-domevents">[DOM4]</a>.
Implementations must therefore support this specification.

<p>When support for a feature is disabled (e.g. as an emergency measure to
mitigate a security problem, due to lack of sensor support in the current
platform, to aid in development, or for performance reasons), user agents
<em class="rfc2119" title="MUST">MUST</em> act as if they had no support for
the feature whatsoever, and as if the feature was not mentioned in this
specification. For example, if a particular feature is accessed via an
attribute in a Web IDL interface, the attribute itself would be omitted from
the objects that implement that interface - leaving the attribute on the
object but making it return null or throw an exception is insufficient.

<h2 id="introduction"><span class=secno>2 </span>Introduction</h2>

<p><em>This section is non-normative.</em>
Expand Down