Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
An attempt to de-clusterfy .listen,
while still allowing editing of input fields when(isActive)
but allowing setValue to cause updateDisplay, so events like keyboard events will work...
updateDisplay(force)
: skips active check (note force is false during the .___listening loop)otherwise runs active check and doesnt update if dom.isActive(element)
fixes listen, while allowing editing, allows drag events, and re-added key up/down (which were blocked if checking isActive but not force)
isactive problems: fixes #206, fixes #179
keyboard: fixes #195, (which isactive checks block without upateDisplay(force) option)
possible related, but am confus:
#95: this is true. onChange is fired by setValue, onFInishChange only after slider/mouse event
#212: I don't follow this, though it seems related... a code example might help. I suspect he could updateDisplay(true) after whatever he's doing
withdrawing head from code in 3... 2.... 1....