#475: isInputPending
Discussions
2020-04-13
David: This is marked as untriaged, which seems like an error on our end. There is a run-to-completion violation, which may or may not be a significant issue.
Peter: There can be cases where it makes sense to violate. Is there already a navigator.scheduling interface or does that need to be created?
David: Doesn't exist in Gecko as of now
Sangwhan: Have minor comments, but not significant enough for minutes, will comment later
Peter: Any other feedback? One thing that is weird is that requires instantiation? The notion of "continuous events" sounds foreign, is this specific to this spec? Otherwise seems okay with me.
There is also a mention of isFramePending..
David: Did you have any comments on continuous events?
Peter: I was concerned that it was a spec-specific nomenclature, should probably be defined elsewher
2020-04-27
David: People seem to be ok with the run-to-completion violation... need to look at the response in more detail. We may be able to close this at the plenary.
... Will mark as propose close.
OpenedFeb 18, 2020
Hello TAG!
I'm requesting a TAG review of isInputPending. There was some prior discussion here, however it appears to have pivoted to discuss the postTask family of APIs.
In a nutshell, isInputPending is an API for developers to provide more intelligent cooperative multitasking by allowing developers to yield efficiently when there is pending user input to be handled.
Further details:
You should also know that...
We'd prefer the TAG provide feedback as (please delete all but the desired option):
💬 leave review feedback as a comment in this issue and @-notify @acomminos, @n8schloss