You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
you have to test the demo on Mozilla and chrome by simply clicking the update button
What is expected?
expected the value to be updated before the confirm dialog fires
What is actually happening?
$nextTick still executes before the window.confirm dialog interrupts the DOM update on chrome but not on mozilla
The text was updated successfully, but these errors were encountered:
Abassion
changed the title
$nextTick still executes before the window.confirm dialog interrupts the DOM update on chrome but not on mozilla
$nextTick still executes before the window.confirm interrupts the DOM update on chrome but not on mozilla
Aug 26, 2019
The browser rendering the DOM vs rendering messages and blocking the rendering thread is something we cannot control. We can only ensure the DOM is updated, that's when nextTick triggers, you can use a console.log to check it. To ensure the view is also updated, use this
this.$nextTick(()=>{console.log(document.getElementById('app').textContent)requestAnimationFrame(()=>{confirm('if you are using chrome notice that the value is not updated only after you resolve the dialog')})})
Version
2.6.10
Reproduction link
https://codepen.io/Dadboz/pen/vYBxerr
Steps to reproduce
you have to test the demo on Mozilla and chrome by simply clicking the update button
What is expected?
expected the value to be updated before the confirm dialog fires
What is actually happening?
$nextTick still executes before the window.confirm dialog interrupts the DOM update on chrome but not on mozilla
The text was updated successfully, but these errors were encountered: