Re:Qt for WebAssembly
by dchest on Tuesday June 19, 2018 @05:29PM
(#17350421)
[ Parent
| on HN ]
Yeah, it would be great when it'll work for more than just 60% of the internet users. Maybe then we can actually use it!
I'm so sorry that a little bit of HTML and JavaScript reminds you and other commenters under my post of web developer's Old Browser nightmares and brave endeavors of satisfying 100% of Web users at any the cost, but we're talking about Electron which ships a quite recent version of Chromium :-)
Re:Qt for WebAssembly
by singularity2001 on Wednesday June 20, 2018 @05:13AM
(#17353698)
https://caniuse.com/#search=dialog ? NO!
<script>
confirm("No dialog needed")
</script>
Nice table, which shows that you are free to use <dialog> and many other modern features to write your Electron app:
Electron v2.0.2
Chromium v61.0.3163.100
Node v8.9.3v8 v6.1.534.41
Re:Qt for WebAssembly
by singularity2001 on Wednesday June 20, 2018 @11:28AM
(#17356286)
Electron… fair point! Except we were comparing new web GUIs.
On the flip side Electron explicitly does not impliment confirm() and prompt() which made me furious.
So there is definitely truth in the general js=cluster-fuck sentiment.
`confirm()`, `alert()`, `prompt()` and similar are widely regarded as mistakes. Including them on your new Electron app isn't something you should be doing in the first place.
Indeed:
https://developers.google.com/web/updates/2017/03/dialogs-po...
Electron has native dialog APIs: https://electronjs.org/docs/api/dialog
Re:Qt for WebAssembly
by singularity2001 on Wednesday June 20, 2018 @05:01AM
(#17353652)
TypeError: dialog.showModal is not a function
Your Electron version is old; if you're shipping it, you're probably putting your users at risk due to security issues in them. Check the latest versions here: https://electronjs.org/releases
cool... then now make it work for ie. and mobiles. and... everything else other than the betas of chrome and firefox
here you go: https://github.com/GoogleChrome/dialog-polyfill