[go: up one dir, main page]

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

fix: disable mutation observing when not supported #405

Conversation

ncoden
Copy link
Contributor
@ncoden ncoden commented Oct 2, 2018

Related Issue

Closes #404

Your solution

Disable mutation observing and display a message when MutationObserver is not supported by the browser.

aos: MutationObserver is not supported on this browser,
code mutations observing has been disabled.
You may have to call "refreshHard()" by yourself.

How Has This Been Tested?

  • npm run build
  • linked and tested in an other project
  • npm test (all tests passed)
  • search for possible side-effects

Note

When preparing a new version, the next version should always be ahead of the past versions. When bugfixes are or new features are added, they should be made in priority on the next version, and duplicated on older versions for long-term support and quick-release purposes. Older versions should not contains features or fixes the next version does not have. This way, no regression will be made when releasing the next version.

I tried to provide the same fix for the next branch, but the disableMutationObserver is not implemented on it. This is a real problem with the development workflow of this project. I would recommend you to take a look at the Foundation Contributing Guidelines that explains how we deal with the parallel development of several versions.

Disable mutation observing and display a message when MutationObserver is not supported by the browser.

Closes michalsnik#404
@ncoden
Copy link
Contributor Author
ncoden commented Oct 2, 2018

@michalsnik

Copy link
Owner
@michalsnik michalsnik left a comment

Choose a reason for hiding this comment

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

Thanks for the PR! It looks good to me 👍 I’m also aware of how the process or developing two versions simultanosly should look like :) I just wasn’t that active recently due to other projects I’m participating in and other stuff. The PR with disableMutationObserver was created while I was working on the “next” branch before releasing it, hence it got to master, and then I didn’t forget to pull this to next. I’m happily accepting PR’s to v2 branch but only with bug fixes and small features (until I release v3 officially, then only bug fixes). Every other PR should land on „next”.

@michalsnik michalsnik merged commit bdad43c into michalsnik:v2 Oct 3, 2018
@ncoden ncoden mentioned this pull request Oct 3, 2018
michalsnik pushed a commit that referenced this pull request Oct 3, 2018
Disable mutation observing and display a message when MutationObserver is not supported by the browser.

Closes #404
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.

2 participants