Created attachment 460738 [details] Safeframe embedded page Cross-origin iFrames with Timing-Allow-Origin: * are not generating an PerformanceTimingEntry when the iframe comes from cache. The code on https://jsbin.com/veyidigudi loads a safeframe and then adds the performance entry in a textNode after it. The first time you load it, there will be an entry but when you refresh the page the timing entry goes away. Clearing cache and refreshing brings the timing entry back until you refresh for the 4rd time (and it comes from cache again).
<rdar://problem/97019263>
This is still an issue in Safari 16. Any update on this? Chrome 109 and Firefox 109 both have a entry present even when the iframe comes from cache.
In WebKit ToT (280460@main) - it shows: [ { "name": "https://tpc.googlesyndication.com/safeframe/1-0-37/html/container.html", "entryType": "resource", "startTime": 619, "duration": 61, "initiatorType": "iframe", "nextHopProtocol": "h2", "workerStart": 0, "redirectStart": 0, "redirectEnd": 0, "fetchStart": 619, "domainLookupStart": 620, "domainLookupEnd": 621, "connectStart": 622, "connectEnd": 654, "secureConnectionStart": 633, "requestStart": 654, "responseStart": 677, "responseEnd": 680, "transferSize": 0, "encodedBodySize": 0, "decodedBodySize": 0, "serverTiming": [] } ] So I think it might have been fixed recently since even STP197 is broken. @Youenn - something you fixed recently? https://github.com/WebKit/WebKit/commit/6a2c5a3042534caf2df6952d1d7d151d3e3c76bc