BUG: Event 'open' stop works after once triggered
See original GitHub issue- NWjs 0.66.1 - ok
- NWjs 0.67.1 - ok
- NWjs 0.68.1 - fail
Windows 11 22H2 (22622.601) x64
index.html
<!DOCTYPE html>
<html lang="en">
<head>
<meta charset="utf-8">
<title>Demo</title>
</head>
<body>
<script>
nw.App.on('open', (params) => {
console.log(params);
});
setTimeout(() => nw.Window.get().showDevTools(), 100);
</script>
</body>
</html>
Issue Analytics
- State:
- Created a year ago
- Comments:7 (5 by maintainers)
Top Results From Across the Web
How to trigger an event after using event.preventDefault()
Nope. Once the event has been canceled, it is canceled. You can re-fire the event later on though, using a flag to determine...
Read more >Solved: Onchange event often triggers when screen becomes
I solved my issue. It turns out that there is a bug in PowerApps such that simply changing records triggers the OnChange event...
Read more >.trigger() | jQuery API Documentation
stopPropagation() method on the event object passed into the event. Although .trigger() simulates an event activation, complete with a synthesized event object, ...
Read more >The event loop - JavaScript - MDN Web Docs - Mozilla
If there is no other message in the queue, and the stack is empty, the message is processed right after the delay. However,...
Read more >Triggering a workflow - GitHub Docs
For example, the following workflow triggers when an issue is opened or ... is opened, three workflow runs will start: one for the...
Read more >Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start FreeTop Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found
Top GitHub Comments
It’s a single big master patch. You can get it by comparing NW with the upstream.
I understand that. My question is are the list of modifications saved somewhere or do you know them by memory (trying to understand the codebase)?