Re: [w3c/gamepad] gamepadconnected/disconnected events & non-"fully active" documents (#149)

> Not sure if I get what you're suggesting correctly, but I think this applies to most events that come from "external sources" (e.g. devices), 

Right, yes.  

> while "internal events" (changes to DOM?) are less of a problem because we won't run tasks/scripts within the non-fully active document itself. 

In the sentence above, who is "we" in "we won't run tasks"? Do you mean the browser or something specific that guards against that in a spec? 

> Providing general guidance on top of the TAG docs sounds good, how should we do that?

I guess we could have a go here (or in Geo) at preparing a pull request... then based on that, we can see if some general guidance is needed about how to write whatever prose is needed. 

It's also really helpful that various specs have been identified as needing changes. We could maybe link, or quote, to the appropriate prose from those specs (e.g., Screen Wake Lock). 

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/w3c/gamepad/issues/149#issuecomment-846779063