Currently, all confirm window of tiddlywiki basically use the window.confirm window.prompt interface. My usage scenario is in full screen mode, and these pop-ups will force you to exit the full screen mode. I know this is a problem with the browser’s security mechanism. Entering full screen through f11 will not cause the full screen mode to exit. However, if you manually call the full screen interface through the interface or tw’s full screen button, these pop-ups will force you to exit the full screen mode, which really affects the experience. Unless you manually click f11 every time
Hi @oeyoews sadly, the implementation of <$action-confirm> depends on the confirmation dialogue being synchronous, with JavaScript execution paused for as long as the confirmation dialogue is displayed. This is only possible with the window.confirm() method, and it is not possible to emulate the same behaviour with pure HTML, CSS and JavaScript.
Meanwhile, there have long been rumblings within the W3C community to deprecate window.confirm and window.alert – see Deprecate alert(), confirm(), prompt() · Issue #2894 · whatwg/html · GitHub
I think we have little choice at some point but to deprecate <$action-confirm>. We can provide an alternative, but it will not be fully backwards compatible. This is the sort of thing we might do as part of a putative v5.4.0 release which intentionally breaks some backwards compatibility in the interests of future proofing TiddlyWiki.
In the meantime, the best path forward for your application might be to use TiddlyWiki’s modal system to display a custom confirmation dialogue.
4 Likes