Separate Promise implementation from polyfilling
This commit is contained in:
parent
1410e35456
commit
d283b24337
6 changed files with 110 additions and 95 deletions
|
|
@ -47,6 +47,13 @@
|
|||
|
||||
---
|
||||
|
||||
### v1.1.7
|
||||
|
||||
- Promise polyfill implementation separated from polyfilling logic.
|
||||
- `PromisePolyfill` is now available on the exported/global `m`.
|
||||
|
||||
---
|
||||
|
||||
### v1.1.6
|
||||
|
||||
- core: render() function can no longer prevent from changing `document.activeElement` in lifecycle hooks ([#1988](https://github.com/MithrilJS/mithril.js/pull/1988), [@purplecode](https://github.com/purplecode))
|
||||
|
|
|
|||
|
|
@ -26,6 +26,8 @@ A [ES6 Promise](https://developer.mozilla.org/en/docs/Web/JavaScript/Reference/G
|
|||
|
||||
A Promise is a mechanism for working with asynchronous computations.
|
||||
|
||||
Mithril provides a polyfill when the environment does not support Promises. The polyfill can also be referenced specifically via `m.PromisePolyfill`.
|
||||
|
||||
---
|
||||
|
||||
### Signature
|
||||
|
|
|
|||
Loading…
Add table
Add a link
Reference in a new issue