{"id":291,"date":"2011-01-02T17:43:01","date_gmt":"2011-01-02T16:43:01","guid":{"rendered":"http:\/\/www.speich.net\/articles\/?p=291"},"modified":"2019-10-06T12:28:19","modified_gmt":"2019-10-06T10:28:19","slug":"creating-a-blocking-confirm-dialog-with-dojo","status":"publish","type":"post","link":"https:\/\/www.speich.net\/articles\/en\/2011\/01\/02\/creating-a-blocking-confirm-dialog-with-dojo\/","title":{"rendered":"Creating a ‘blocking’ confirm dialog with dojo"},"content":{"rendered":"\n

Update 30.03.2018<\/strong>: Version 1.10 of dojotoolkit includes a dijit\/DialogConfirm<\/a> now, which is simply a dijit\/Dialog featuring ‘OK’ and ‘Cancel’ buttons, no blocking though.<\/p>\n\n\n\n

Update 15.10.2012:<\/strong> Code is available on githup <\/a>now. I also fixed updating the content of the dialog after creation (e.g. dialog.set(‘content’, newContent) overwrote the confirm\/cancel buttons because they were part of the content.<\/p>\n\n\n\n

Update 03.12.2011:<\/strong> I updated the code to use dojo 1.7 with AMD. I also moved the creation of the Deferred to the show() method as suggested by ben<\/a>, which will make the instance of the dialog reusable. Added new property hasUnderlay: true, which can be set to false.<\/p>\n\n\n\n

JavaScript has a window.confirm()<\/a> method, which opens a dialog and stops code execution until the user presses either the ‘OK’ or ‘Cancel’ button. Dojo also comes with a dijit.Dialog <\/a>widget, but that doesn’t exhibit the same blocking behavior. Since I needed to simulate the native blocking behavior for an application I am currently developing, I extended the widget and created the DialogConfirm widget<\/a> with the following features:<\/p>\n\n\n\n