-
Notifications
You must be signed in to change notification settings - Fork 2k
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
Delete api/DOMHighResTimestamp.json #9892
Conversation
This interface is officially called DOMHighResTimeStamp. Specification: https://www.w3.org/TR/hr-time-2/#dom-domhighrestimestamp Firefox source: https://github.com/mozilla/gecko-dev/blob/master/dom/webidl/Performance.webidl WebKit source: https://github.com/WebKit/WebKit/blob/main/Source/WebCore/page/PerformanceResourceTiming.idl Chromium: https://github.com/chromium/chromium/blob/master/third_party/blink/renderer/core/timing/dom_high_res_time_stamp.idl
This is a curious case. I agree with matching the spec, but I wonder if this should really be in MDN and BCD. This is a typedef (alias) for double, so it's a bit like saying that JS Number is supported, which it was since before the typedef was conceived of. @ddbeck @Elchi3 like mixins and partials this is a spec writer convenience, should we remove it? |
Yeah, not sure types need compat data. It seems similar to what we said about constants: usually, there is no compat story to tell. The MDN page seems worthwhile so that people know what this type is, though. However, it could be a glossary page or something more light. |
Constants are at least visible, But that's all good, if constants were obscure enough to omit then typedefs must be too. I'll file an issue. |
Given discussion above, deleting this file maks more sense. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Thank you! 🎉
This interface is officially called DOMHighResTimeStamp.
Specification:
https://www.w3.org/TR/hr-time-2/#dom-domhighrestimestamp
Firefox source:
https://github.com/mozilla/gecko-dev/blob/master/dom/webidl/Performance.webidl
WebKit source:
https://github.com/WebKit/WebKit/blob/main/Source/WebCore/page/PerformanceResourceTiming.idl
Chromium:
https://github.com/chromium/chromium/blob/master/third_party/blink/renderer/core/timing/dom_high_res_time_stamp.idl
Edit: removed unnecessary reference to another bug.
A checklist to help your pull request get merged faster: