Skip to content

Commit 41d9808

Browse files
authored
Add content-type to resource-timing (#341)
* Add content-type to resource-timing * Move content-type into response body info * Mention possibility of truncating by user agents * Add link to user agent * Remove stripping * Serialize instead of returning essence * Return minimzed content type received from fetch
1 parent d369e1f commit 41d9808

File tree

1 file changed

+6
-0
lines changed

1 file changed

+6
-0
lines changed

‎index.html

Lines changed: 6 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -375,6 +375,7 @@ <h3>
375375
readonly attribute unsigned long long decodedBodySize;
376376
readonly attribute unsigned short responseStatus;
377377
readonly attribute RenderBlockingStatusType renderBlockingStatus;
378+
readonly attribute DOMString contentType;
378379
[Default] object toJSON();
379380
};
380381
</pre>
@@ -757,6 +758,11 @@ <h3>
757758
"FETCH#concept-filtered-response-opaque">opaque filtered
758759
response</a>.
759760
</p>
761+
<p data-dfn-for="PerformanceResourceTiming">
762+
The <dfn>contentType</dfn> getter steps are to return
763+
<a>this</a>'s <a data-for="PerformanceResourceTiming">resource
764+
info</a>'s [=response body info/content type=].
765+
</p>
760766
<p data-dfn-for="PerformanceResourceTiming">
761767
The <dfn>renderBlockingStatus</dfn> getter steps are to return
762768
<a data-link-for="RenderBlockingStatusType">blocking</a> if

0 commit comments

Comments
 (0)