Not planned
Description
Steps To Reproduce
- Install React Devtools extension for Firefox
- Go to "about:neterror?e=connectionFailure"
The current behavior
Firefox shows this error in the console: "The extension "React Developer Tools" is not allowed to access about:neterror?e=connectionFailure"
The expected behavior
Firefox shows no error in the console
Metadata
Metadata
Assignees
Type
Projects
Milestone
Relationships
Development
No branches or pull requests
Activity
bvaughn commentedon Nov 2, 2020
Related to PR #20023
I'm not aware of a reliable way to detect special/protected URLs like "about:neterror" in Firefox and prevent React DevTools from treating it like any other page. If you know of a way, please shoot us a PR!
[-]Bug: The extension "React Developer Tools" is not allowed to access about:neterror?e=connectionFailure[/-][+]React Developer Tools triggers console error in Firefox for protected URLs[/+]sktguha commentedon Nov 12, 2020
Hi, author of the above PR here.
To add to Brian's comment, so I think in the code here:
react/packages/react-devtools-extensions/src/background.js
Line 108 in 1b96ee4
When we try to access
tab.active
in firefox, if it is a protected page, firefox will throw an errorIf that is the case, I don't think we can really do anything at all. If we try to access the
tab.url
or some other property on thetab
object to see if its a protected page, before that check only firefox will throw the same errorMaybe wrapping the code in a try catch could work ? But I doubt it
@SimonSiefke maybe you could possibly step through in a debugger in firefox and check that the above thing happens and/or verify the try catch theory ?
In chrome and edge however this issue doesn't happen. Infact it is possible to read the
tab.url
of a protected page like chrome://extensions etc from any extension.arshbuilds commentedon Mar 24, 2024
Apparently, I only get this error when I go to
localhost:3000
without turning on the dev serveryarn dev
github-actions commentedon Jun 22, 2024
This issue has been automatically marked as stale. If this issue is still affecting you, please leave any comment (for example, "bump"), and we'll keep it open. We are sorry that we haven't been able to prioritize it yet. If you have any new additional information, please include it with your comment!
github-actions commentedon Jun 29, 2024
Closing this issue after a prolonged period of inactivity. If this issue is still present in the latest release, please create a new issue with up-to-date information. Thank you!