-
-
Notifications
You must be signed in to change notification settings - Fork 140
[Bug]: Clarify how sync() works #856
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
Comments
Furthermore
This happens because |
Ok.
and are ignored here:
during the call |
I fixed the problem by changing the line in -const settings = get_settings ? getSettings( self.input, {delimiter:self.settings.delimiter} as RecursivePartial<TomSettings> ) : self.settings;
+const settings = get_settings ? getSettings( self.input, self.settings) : self.settings; It looks good, except the selected option at is not reflected by TomSelect and the previous options are not cleared. |
I think I have the same bug. I am modifying the underlying select element's options and then I Not sure if this is intentional but quite sure it is bad and should reflect the select element's options order. |
Expected behavior
I am trying to resolve this issue: #855
But when I changed HTML: clear and add my custom options and called .sync() nothing is happened.
Steps to reproduce
Additional context
Bug description
https://tom-select.js.org/docs/api/#sync
It does not clear how it works.
The text was updated successfully, but these errors were encountered: