Chromium Code Reviews
chromiumcodereview-hr@appspot.gserviceaccount.com (chromiumcodereview-hr) | Please choose your nickname with Settings | Help | Chromium Project | Gerrit Changes | Sign out
(75)

Unified Diff: third_party/WebKit/Source/core/timing/PerformanceBase.cpp

Issue 2610063006: Create TaskAttributionTiming PerformanceEntry for attribution in PerformanceLongTaskTiming. Move cu… (Closed)
Patch Set: update copyright year Created 3 years, 11 months ago
Use n/p to move between diff chunks; N/P to move between comments. Draft comments are only viewable by you.
Jump to:
View side-by-side diff with in-line comments
Download patch
Index: third_party/WebKit/Source/core/timing/PerformanceBase.cpp
diff --git a/third_party/WebKit/Source/core/timing/PerformanceBase.cpp b/third_party/WebKit/Source/core/timing/PerformanceBase.cpp
index aa49b288243b451cf35a4f9024895baed6f96337..75089a33697c37905e1fd8b3aaf7b254f5e9bdfb 100644
--- a/third_party/WebKit/Source/core/timing/PerformanceBase.cpp
+++ b/third_party/WebKit/Source/core/timing/PerformanceBase.cpp
@@ -135,9 +135,12 @@ PerformanceEntryVector PerformanceBase::getEntriesByType(
switch (type) {
case PerformanceEntry::Invalid:
return entries;
+ // Unsupported for LongTask, TaskAttribution.
+ // Per the spec, these entries can only be accessed via
+ // Performance Observer. No separate buffer is maintained.
case PerformanceEntry::LongTask:
tdresser 2017/01/05 13:34:14 I'd be tempted to stick these cases at the bottom
panicker 2017/01/05 20:56:49 Done.
- // Unsupported for LongTask. Per the spec, Long task entries can only be
- // accessed via Performance Observer. No separate buffer is maintained.
+ return entries;
+ case PerformanceEntry::TaskAttribution:
return entries;
case PerformanceEntry::Resource:
for (const auto& resource : m_resourceTimingBuffer)

Powered by Google App Engine
This is Rietveld 408576698