You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Run nw.exe (same result with and without a manifest)
Right click the NWJS taskbar icon
Right click the option: "NWJS Default"
Click "Properties"
The properties window will show that the icon Target is "...\chrome_proxy.exe" and not "...\nw.exe" as it should be.
This issue prevents the use of the "Pin to taskbar" option because the pinned icon will try to launch "chrome_proxy.exe" which does not exist.
This bug has been reported before as issue #7033. It was fixed and closed. This seems to be a regression due to changes since that fix.
The file that was modified to fix this issue before (#7033) was chrome/browser/web_applications/components/web_app_shortcut_win.cc. I wanted to look at that file to see what had changed and it seems it no longer exists. The folder chrome/browser/web_applications/components no longer exists (web_applications).
The text was updated successfully, but these errors were encountered:
Issue Type
Expected/Proposed Behavior
I expected the taskbar icon to point to the
nw.exe
app.Additional Info
To reproduce
On a Windows 10 x64 PC (32bit has same issue)
nw.exe
(same result with and without a manifest)Target
is "...\chrome_proxy.exe" and not "...\nw.exe" as it should be.This issue prevents the use of the "Pin to taskbar" option because the pinned icon will try to launch "chrome_proxy.exe" which does not exist.
This bug has been reported before as issue #7033. It was fixed and closed. This seems to be a regression due to changes since that fix.
The file that was modified to fix this issue before (#7033) was
chrome/browser/web_applications/components/web_app_shortcut_win.cc
. I wanted to look at that file to see what had changed and it seems it no longer exists. The folderchrome/browser/web_applications/components
no longer exists (web_applications).The text was updated successfully, but these errors were encountered: