Skip to content

fix: trigger dom mutation observer independent of insertion order #847

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

Merged
merged 1 commit into from
Oct 15, 2019

Conversation

pskelin
Copy link
Contributor

@pskelin pskelin commented Oct 15, 2019

DOM insertion order was leading to situations where the mutation
observer was not registered
leaving empty rendered rows

fixes: #839

DOM insertion order was leading to situations where the mutation
observer was not registered
leaving empty rendered rows

fixes: #839
@pskelin pskelin merged commit d7d96ec into master Oct 15, 2019
@pskelin pskelin deleted the fix-dom-observer-order branch October 15, 2019 13:33
@fifoosid
Copy link
Contributor

fixes #936

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.

[ui5-table-row] Table rows are invisible when added after initialization
3 participants