Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix: always use microtasks for nextTick #8450

Merged
merged 2 commits into from
Dec 19, 2018
Merged
Show file tree
Hide file tree
Changes from 1 commit
Commits
File filter

Filter by extension

Filter by extension

Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
Prev Previous commit
Merge branch '2.6' into revert-nexttick
  • Loading branch information
yyx990803 committed Dec 19, 2018
commit 8132002aba49cb3b0a520d3f0f3d54de064eaace
4 changes: 0 additions & 4 deletions src/core/util/next-tick.js
Original file line number Diff line number Diff line change
Expand Up @@ -80,10 +80,6 @@ if (typeof Promise !== 'undefined' && isNative(Promise)) {
}
}

/**
* Wrap a function so that if any code inside triggers state change,
* the changes are queued using a (macro) task instead of a microtask.
*/
export function nextTick (cb?: Function, ctx?: Object) {
let _resolve
callbacks.push(() => {
Expand Down
1 change: 0 additions & 1 deletion src/platforms/web/runtime/modules/events.js
Original file line number Diff line number Diff line change
Expand Up @@ -44,7 +44,6 @@ function add (
capture: boolean,
passive: boolean
) {
if (once) handler = createOnceHandler(handler, event, capture)
target.addEventListener(
event,
handler,
Expand Down
You are viewing a condensed version of this merge commit. You can view the full changes here.