Skip to content

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.

Sign up for GitHub

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

Clear current search query, filters, and sorts
50 Open 163 Closed
50 Open 163 Closed
Author
Filter by author
Loading
Label
Filter by label
Loading
Use alt + click/return to exclude labels
or ⇧ + click/return for logical OR
Projects
Filter by project
Loading
Milestones
Filter by milestone
Loading
Assignee
Filter by who’s assigned
Sort
Sort by
Newest Oldest Most commented Least commented Recently updated Least recently updated Best match
Most reactions
👍 👎 😄 🎉 😕 ❤️ 🚀 👀

Issues list

Collect initiatorType use-cases
#132 opened Dec 15, 2017 by nicjansma updated Mar 12, 2018 Level 3
2
Register TAO as Permanent Message Header Field Name w3c
#198 opened Jan 15, 2019 by plehegar updated Jan 15, 2019 Level 2
@plehegar
Critical path length? enhancement
#149 opened Mar 17, 2018 by lencioni updated Mar 13, 2019 Level 3
2
Resource processing time enhancement
#133 opened Dec 18, 2017 by yoavweiss updated Mar 13, 2019 Level 3
5
Add information about local cache performance enhancement whiteboard
#76 opened Nov 9, 2016 by bmaurer updated Mar 13, 2019 Level 3
6
For all resources, add timestamp of when it was available to the browser enhancement
#60 opened Jun 24, 2016 by bluesmoon updated Mar 13, 2019 Level 3
3
Improve "initiator" reporting enhancement
#8 opened Feb 16, 2015 by vayam updated Mar 13, 2019 Level 3
1
12
Make TAO a subset of CORS enhancement requires Fetch integration
#178 opened Nov 13, 2018 by yoavweiss updated Mar 13, 2019 Level 3
5
Expose JavaScript code caching information in PerformanceResourceTiming enhancement whiteboard
#190 opened Jan 2, 2019 by mathiasbynens updated Jan 29, 2020 Level 3
7
Proposal: API for exposing resource requests enhancement
#137 opened Jan 10, 2018 by npm1 updated Nov 2, 2020 Level 3
18
Allow semi-wildcard Timing-Allow-Origin values (for subdomains) enhancement
#175 opened Oct 24, 2018 by jakub-g updated Nov 2, 2020 Level 3
2
consider adding attributes to track Cache API performance in a service worker FetchEvent handler enhancement
#162 opened Aug 16, 2018 by wanderview updated Nov 2, 2020 Level 3
6
Access to the Remote Address information enhancement
#180 opened Nov 28, 2018 by gui-poa updated Nov 2, 2020 Level 3
4
Resource initiator information to enable creation of dependency trees enhancement
#263 opened Apr 1, 2021 by yoavweiss updated May 22, 2021
2
Expose the TLS certificate + other TLS parameters for a resource enhancement whiteboard
#75 opened Nov 8, 2016 by bmaurer updated Jun 21, 2021 Level 3
Add fields for identifying the security protocol, cipher, signature and so on enhancement whiteboard
#74 opened Nov 8, 2016 by phistuck updated Jun 21, 2021 Level 3
22
Rationalize Resource-Timing opt-ins with CORS/CORP enhancement
#240 opened Dec 10, 2020 by yoavweiss updated Jun 23, 2021
5
Consider removing wildcard option of the Timing-Allow-Origin header to prevent accidental application state leakage privacy-needs-resolution Issue the Privacy Group has raised and looks for a response on.
#223 opened Feb 5, 2020 by kdzwinel updated Jul 1, 2021
2
Clean up cross references/versioning
#271 opened Apr 21, 2021 by annevk updated Sep 7, 2021
@marcoscaceres @caribouW3
7
Would like a precise way to map PerformanceTimings to FetchEvent enhancement
#259 opened Aug 8, 2017 by jakearchibald updated Sep 29, 2021
13
initiatorType for favicon
#298 opened Oct 3, 2021 by noamr updated Nov 30, 2021
6
initiatorType definition doesn't define initiator in multiple element scenarios Clarification whiteboard
#54 opened May 23, 2016 by yoavweiss updated Apr 11, 2022 Level 3
@yoavweiss
10
Reflect preload information (in ResourceTiming?) enhancement
#303 opened Oct 26, 2021 by noamr updated Apr 14, 2022
23
InitiatorType should not single out XHR Clarification
#142 opened Jan 24, 2018 by yoavweiss updated Apr 19, 2022 Level 3
14
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 updated Apr 29, 2022
11
ProTip! Add no:assignee to see everything that’s not assigned.