fix: disable mutation observing when not supported #405
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Related Issue
Closes #404
Your solution
Disable mutation observing and display a message when MutationObserver is not supported by the browser.
How Has This Been Tested?
npm run build
npm test
(all tests passed)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 thenext
version, and duplicated on older versions for long-term support and quick-release purposes. Older versions should not contains features or fixes thenext
version does not have. This way, no regression will be made when releasing thenext
version.I tried to provide the same fix for the
next
branch, but thedisableMutationObserver
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.