Comments (4)
igrigorik
commented on July 17, 2024
Duplicate of #12 - please see that thread.
from resource-timing.
vaibhavtripathi
commented on July 17, 2024
@igrigorik Can you elaborate on how this issue is a duplicate of #12? As far as I could understand, #12 does specify what resources should be a part of the resource timing entires but I could not see sufficient markers by which a developer can distinguish between resources that succeeded and those that failed. If that is the case, this issue seems to be a bit different from what is discussed in #12. @nicjansma's comment "There should probably also be a new field on the PerformanceResourceTiming interface to indicate that it is a failure (and possibly, some classification on why)." is more relevant to this but I do not see any follow ups on that.
from resource-timing.
igrigorik
commented on July 17, 2024
@vaibhavtripathi see #12 (comment). There is still a discussion to be had about additional status codes.. and we should open a new issue for that.
(and if we're willing to go down this path)
from resource-timing.
vaibhavtripathi
commented on July 17, 2024
@igrigorik Thanks a lot. I had missed that particular comment for some reason.
from resource-timing.
Related Issues (20)
- User Agent may want to restrict cross-origin transferSize/encodedBodySize/decodedBodySize visibility even with TAO HOT 2
- Consider adding finalResponseHeaders{Start|End} times HOT 30
- InitiatorType for module scripts HOT 2
- Failed deploy HOT 3
- Specify the behaviors of requestStart and responseStart for Prefetch HOT 3
- Cache and Proxy information
- How to get correct connectStart/End, domainLookupStart/End value when service worker is enabled? HOT 8
- List of initiatorType types HOT 2
- Why is there noticeable gap between requestStart and connectEnd? HOT 1
- Should the spec mention "Queue entry" at somepoint? HOT 3
- Capturing basic auth credentials in URLs, part 2 HOT 1
- Test infrastructure to expose whether a browser intends to expose transferSize across origins with TAO HOT 10
- Adding HTTP method to ResourceTiming API structure HOT 5
- Adding resource discovery time to ResourceTiming API structure HOT 3
- Broken references in Resource Timing
- sendBeacon() integration HOT 4
- Resource Initiator Information Reporting HOT 2
- Expose Content-Encoding to ResourceTiming HOT 4
- Should `firstInterimResponseStart` show 0 when there is no interim response? HOT 3
- Should data: urls be reported in resource timing? HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
D3
Bring data to life with SVG, Canvas and HTML. 📊📈🎉
-
Recommend Topics
-
javascript
JavaScript (JS) is a lightweight interpreted programming language with first-class functions.
-
web
Some thing interesting about web. New door for the world.
-
server
A server is a program made to process requests and deliver data to clients.
-
Machine learning
Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from resource-timing.