-
-
Notifications
You must be signed in to change notification settings - Fork 144
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
[@thi.ng/rdom] setScheduler
not behaving as expected
#402
Comments
postspectacular
added a commit
that referenced
this issue
Jan 14, 2024
BREAKING CHANGE: remove scheduler, update IComponent and various DOM update fn signatures - remove scheduler support since never used (other than default/dummy `NullScheduler`) and `RAFScheduler` logic is better handled via `synRAF()` or similar (also see #402) - update IComponent.mount() signature to use `ParentNode as type for `parent` arg, e.g. to support use w/ `ShadowRoot` - update various DOM update fns with same parent arg type - update all utility components/wrappers
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
It seems that
setScheduler(new RAFScheduler())
does not behave properly because the number of job objects are out of sync with the DOM objects that are created (more DOM object are created that actually exists in the jobs stream). The only way I can have the list of jobs synced with the DOM is by usingsyncRAF
.The text was updated successfully, but these errors were encountered: