Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Validate state transitions. #113

Closed
riju opened this issue Jun 1, 2016 · 2 comments
Closed

Validate state transitions. #113

riju opened this issue Jun 1, 2016 · 2 comments
Labels
api-refactoring ED-ready non-normative resolved
Milestone
Level 1

Comments

@riju
Copy link
Contributor

riju commented Jun 1, 2016 •
edited
Loading

Its more of a note for implementators.
In the updateState() function, validate the state transitions.

state_change
@bbernhar
Copy link

bbernhar commented Aug 2, 2016

It seems unnecessary to fire a 'statechange' event during the Activating->Active transition, where updateState(Active) would have already dispatched a 'readingchange' event. The current spec 9.8, could further clarify when these transition events are required to fire.

@tobie tobie modified the milestone: Level 1 Oct 27, 2016
@tobie tobie added the resolved label Oct 28, 2016
@tobie
Copy link
Member

tobie commented Oct 28, 2016 •
edited
Loading

See decisions made in #104 where statechange events are dramatically simplified.

@tobie tobie closed this as completed Oct 28, 2016
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
api-refactoring ED-ready non-normative resolved
Projects
None yet
Milestone
Level 1
Development

No branches or pull requests
4 participants
@tobie @anssiko @riju @bbernhar