Repository navigation
0.13 beta4 - devtools / source not found when clicking links from console #4269
Description
In beta4 on Ubuntu 15.10 64-bit, clicking a link to source from the console opens a new ERR_FAILED browser window with "This webpage is not available," rather than displaying the source within devtools:
package.json:
{
"name": "sample",
"main": "index.html"
}
index.html:
<!DOCTYPE html>
<html>
<head>
<title>Hello World!</title>
</head>
<body>
<h1>Hello World!</h1>
<script>
nw.require('./myModule.js');
</script>
</body>
</html>
myModule.js:
console.log("Hello.");
To reproduce:
- Run
nwjs-sdk-v0.13.0-beta4-linux-x64/nw . - Right-click -> "Inspect background page"
- See output:
Hello. /home/max/code/sports/test/myModule.js:1 - Click link to source
Result: New window opens. URL is "chrome-devtools://devtools/home/max/code/test/myModule.js". Title is "chrome-devtools://devtools/home/max/code/test/myModule.js is not available - NW.js". Content is: "This webpage is not available | ERR_FAILED | The webpage at chrome-devtools://devtools/home/max/code/test/myModule.js might be temporarily down or it may have moved permanently to a new web address."
Notably, this only happens when myModule.js is included in the above fashion. If instead index.html includes it like this:
<script src="myModule.js"></script>
... then it works, except that it doesn't seem to correctly link to the right line number, and the output must be viewed via "Inspect" rather than "Inspect background page".
Activity
maxbarry commentedon Jan 18, 2016
I also just posted in #4121, which is closed, but still exhibiting a similar crashing bug for me.
ghostoy commentedon Jan 19, 2016
The root cause is that NW crashes when trying to opening a new window in a tab, which was the behavior of Chrome browser. It will happen in following scenarios:
test case for issue nwjs#4269
Merge pull request #4279 from ghostoy/issue-4269-test
rogerwang commentedon Jan 20, 2016
Fixed in git and will be available in the next nightly build.
Not open external site for case nwjs#4269
Merge pull request #4298 from ghostoy/issue-4269-no-external-site
Change default disposition to `NEW_POPUP` for urls opened by app
12 remaining items
maxbarry commentedon Apr 6, 2016
Sorry, more of a question than a bug report, but I just noticed this is now milestoned for 0.14, and am a bit alarmed at the idea of not being able to use 0.13 at all.
Is there a workaround for this bug? I don't understand how I can work with 0.13 since I can't debug. The only thing I can think of is to merge the entire app into a single file so that it doesn't 'require' anything.
rogerwang commentedon Apr 6, 2016
@ghostoy had a fix. It's still under review and it's marked as 0.14 because the underlying change is important. We want to make sure it doesn't have any side effects. @ghostoy can we have some way to enable it only in SDK build?
btw, 0.14 would be released soon with Chromium 50 stable in 1-2 weeks.
rogerwang commentedon Apr 6, 2016
PS, the patch still has a chance to be in 0.13.x although it's marked as 0.14.
Fix broken links generated from Node modules in DevTools
Fix broken links generated from Node modules in DevTools
IssueHuntBot commentedon Sep 17, 2018
@loadbalance-sudachi-kun funded this issue with $256. Visit this issue on Issuehunt
championpaddler commentedon Dec 21, 2018
@maxbarry I am claiming this issue.