-
Notifications
You must be signed in to change notification settings - Fork 35
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
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
Add service worker static routing API information to resource timing
#389
opened May 16, 2024 by
sisidovski
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
Expose Content-Encoding to ResourceTiming
enhancement
fetch-integration
requires Fetch integration
#381
opened Sep 16, 2023 by
nicjansma
Would like a precise way to map PerformanceTimings to FetchEvent
enhancement
#259
opened Aug 8, 2017 by
jakearchibald
Previous Next
ProTip!
Updated in the last three days: updated:>2024-07-31.