Added DOM_OBJECTS_UPDATED notification when the DOM is re-rendered via updateDom#3535
Conversation
in this case, yes. |
|
@ryan-d-williams the test fix is merged, best approach would be to rebase/merge your PR on new develop, thanks! |
|
@khassel is it possible to have an admin restart the tests? If develop was updated a restart should show the tests pass? I'm happy to do a rebase/merge, but that's going to take me a minute of fumbling around and probably destroying my branch at least a few times so if we can take the path of least resistance of restarting the tests I would appreciate it. If that's not possible I'll try to get the branch updated. |
yes, but they will run on the same commit and fail again if it is o.k. for you I can do the rebase |
…ed. Ensures the module can know when the DOM is available for interaction. Fixes MagicMirrorOrg#3534.
|
@khassel that would be great thank you! If you don't mind letting me know the steps you took - it's been a while since I've done a rebase like this so it would be nice to refresh my memory on it for next time. |
well, I'm using a graphical tool called "Git Extensions" under Windows, steps:
|
|
@khassel thank you! I made it to the end, but when I saw I had to force-push I figured I had messed something up. Thanks again! |
|
i think it should be fixed now in dev.. he just put in in current release.. don't need extra debt.. |
|
so I will fix it on |
|
done. |
|
My fault, sorry about that. Thanks for the fix @khassel |
|
No problem, it's not the first time and I hate the current construction with the changelog ... |
developbranch.npm run lint:prettierbefore submittingMore info can be found in #3534, but as a summary:
The
updateDomfunction is not synchronous - there is an undetermined amount of time between when it completes and when the DOM has actually been re-rendered and is ready for interaction. The existing notification (MODULE_DOM_CREATED) only fires once on the initial DOM render. This PR solves the issue of subsequent re-renders by adding a new notification that fires whenever the DOM is ready after an update. This notification falls within expected lifecycle notifications (very similar to other libraries that provide DOM lifecycle notifications).