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

Fixes a crash if document.body is not ready yet #144

Merged
merged 1 commit into from
Aug 4, 2016

Conversation

jantimon
Copy link
Contributor

@jantimon jantimon commented Aug 3, 2016

Ally tries to access document.body to soon.
This fix uses document.documentElement which is the "html" element.

@coveralls
Copy link

coveralls commented Aug 3, 2016

Coverage Status

Coverage remained the same at 98.872% when pulling e1f5f5d on jantimon:master into e8c65f7 on medialize:master.

@jantimon jantimon changed the title Fixes a crash if document.body is not yet Fixes a crash if document.body is not ready yet Aug 3, 2016
@rodneyrehm
Copy link
Member

Nice catch, thank you!

I guess "accessing document.body too soon" happens when you synchronously load ally.js in <head>?

@rodneyrehm rodneyrehm added the bug label Aug 3, 2016
@jantimon
Copy link
Contributor Author

jantimon commented Aug 4, 2016

Correct - during dev we bundle it and the result is placed in the head (because of some other dev tools).

@rodneyrehm rodneyrehm merged commit b442166 into medialize:master Aug 4, 2016
rodneyrehm added a commit that referenced this pull request Aug 4, 2016
@jantimon
Copy link
Contributor Author

jantimon commented Aug 4, 2016

Cool thanks 👍 will there be a 1.1.1?

@rodneyrehm
Copy link
Member

Nope, but there will be a 1.2-alpha.1 soon. If you need the changes right away, you can import the build containing your fixes directly:

"dependencies": {
  "ally.js": "https://s3.eu-central-1.amazonaws.com/ally.js/travis/565/ally.js.tar.gz",
}

@jantimon
Copy link
Contributor Author

jantimon commented Aug 4, 2016

I guess my teammates won't understand which version https://s3.eu-central-1.amazonaws.com/ally.js/travis/565/ally.js.tar.gz is ;)

Maybe I gonna use the github repository of the fork like:

"dependencies": {
  "ally.js": "jantimon/ally.js"
}

Is there any reason why ally.js is not following semantic versioning?

@rodneyrehm
Copy link
Member

Maybe I gonna use the github repository of the fork like:

That won't contain the UMD build, as well as the AMD and CommonJS modules. If you're using the ES6 source modules, this is an option. I'd recommend going with the artifact I've linked to, as that's exactly what you'd get from npm (except for the version described in package.json).

Is there any reason why ally.js is not following semantic versioning?

semver defines what kind of version bump is appropriate for what kind of change. As far as I know it does not, however, mandate that a change must be released right away. The pre-release version notation is in line with semver. I don't think "ally.js is not following semantic versioning" is a correct assessment.

The release process is manual, as I have not yet gotten around to automatic/continuous releases. Also I have other things I'm still working on (albeit not at the speed I'd like to).

Are you're interested in helping out with this?

@jantimon
Copy link
Contributor Author

jantimon commented Aug 4, 2016

Sure - what can I do to help you with it?

@jantimon
Copy link
Contributor Author

jantimon commented Aug 4, 2016

Do you know https://github.com/semantic-release/semantic-release ?
It would work quite well together with your commit messages.. however I am not sure if this would also update your github pages..

It will create a release for every master commit (so it requires squashing commits during merging).
Works also well together with greenkeeper

@rodneyrehm
Copy link
Member

I know of semantic-release, but I haven't tried to integrate it yet. Mainly because I think my commit messages are not 100% compatible…

@jantimon
Copy link
Contributor Author

jantimon commented Aug 4, 2016

Oh that's configurable.

rodneyrehm added a commit that referenced this pull request Aug 6, 2016
rodneyrehm added a commit that referenced this pull request Aug 6, 2016
rodneyrehm added a commit that referenced this pull request Aug 6, 2016
@rodneyrehm
Copy link
Member

Your fix is included in v1.1.1 released just now.

@jantimon
Copy link
Contributor Author

jantimon commented Aug 7, 2016

Thank you so much! 👍

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants