-
Notifications
You must be signed in to change notification settings - Fork 22.9k
Add information about Chrome DevTools extensibility API #41372
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
Merged
wbamberg
merged 4 commits into
mdn:main
from
tunetheweb:document-chromes-extensibility-api
Nov 5, 2025
Merged
Add information about Chrome DevTools extensibility API #41372
wbamberg
merged 4 commits into
mdn:main
from
tunetheweb:document-chromes-extensibility-api
Nov 5, 2025
+204
−9
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
wbamberg
reviewed
Oct 9, 2025
|
Thanks @wbamberg . I've now done this the proper way, rather than trying to wedge it in as a note. |
wbamberg
approved these changes
Nov 5, 2025
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.
Penya1313
reviewed
Nov 6, 2025
|
|
||
| You can optionally supply an argument to label the timestamp, and this label will then be shown alongside the marker. | ||
|
|
||
| Some browsers have further extended this `console.timeStamp()` method to allow additional, optional parameters to be provided as part of its extensibility API that surfaces these in performances traces. See the [Chrome's extensibility API documentation](https://developer.chrome.com/docs/devtools/performance/extension#inject_your_data_with_consoletimestamp) for more information. |
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.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Description
Chrome DevTool's extensibility API extends some standard (and non-standard!) Web APIs with either new additions, or in the use of structured versions of existing fields.
Therefore I think it is helpful for developers who may see these being used in the wild to understand them.
At the same time, as these are non-standard extensions (at least for now!) I don't think it should be documented on MDN other than a small note. I'm also conscious that MDN is not a documentation site for specific browsers, but rather the web platform which is another reason to keep this light. Happy to take feedback on this and iterate if you don't think I've struck the right balance here.
Motivation
A developer approached me confused that the
console.timeStampMDN docs suggested this API did not allow for the extensions Chrome uses.Additionally, with the likes of popular libraries like React and Angular uses the extensibility API, this is becoming a more popular API.
Firefox have also expressed interest to potentially implementing these extensions (at which point we can document this more on MDN as it's more cross-browser).
Additional details
https://developer.chrome.com/docs/devtools/performance/extension
Related issues and pull requests