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.

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

Rework event dispatching #162

Merged
merged 1 commit into from Mar 6, 2017
Merged

Rework event dispatching #162

merged 1 commit into from Mar 6, 2017

Conversation

inexorabletash
Copy link
Member

Use 'fire an event' steps when easy, proper event creation and 'dispatch' steps otherwise.

proper event creation and 'dispatch' steps otherwise.
must use the [=Event=] interface and set the
{{Event/type}} attribute to "<code>success</code>". The
event does not bubble and is not cancelable. If the steps
to |result| and [=fire an event=] named
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Is this different from the "fire a success event" algorithm defined below?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Yes, see the note just below this algorithm. "The firing of..."

Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Thank you for clarifying! The GitHub edit window is too small... I'll review the changes with the HTML on the right.

@pwnall
Copy link

pwnall commented Mar 6, 2017

LGTM.

@inexorabletash inexorabletash merged commit 9a26037 into gh-pages Mar 6, 2017
@inexorabletash inexorabletash deleted the dispatch branch March 7, 2017 20:42
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants