DevTools: Add Product field in timeline event details.

third_party/WebKit/LayoutTests/inspector/tracing/timeline-misc/timeline-event-details-expected.txt

Index: third_party/WebKit/LayoutTests/inspector/tracing/timeline-misc/timeline-event-details-expected.txt
diff --git a/third_party/WebKit/LayoutTests/inspector/tracing/timeline-misc/timeline-event-details-expected.txt b/third_party/WebKit/LayoutTests/inspector/tracing/timeline-misc/timeline-event-details-expected.txt
new file mode 100644
index 0000000000000000000000000000000000000000..30126d623a0578395626bfdd08d597cc2ee4cf89
--- /dev/null
+++ b/third_party/WebKit/LayoutTests/inspector/tracing/timeline-misc/timeline-event-details-expected.txt
@@ -0,0 +1,5 @@
+Checks the details of timeline event nodes.
+
+Script: www.google.com:1337
+Product: Google CDN

[allada, 2017/05/05 01:27:38]

I would rather not ever check a specific product since this list can change at
any point.

Instead lets hijack the ProductRegistry.instance() or something similar to
always resolve something specific.

I am almost in favor of not writing a test yet since I think we should add
something generic for anyone using product registry to get consistent results.

Plus... ProductRegistryImpl is a remote module, meaning it [probably] will never
resolve on bots.

[dgozman, 2017/05/05 05:57:50]

If we don't have something already, let alph@ come up with testing
infrastructure in this patch.
Remote modules should load from local source in layout tests.

[alph, 2017/05/05 21:46:40]

I would like to add a test for it to test the feature is still there.
If the string becomes unstable (which I doubt) we can then update the test to
match any product string.

[alph, 2017/05/05 21:46:40]

I believe it should work as long as network tests for products work.

+