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

Listen to events in the AMD callback, not during load time #140

Merged
merged 3 commits into from
Jun 4, 2014

Conversation

jonathanweiss
Copy link
Contributor

No description provided.

drublic and others added 2 commits May 25, 2014 12:14
Bean does not seem to support hashchange for IE8 properly. This
commit fixes this behavior by utilizing attachEvent for IE8.
@@ -366,6 +372,7 @@
// Expose modal for loaders that implement the Node module pattern.
if (typeof module === 'object' && module && typeof module.exports === 'object') {
module.exports = modal;
modal.init();
Copy link
Owner

Choose a reason for hiding this comment

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

This won't work I guess. Can we not evoke the modal.init()-function in case we export the module? Same goes for the case when we make CSSModal publicly available on the global space. Maybe we should document this?
Any objections?

Copy link
Contributor Author

Choose a reason for hiding this comment

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

The later case (} else if (typeof global === 'object' && typeof global.document === 'object') {) works well. I'm not sure about how module.exports though… We could document that one must call modal.init() before using the modal in a Node / Browserify environment.

@drublic drublic merged commit 0d4f3b2 into master Jun 4, 2014
@drublic drublic added this to the v1.2.0 milestone Jun 5, 2014
@drublic drublic deleted the ie8-support branch June 23, 2014 17:36
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