Stuck on an issue?
Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.
And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.
Destroy doesn't put original select back
See original GitHub issueScenario I have a normal select box with class ‘searchable’ and normal html options (no ajax).
a choices instance is created:
choices = new Choices('select.searchable')
I destroy the choices instance
choices.destroy()
NOW, the Docs say that my select tag should be back to its original state.
HOWEVER instead, the select box is left blank (i.e no options in list)
Issue Analytics
- State:
- Created 6 years ago
- Comments:14
Top Results From Across the Web
Bootstrap select destroy removes the original select from DOM
Found the solution, I edit the plugin function destroy where instead of removing the original element, I show it back:
Read more >UnityEngine.Object.Destroy not deleting GameObject
I have a gameObject that is a placeholder for all the other gameObjects in a level. When I want to unload the level...
Read more >instance.destroy(...) does not return any information if rows ...
using Sequelize 3.3.2 var user = User.build({ id: 1 }, { isNewRecord: false }) user.destroy() .then(function(){ console.log(arguments) } ...
Read more >Scripting API: Object.DontDestroyOnLoad - Unity - Manual
To implement this example, create two new Scenes, named scene1 and scene2 . Open scene1 and add the SceneSwap.cs script to an empty...
Read more >Force Component Destroy by Using Page Life Cycle in ...
This is great for performance since the framework doesn't have to work as hard to recreate the components that you might return to....
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
This has been fixed on the
developbranch and will go out in the next release 👍This seems to be an issue in 6.0.3, see updated example: https://jsfiddle.net/pco03evt/
Should this be re-opened?