For documentation tooling this means that there are now distinct startTime, duration, name, entryType properties for the PerformanceLongTaskTiming, TaskAttributionTiming, PerformanceLongAnimationFrameTiming, PerformanceScriptTiming interfaces. Previously these were just documented with the PerformanceEntry interface once for all.
It seems that no other Performance spec does this. So, for our tooling it means that LargestContentfulPaint, LayoutShift, PerformanceElementTiming, PerformanceEventTiming, PerformanceMark, PerformanceMeasure, PerformancePaintTiming, etc. etc. can all refer to PerformanceEntry for these properties as they are not appearing as "overloading" in their IDLs again. That seems inconsistent with what this spec is doing as of https://github.com/w3c/longtasks/commit/61a67ee58896d6e6da4281db6cbb17e9ac38eecc. Maybe I'm missing something, though.
Why is this specification overloading PerformanceEntry in the IDL? E.g.:
For documentation tooling this means that there are now distinct
startTime
,duration
,name
,entryType
properties for thePerformanceLongTaskTiming
,TaskAttributionTiming
,PerformanceLongAnimationFrameTiming
,PerformanceScriptTiming
interfaces. Previously these were just documented with thePerformanceEntry
interface once for all.It seems that no other Performance spec does this. So, for our tooling it means that
LargestContentfulPaint
,LayoutShift
,PerformanceElementTiming
,PerformanceEventTiming
,PerformanceMark
,PerformanceMeasure
,PerformancePaintTiming
, etc. etc. can all refer toPerformanceEntry
for these properties as they are not appearing as "overloading" in their IDLs again. That seems inconsistent with what this spec is doing as of https://github.com/w3c/longtasks/commit/61a67ee58896d6e6da4281db6cbb17e9ac38eecc. Maybe I'm missing something, though.