fix double redraw when events fire simultaneously
This commit is contained in:
parent
0354a4e251
commit
ccde633e92
5 changed files with 99 additions and 102 deletions
|
|
@ -1,5 +1,14 @@
|
|||
## Change Log
|
||||
|
||||
[v0.1.18](/mithril/archive/v0.1.19) - maintenance
|
||||
|
||||
### Bug Fixes:
|
||||
|
||||
- fix double redraw when events fire simultaneously
|
||||
- prevent routes from reverting to original route in some cases
|
||||
|
||||
---
|
||||
|
||||
[v0.1.18](/mithril/archive/v0.1.18) - maintenance
|
||||
|
||||
### Bug Fixes:
|
||||
|
|
|
|||
|
|
@ -376,8 +376,6 @@ m.module(document, todo);
|
|||
|
||||
Mithril's auto-redrawing system keeps track of controller stability, and only redraws the view once it detects that the controller has finished running all of its code, including asynchronous AJAX payloads.
|
||||
|
||||
Also note that this mechanism itself is not asynchronous if it doesn't need to be: Mithril does not need to wait for the next browser repaint frame to redraw - it doesn't even need to wait for the document ready event on the first redraw - it will redraw immediately upon script completion, if able to.
|
||||
|
||||
---
|
||||
|
||||
### Summary
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue