docs: remove nonexistent contentTracing methods #16597
Merged
Conversation
This file contains 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
deepak1556
approved these changes
Jan 30, 2019
There was a problem hiding this comment.
LGTM, they were removed as a part of chrome 49 upgrade 5fae63a#diff-8157f19cbc1d460700f2c2c39acfa83b
miniak
approved these changes
Jan 30, 2019
ckerr
approved these changes
Jan 30, 2019
|
Release Notes Persisted
|
|
I have automatically backported this PR to "5-0-x", please check out #16614 |
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 of Change
Remove
contentTracingmethods that mysteriously appear to never have actually existed 馃懡cc @MarshallOfSound @BinaryMuse
Checklist
npm testpassesRelease Notes
Notes: Removed
contentTracingmethods which were never actually implemented.