No more interference from chrome-extensions that utilize postmessages #4
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
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.
Hi
I've modified the extension a bit to check if the postmessages are coming from chrome-extensions or not. I'm having Wappalyzer installed and it was interfering with the postmessage extension. This resulted in having arround 5-6 extra logs and stack traces included in every webpage I requested.
One thing remained unsolved, and that is the little popup that counts all the postmessages it has found from an origin. I'm unsure how to let it only count the ones that are actually included in the extension's popup.
I thought that this might be helpful to someone else, reason why I'm creating a PR.