Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

NW2: Uncaught ReferenceError: Window.eval in different context #7315

Closed
prominentdetail opened this issue Jan 11, 2020 · 2 comments
Closed
Labels

Comments

@prominentdetail
Copy link

NWJS Version : 0.43.4
Operating System : win10

Expected behavior

tilesetWindow.eval(null, "tileSet.refresh( );" ); should successfully call the tileSet.refresh()

Actual behavior

An error:
Uncaught ReferenceError: tileSet is not defined
at :1:1
at NWWindow.eval (extensions::nw.Window:379:20)
at mainData.tab (chrome-extension://jdgkbifmkkkcgglljmlojibojoafmlhi/mainWin.js:16:17)
at :1:6
at NWWindow.eval (extensions::nw.Window:379:20)
at configData.chooseTab (chrome-extension://jdgkbifmkkkcgglljmlojibojoafmlhi/second.html:44:13)
at haveParent (chrome-extension://jdgkbifmkkkcgglljmlojibojoafmlhi/second.html:26:11)
at NWWindow. (chrome-extension://jdgkbifmkkkcgglljmlojibojoafmlhi/mainWin.js:40:18)
at NWWindow. (extensions::nw.Window:199:18)

How to reproduce

Run the attached code
nwjsTest.zip

IF I USE
"chromium-args": "--disable-features=nw2"
THEN IT WILL WORK.

@rogerwang
Copy link
Member

This is fixed in git and will be available in the next nightly build.

@rogerwang rogerwang changed the title NW2: Uncaught ReferenceError. NW2: Uncaught ReferenceError: Window.eval in different context Jan 12, 2020
@rogerwang
Copy link
Member

The nightly build for this issue is available at https://dl.nwjs.io/live-build/nw43/20200112-162000/425569548

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants