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
When a prompt opens, for example when you go to "Save As", pressing return should "Accept" the prompt, but doesn't respond.
In the code the prompts are done with DOM prompt() function, which is rendered this way in nodewebkit (in chrome the prompt lets you Accept with return). Is there a way to change this behaviour? Should it use a not native prompt instead?
The text was updated successfully, but these errors were encountered:
I think indeed the nice way is not to use native prompts, giving much more control. However this will take some more effort since it will means that the code will go from synchronous to asynchronous (like a callback or promise) based on the output of the prompt.
When a prompt opens, for example when you go to "Save As", pressing return should "Accept" the prompt, but doesn't respond.
In the code the prompts are done with DOM prompt() function, which is rendered this way in nodewebkit (in chrome the prompt lets you Accept with return). Is there a way to change this behaviour? Should it use a not native prompt instead?
The text was updated successfully, but these errors were encountered: