-
Notifications
You must be signed in to change notification settings - Fork 3.9k
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
alert message is not visible in windows 7 #6019
Comments
@rezaamya In which version of nwjs did you run? I have a similar problem here, but it is in the newer version v0.23.6, I want to check before opening an issue. |
@EdvaldoLima I am using nwjs-v0.23.6-win-x64. same situation is for nwjs-v0.23.6-win-ia32 too. |
@rezaamya ok, can you handle the alert, close, click "ok" normally? |
@EdvaldoLima if you mean without using NWJS, yes I can, if you mean, inside the NWJS, I can't see the message but if I press Space on my keyboard, it will press "ok" and I can continue using NWJS, before pressing Space key, it's like freezing, but in fact the focus in on the alert box and I can't do anything before closing (by clicking on the "ok") the alert box. |
@rezaamya many thanks for the answers, I can reproduce the same problem on Windows 10 x64, version 0.23.6-Win-x64 on the NWJs. |
looks like this bug is due to my "transparency" code, introduced on nw23.6 there is a workaround, you can run "nw --disable-transparency" |
@rogerwang I've made a pull request nwjs/chromium.src#88 |
@jtg-gg no problem. Fixed in git and will be available in the next nightly build. |
I also encountered this problem in version 14.7. |
in the documentation there is a sample that will not show anything if click 'Item A', I found that it will show alert but it's not visible and if I press "Space key" on my keyboard, it will press 'ok'.

but if I change the Compatibility for the NW.exe, for example to Windows Vista, it will work:

the problem is I can't tell everyone to change the Compatibility mode! and also, some other features like sounds, will not work truly in compatibility mode...
The text was updated successfully, but these errors were encountered: