Closed nathanbowser closed 9 years ago
process.nextTick returns undefined for most browsers, but for IE10+ which use setImmediate, it returns the immediateId, which can lead to problems. This makes the api consistent.
process.nextTick
setImmediate
I think this is made irrelevant by https://github.com/defunctzombie/node-process/commit/62acf3e9e9c2e40d22465f1db309bb82ae7fda91 Let me know if that is not the case.
process.nextTick
returns undefined for most browsers, but for IE10+ which usesetImmediate
, it returns the immediateId, which can lead to problems. This makes the api consistent.