Twiddle text node to trigger ASAP flush

[josh]

Some buggy MutationObserver implementations or polyfills may not trigger a mutation when an attribute is just set again to the same value.

This text node twiddle approach is based on Polymer's microtask.js.

Fixes #170

Related

• ASAP flush is broken with polyfilled MutationObserver #170
• Change asap mutation observer implementation to touch text node stefanpenner/es6-promise#2

/cc @jakearchibald @azakus

[stefanpenner]

This seems reasonable, but I want to understand if this is a bug in those polyfils or a fundamental limitation. I suspect a limitation.

I don't see any downside to this change, but as this scenario may not be entirely obvious a small inline comment would be appreciated.

[josh]

This seems reasonable, but I want to understand if this is a bug in those polyfils or a fundamental limitation. I suspect a limitation.

For DOMAttrModified at least, its not fired if the attribute is the same. Though there maybe other ways of detecting via onpropchange. I'm not an expert in the MutationObserver polyfill domain.

We could keep the setAttribute if you'd like and set it to an incremented value. But the text node approach was suggested to me by @azakus.

[stefanpenner]

@josh seems good, lets give it a try :)

[josh]

Rad.

Hoping to have github.com running the Promises polyfill by the end of the week.

[stefanpenner]

nice!

[stefanpenner]

@josh although not general purpose yet, you might want to checkout our WIP promise tooling: emberjs/ember-inspector#76