The intent of this text is to attach these steps to the "loss of visibility" or "loss of full activity" event on any document. It feels like it should be something like,

When the user agent determines that a document is no longer fully active, it must run these steps:

1. Let document be that document.
2. ...

The abort all active watchAdvertisements algorithm should really be taking the document (or the document's navigator.bluetooth instance) as a parameter.

Does that make sense? Can you suggest the proper way to create such an event listener?

Thanks! The <object> spec does something similar:

Whenever one of the following conditions occur:
...

• the element's node document changes whether it is fully active,

...
(do some stuff)

so I'm guessing something like what you quoted would be fine.

CC @annevk

Yeah, probably. Getting some of this formalized better is a long-standing issue of the HTML standard.

What do you think of this?

When a document's visibility state changes,

1. Let document be the document.
2. Let global be document's relevant global object.
3. Queue a task on the Bluetooth event source with global and the following steps,
   1. If document’s visibility state is not "visible", then abort all active watchAdvertisements operations on global.

I'm unsure when I want to use the "document" concept vs. the "Document" interface.

To get the Bluetooth instance from a document it seems like I should go through the associated Navigator (given global) and define a similar "associated Bluetooth" concept which is used in the getter steps for the "bluetooth" attribute in the Navigator partial interface.