-
Notifications
You must be signed in to change notification settings - Fork 26
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
The common atttribute of PerformanceEntry
should be initialized rat…
#210
Conversation
…her than inherited Other specs should initialize startTime/entry/name/endTime rather than provide overrides for them.
@clelland care to review? |
index.html
Outdated
|
||
<ol> | ||
<li>Assert: <var>entryType</var> is defined in the <a href="https://w3c.github.io/timing-entrytypes-registry/#registry">entry type registry</a>. | ||
<li>Set <var>entry</var>'s <a>startTime</a> to <var>startTime</var>. |
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.
Done
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.
Oops, accidentally deleted that comment; didn't realize it had already been sent. The general idea I wanted to suggest was that we may want to make a general distinction in specs between a one-time 'initialization" vs a maybe-repeatable "set" operation. I don't know if this happens anywhere else, aside from the "initial values" we give to some properties.
Anyway, this LGTM, thanks!
…her than inherited
Other specs should initialize startTime/entry/name/endTime rather than provide overrides for them.
💥 Error: 502 Bad Gateway 💥
PR Preview failed to build. (Last tried on Feb 2, 2024, 2:45 PM UTC).
More
PR Preview relies on a number of web services to run. There seems to be an issue with the following one:
🚨 Spec Generator - Spec Generator is the web service used to build specs that rely on ReSpec.
🔗 Related URL
If you don't have enough information above to solve the error by yourself (or to understand to which web service the error is related to, if any), please file an issue.