-
Notifications
You must be signed in to change notification settings - Fork 36
Issues: w3c/resource-timing
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Add service worker static routing API information to resource timing
#389
opened May 16, 2024 by
sisidovski
Expose Content-Encoding to ResourceTiming
enhancement
fetch-integration
requires Fetch integration
#381
opened Sep 16, 2023 by
nicjansma
Adding resource discovery time to ResourceTiming API structure
enhancement
#374
opened Mar 31, 2023 by
giacomozecchini
Adding HTTP method to ResourceTiming API structure
enhancement
#373
opened Mar 22, 2023 by
sohomdatta1
Why is there noticeable gap between requestStart and connectEnd?
#365
opened Dec 15, 2022 by
xiaofud
How to get correct connectStart/End, domainLookupStart/End value when service worker is enabled?
#363
opened Nov 23, 2022 by
xiaofud
Specify the behaviors of requestStart and responseStart for Prefetch
#360
opened Nov 10, 2022 by
liuwilliam-gh
Resource initiator information to enable creation of dependency trees
enhancement
#263
opened Apr 1, 2021 by
yoavweiss
Rationalize Resource-Timing opt-ins with CORS/CORP
enhancement
#240
opened Dec 10, 2020 by
yoavweiss
Consider removing wildcard option of the Issue the Privacy Group has raised and looks for a response on.
Timing-Allow-Origin
header to prevent accidental application state leakage
privacy-needs-resolution
#223
opened Feb 5, 2020 by
kdzwinel
Consider removing wildcard option of the Issue the Privacy Group has raised and looks for a response on.
Timing-Allow-Origin
header to prevent browser history leakage
privacy-needs-resolution
#222
opened Feb 5, 2020 by
kdzwinel
Consider removing nextHopProtocol as it may expose whether visitor is using VPN / proxy
privacy-needs-resolution
Issue the Privacy Group has raised and looks for a response on.
#221
opened Feb 5, 2020 by
kdzwinel
Previous Next
ProTip!
Exclude everything labeled
bug
with -label:bug.