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
github-actions
bot
added
the
data:api
|
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. |
bershanskiy
changed the title
|
Given discussion above, deleting this file maks more sense. |
5 participants
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: