Why is this specification overloading PerformanceEntry in the IDL? E.g.:
interface PerformanceLongTaskTiming : PerformanceEntry {
/* Overloading PerformanceEntry */
readonly attribute DOMHighResTimeStamp startTime;
readonly attribute DOMHighResTimeStamp duration;
readonly attribute DOMString name;
readonly attribute DOMString entryType;
}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 61a67ee. 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,entryTypeproperties for thePerformanceLongTaskTiming,TaskAttributionTiming,PerformanceLongAnimationFrameTiming,PerformanceScriptTiminginterfaces. Previously these were just documented with thePerformanceEntryinterface 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 toPerformanceEntryfor these properties as they are not appearing as "overloading" in their IDLs again. That seems inconsistent with what this spec is doing as of 61a67ee. Maybe I'm missing something, though.