From 92d9e10039df8d3654b633653d627f2ba7e8ebb9 Mon Sep 17 00:00:00 2001 From: Jake Archibald Date: Mon, 12 Oct 2015 11:22:45 +0100 Subject: [PATCH] Reusing onLine definition Does it make sense to reference `navigator.onLine` here as a minimum viable definition? Also, I adjusted the wording to suggest the UA may use *connectivity* to the target origin as a signal. Does this fit with the intention of this definition? --- spec/index.bs | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-) diff --git a/spec/index.bs b/spec/index.bs index 2b5def8..6ac4700 100644 --- a/spec/index.bs +++ b/spec/index.bs @@ -37,6 +37,7 @@ spec: ecma-262; urlPrefix: http://www.ecma-international.org/ecma-262/6.0/ spec: html; urlPrefix: https://html.spec.whatwg.org/ type: dfn text: trusted; url: concept-events-trusted + text: navigator.onLine; url: dom-navigator-online spec: powerful-features; urlPrefix: https://w3c.github.io/webappsec/specs/powerfulfeatures/# type: dfn @@ -99,7 +100,7 @@ spec: WebIDL; urlPrefix: https://heycam.github.io/webidl/# The sync event is considered to run in the background if the user agent is either closed or no service worker clients (controlled or uncontrolled) exist for the corresponding service worker registration. - The user agent is considered to be online if the user agent has established a network connection. A user agent MAY use a stricter definition of being online. Such a stricter definition MAY take into account the particular service worker or origin a sync registration is associated with. + The user agent is considered to be online if navigator.onLine is true. A user agent MAY use a stricter definition of being online. Such a stricter definition MAY take into account connectivity to the particular service worker or origin the sync registration is associated with.