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

I agree with @reillyeon, and have similar opinion to other specification issues on whether we should drop vs send the latest update e.g. the [Permissions](https://github.com/w3c/permissions/issues/162#issuecomment-896472965) and Geolocation APIs now.

I'm now going to revise my [TAG Design Principles guidelines update](https://github.com/w3ctag/design-principles/pull/317) to explicitly mention how existing APIs should be updated to align better with the [Priority of Constituencies](https://www.w3.org/TR/design-principles/#priority-of-constituencies):
* If we leave the responsibility to the developer to proactively update their sites to handle bfcache, end users might end up potentially suffering inexplicable errors on sites that don't explicitly support BFCache.
* Specifying ways to make existing usage of existing APIs to more or less seamlessly work with BFCache seems to be the right choice, as the burden should be on browsers to make sure things will work (either by expending effort to implement support for the features, or disabling BFCache when that's not possible).

(And more specifically, changing the recommendation from  "drop updates" to "save the last state and send it" instead, as that seems to be a common use. Glad that we're having all these spec discussions that makes us rethink our recommendation!)

-- 
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-896508025