diff --git a/index.html b/index.html index ee66bce..d1e087f 100644 --- a/index.html +++ b/index.html @@ -28,6 +28,9 @@ testSuiteURI: "https://w3c-test.org/vibration/", implementationReportURI: "https://w3c.github.io/test-results/vibration/20141118.html", processVersion: 2017, + xref: { + profile: "web-platform" + }, localBiblio: { "NOTIFICATIONS": { title: "Notifications API", @@ -113,20 +116,6 @@

as this specification uses that specification and terminology.

-
-

- Terminology -

-

- The concepts top-level - browsing context and spin - the event loop and the - Navigator interface are defined in [[!HTML]]. -

-

Vibration Interface @@ -139,9 +128,9 @@

};

- The vibrate() method, - when invoked, MUST run the algorithm for processing vibration - patterns. A vibration pattern is represented by a + The vibrate() method + steps are to run the processing vibration patterns algorithm. + A vibration pattern is represented by a VibratePattern object.

@@ -167,7 +156,8 @@

  • - Perform vibration with valid pattern. + Perform vibration with this's relevant global object + and valid pattern.
  • @@ -222,10 +212,15 @@

    - To perform vibration using pattern, run these - steps: + To perform vibration using a global object + global and a vibration pattern pattern, + run these steps:

      +
    1. + If global does not have sticky activation, + return false and terminate these steps. +
    2. An implementation MAY return false and terminate these steps.
      For example, an implementation might abort the algorithm because no @@ -262,7 +257,7 @@

    - When the user agent determines that the user agent determines that the visibility state of the Document of the top-level browsing context changes, it MUST abort the already running processing @@ -288,9 +283,9 @@

    enable physical identification, and possibly tracking of the user.

    - For these reasons, the user agent SHOULD inform the user when the API - is being used and provide a mechanism to disable the API (effectively - no-op), on a per-origin basis or globally. + For these reasons, the user agent SHOULD inform the user when + the API is being used and provide a mechanism to disable the API + (effectively no-op), on a per-origin basis or globally.