postMessage getting spammed from developer tools when turned off in non-react site

[ericthomson13]

I get an error at interval for cross origin issues with unrecognized domains. I'm on a non-react site and react-developer-tools plugin is supposedly not in use but uninstalling the plugin resolved the issue. This is from a consistent message being posted that the data is hello: true

This makes it hard to debug other applications and I don't understand why this would be turned off and spamming the browser with messages.

[hoxyq]

I assume you are referring to the React DevTools browser extension? Can you please share which browser and version you are using, and also version of the extension?

Do I understand correctly that the main issue with this is frequent window.postMessage calls, which makes it harder for you to debug your app? Can you filter these calls from react-devtools based on source?
For some context, this is by design, it is a simple polling, because we don't know when React can be loaded on the page.

[ericthomson13]

Sorry yes browser extension. I am unsure of the extension version as I had to delete it to mitigate the issue. Windows machine running Chrome 118.0.5993.71 Message in the postMessage payload is hello: true if that's of any assistance. I'm running the postMessage developer tools which is how I came across that message as that postMessage tool is helping me troubleshoot other issues in current development. Thanks!

…

On Tue, Oct 17, 2023 at 8:28 AM Ruslan Lesiutin ***@***.***> wrote: I assume you are referring to the React DevTools browser extension? Can you please share which browser and version you are using, and also version of the extension? — Reply to this email directly, view it on GitHub <#27529 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ANVX72TJAKVCMUAFS3NWPLDX72I2RAVCNFSM6AAAAAA6CURAIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRWGUZTMNZVGA> . You are receiving this because you authored the thread.Message ID: ***@***.***>

-- "Get out and enjoy the magical planet. What the hell. Get out there and live." --Jim Whittaker

[hoxyq]

Sorry yes browser extension. I am unsure of the extension version as I had to delete it to mitigate the issue. Windows machine running Chrome 118.0.5993.71 Message in the postMessage payload is hello: true if that's of any assistance. I'm running the postMessage developer tools which is how I came across that message as that postMessage tool is helping me troubleshoot other issues in current development. Thanks!
…
On Tue, Oct 17, 2023 at 8:28 AM Ruslan Lesiutin @.> wrote: I assume you are referring to the React DevTools browser extension? Can you please share which browser and version you are using, and also version of the extension? — Reply to this email directly, view it on GitHub <#27529 (comment)>, or unsubscribe https://github.com/notifications/unsubscribe-auth/ANVX72TJAKVCMUAFS3NWPLDX72I2RAVCNFSM6AAAAAA6CURAIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMYTONRWGUZTMNZVGA . You are receiving this because you authored the thread.Message ID: @.>
-- "Get out and enjoy the magical planet. What the hell. Get out there and live." --Jim Whittaker

As I've mentioned in my previous comment, this behaviour is expected. I understand that this can make it harder for you to debug window.postMessage calls, but you should try filtering them based on source.

[anoteboom]

@ericthomson13 Thank you for finding this. Our application was severly crippled because of this issue. We have a 'sign in button' that opens a popup, and waits for a 'postmessage' to close that popup window again.
And because the devtools keep sending postmessages, we immediately closed the popup without the user able to complete their login. The issue you logged here allowed me to find this cause.
We already checked the origin of the postmessage, and just adding a check on the payload as well fixed our problem.

I still think it is very strange that a devtools plugin shows this as default behavior on all websites the user visits.

[ericthomson13]

@anoteboom we've been using postMessage developer tools for logging and debugging and the react dev tools constant postMessage interval spamming that and it doesn't have a filter. Since @hoxyq has stated that this is their intent I'm working towards opening a PR with the developer tools we're using to allow for an input to filter the postMessages https://github.com/alxHenry/chrome-postMessage-dev-tools/tree/master

[sanmont3drepo]

@ericthomson13 Thank you for finding this. Our application was severly crippled because of this issue. We have a 'sign in button' that opens a popup, and waits for a 'postmessage' to close that popup window again. And because the devtools keep sending postmessages, we immediately closed the popup without the user able to complete their login. The issue you logged here allowed me to find this cause. We already checked the origin of the postmessage, and just adding a check on the payload as well fixed our problem.

I still think it is very strange that a devtools plugin shows this as default behavior on all websites the user visits.

why are you using devtools in a production environment?

[anoteboom]

I'm not using this in production. But our customers apparently are. They complained they were unable to login to our application. It took quite a while to figure out they had this plugin installed.

…

On Wed, Jun 5, 2024, 18:24 sanmont3drepo ***@***.***> wrote: @ericthomson13 <https://github.com/ericthomson13> Thank you for finding this. Our application was severly crippled because of this issue. We have a 'sign in button' that opens a popup, and waits for a 'postmessage' to close that popup window again. And because the devtools keep sending postmessages, we immediately closed the popup without the user able to complete their login. The issue you logged here allowed me to find this cause. We already checked the origin of the postmessage, and just adding a check on the payload as well fixed our problem. I still think it is very strange that a devtools plugin shows this as default behavior on all websites the user visits. why are you using devtools in a production environment? — Reply to this email directly, view it on GitHub <#27529 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/ACQLCJ7TVB6UUSKIUOQDOITZF43VVAVCNFSM6AAAAAA6CURAIGVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDCNJQGQ3TMMJTGA> . You are receiving this because you were mentioned.Message ID: ***@***.***>