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
Not sure, but my application would find it useful.
What version of plugin are you interested in using
n/a
Additional context
Long Tasks are tasks in the browser that take longer than 50ms. These tasks will cause slowdowns in general interactivity of the application, TTI, and animations as they occur on the UI thread. The Long Task API has been spec'd for some time now and is supported in Chromium-based browsers presently.
I would find it useful for these to automatically traced to help find areas of the application that are definitively degrading interactivity. I would be curious to know what child operations happening within a long task span, in addition to knowing where/when the longtasks are happening most frequently.
Is there a reference you could point for the well-defined lifecycle methods**
Long Tasks can be observed with the PerformanceObserver using the longtask entryType.
The text was updated successfully, but these errors were encountered:
Is it applicable for Node or Browser or both
Browser
Do you expect this plugin to be commonly used
Not sure, but my application would find it useful.
What version of plugin are you interested in using
n/a
Additional context
Long Tasks are tasks in the browser that take longer than 50ms. These tasks will cause slowdowns in general interactivity of the application, TTI, and animations as they occur on the UI thread. The Long Task API has been spec'd for some time now and is supported in Chromium-based browsers presently.
I would find it useful for these to automatically traced to help find areas of the application that are definitively degrading interactivity. I would be curious to know what child operations happening within a long task span, in addition to knowing where/when the longtasks are happening most frequently.
Is there a reference you could point for the well-defined lifecycle methods**
Long Tasks can be observed with the
PerformanceObserver
using thelongtask
entryType.The text was updated successfully, but these errors were encountered: