Open rakuco opened 11 months ago
I think Chromium puts the sensor into an essentially "stopped" state and so only one event is fired but the concept of "stopped" and "started" don't really exist in this spec.
Do we want to try address this by the upcoming CR Snapshot or defer for later? Works both ways.
Discussed in https://www.w3.org/2024/02/12-dap-minutes.html#t10
@rakuco took an action item to discover what the implementation consensus (if any) is on this behavior. If the answer is simple we could adjust the specification test to clarify but I don't think this is blocking.
Each of the 3 event types defined in this specification have an excerpt that looks like this:
This does not look entirely clear to me: