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
It will prevent the UI from blocking and should feel faster.
Also, we should start processing the paste before the page rendering (as soon as we got the paste data available), and send events to update the progress bar. The main thread, when dom is ready, will hook on those events and be avaible to udate the css class accordingly.
The text was updated successfully, but these errors were encountered:
It will prevent the UI from blocking and should feel faster.
Also, we should start processing the paste before the page rendering (as
soon as we got the paste data available), and send events to update the
progress bar. The main thread, when dom is ready, will hook on those events
and be avaible to udate the css class accordingly.
—
Reply to this email directly or view it on GitHubhttps://github.com//issues/50
.
It will prevent the UI from blocking and should feel faster.
Also, we should start processing the paste before the page rendering
(as
soon as we got the paste data available), and send events to update the
progress bar. The main thread, when dom is ready, will hook on those
events
and be avaible to udate the css class accordingly.
—
Reply to this email directly or view it on
GitHubhttps://github.com//issues/50
.
—
Reply to this email directly or view it on GitHub #50 (comment).
It will prevent the UI from blocking and should feel faster.
Also, we should start processing the paste before the page rendering (as soon as we got the paste data available), and send events to update the progress bar. The main thread, when dom is ready, will hook on those events and be avaible to udate the css class accordingly.
The text was updated successfully, but these errors were encountered: