Making it easier to handle the state of extendable events #1348
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Currently it's impossible for another spec to know if an extendable event is in progress, or what the result was afterwards.
I intended to just mark some things as "export", but tried to tidy up the useage along the way.
ExtendableEvent
's extend lifetime promises is now exported.ExtendableEvent
now has a timed out flag, which makes the user agent timeout a little more formal and detectable by other specs.ExtendableEvent
now has an active 'getter', which indicates the event is in progress.If this is ok, I'll make the same changes in v1.
Preview | Diff