1. Enforce receiver checks on IDL interfaces. 2. Avoid prototype manipulation on constructing IDL interfaces with `ReflectConstruct`. 3. `defineReplaceableAttribute` should create IDL getter/setter. 4. Corrected `PerformanceResourceTiming` to inherit the public interface `PerformanceEntry` instead of the internal interface `InternalPerformanceResourceTiming`. 5. `detail` is not a specified attribute on `PerfomanceEntry`. Node.js specific extensions are moved to a subclass of `PerformanceEntry` as `PerformanceNodeEntry`. PR-URL: https://github.com/nodejs/node/pull/44483 Reviewed-By: Antoine du Hamel <duhamelantoine1995@gmail.com> Reviewed-By: Minwoo Jung <nodecorelab@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>
24 lines
1.2 KiB
HTML
24 lines
1.2 KiB
HTML
<!DOCTYPE html>
|
|
<html>
|
|
<head>
|
|
<meta charset="UTF-8" />
|
|
<title>window.performance Resource Timing Entries exist</title>
|
|
<link rel="author" title="Microsoft" href="http://www.microsoft.com/" />
|
|
<link rel="help" href="https://w3c.github.io/web-performance/specs/ResourceTiming/Overview.html"/>
|
|
<script src="/resources/testharness.js"></script>
|
|
<script src="/resources/testharnessreport.js"></script>
|
|
<script src="test_resource_timing.js"></script>
|
|
</head>
|
|
<body>
|
|
<h1>Description</h1>
|
|
<p>
|
|
NOTE: Due to caching behavior in the browser, it is possible that when revisiting this page, some resources
|
|
may not have to be fetched from the network. As a result, the performance timeline will not contain entries
|
|
for these resources. This test will fail if any entries are missing to ensure that all resources are fetched
|
|
from the network and entries for these resources exist in the Performance Timeline. If revisiting this page,
|
|
please either perform a full reload of the page or clear the cache between visits.
|
|
</p>
|
|
|
|
<div id="log"></div>
|
|
</body>
|
|
</html>
|