[whatwg/fetch] worker timing doesn't need to be TAO protected for subresources (Issue #1597)

The current implementation in chrome TAO-protects worker timing information only for navigations (iframes, objects).
This makes sense because worker timing is anyway exposed to the origin of the service worker which is in the same origin as its document. 

-- 
Reply to this email directly or view it on GitHub:
https://github.com/whatwg/fetch/issues/1597
You are receiving this because you are subscribed to this thread.

Message ID: <whatwg/fetch/issues/1597@github.com>