Range Slider onchange event doesn't trigger.
See original GitHub issueThis is a
-
bug
-
Framework7 Version: 1.5
-
Platform and Target: iOS 9.3.5
Range Slider onchange event doesn’t trigger after init a Framework7 app.
<!DOCTYPE html>
<html>
<head></head>
<body>
<input type="range" onchange="alert('huhu')">
</body>
<script src="lib/framework7.js"></script>
<script>
var app = new Framework7();
</script>
</html>
Issue Analytics
- State:
- Created 7 years ago
- Comments:5 (1 by maintainers)
Top Results From Across the Web
onchange event on input type=range is not triggering in ...
I was having issues with the 'change' event not firing in mobile chrome (v34), but adding 'input' into the equation has fixed it...
Read more >How to trigger onchange event on input type=range while ...
Onchange : Onchange executes a JavaScript when a user changes the state of a select element. This attribute occurs only when the element ......
Read more >onChange event doesn't trigger when direclty clicking on the ...
When you directly after the loading choose the maximum value on the input type range, the event isn't fire with an onChange. The...
Read more >onchange vs. oninput for Range Sliders - Impressive Webs
The change event does not fire immediately, demonstrated by the fact that the value on the page does not change until the slider...
Read more >Setting a slider's value without triggering the change event
To me this is exactly why we have event and event.originalEvent. The slidechange event should fire anytime the slider value changes (not only...
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 FreeTop 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
Top GitHub Comments
Look like there is defiantly an issue here
This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.