DevTools Elements tab #776
Merged
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
expose dom domain functions to communicate with the inspector frontend
…g through the inspector frontend
|
💔 |
|
run ci |
|
💚 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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.
Implement the DOM and CSS agents to display debug information in the Chrome DevTools.
Supported features (ticked boxes):
The implementation is such that the inspector backend requests information and the runtime calls to tns-core-modules callbacks to fetch the necessary visual tree information and the computed styles per view.
Relies on tns-core-modules 3.1 to provide the agreed-upon callbacks for seamless communication and to work properly. In case the DevTools Elements-enabled runtime is used with tns-core-modules prior to the version supporting elements tab, the visual tree will not be shown.
Considerations: