[DevTools] Fix console links not being openable#210
Closed
everettbu wants to merge 1 commit into
Closed
Conversation
everettbu
force-pushed
the
sebbie/11-26-_devtools_fix_console_links_not_being_openable
branch
from
January 21, 2026 09:17
1825f21 to
82b4ac5
Compare
everettbu
marked this pull request as ready for review
January 21, 2026 09:17
Greptile SummaryAdded error handling to
Confidence Score: 5/5
Important Files Changed
|
Author
|
Upstream PR was closed or merged. Code is synced via branch mirror. |
everettbu
deleted the
sebbie/11-26-_devtools_fix_console_links_not_being_openable
branch
January 21, 2026 10:19
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
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.
Mirror of facebook/react#35229
Original author: eps1lon
In draft so I don't accidentally merge.
Fixes react/react#33983 (comment)
See https://issues.chromium.org/u/1/issues/462747680
Seems like
chrome.devtools.panels.openResourceis not actually the default behavior for the resource handler. It's erroring when trying to open URLs that don't point to Chrome Resources and not doing anything. Will bring this up with Chrome but until then we should have a workaround.E.g. clicking on
https://google.comdoes nothing.Falling back to
window.openin caseopenResourceerrors. https://developer.chrome.com/docs/extensions/reference/api/devtools/panels#method-openResource doesn't document the parameter to the callback but it returns an error-like object.Test plan
Click on the link from
console.log('https://google.com'). File links also work (e.g.console.log('file://404'))