Popup.moveOffScreen should be called on any nodes that will be used as pop-ups. dijit/popup code doesn’t close the pop-up widget directly, but rather calls the onCancel callback from the original popup.open call.dijit/popup code notices the click on the blank area of the screen.If the user clicks a blank section of the screen in order to close the pop-up instead of interacting with the widget, then the ending steps of the lifecycle are slightly different: popup.close calls the onClose callback defined in the original popup.open call.Parent widget calls popup.close, which closes the pop-up.dijit/popup code notices the onExecute/ onCancel method has been called and informs the parent widget by calling the onExecute function defined in the popup.open call.User interacts with the pop-up, causing this.onExecute() or this.onCancel() to be called on the pop-up widget.Parent widget calls popup.open to display the pop-up, passing onExecute and onCancel callbacks for when it needs to close.The lifecycle of a pop-up widget looks like this: While only the popup property is required, most pop-ups will normally need to also provide onCancel and onExecute callbacks (as explained below) as well as either an around or x and y properties. ![]() If(dropDown.startup & !dropDown._started)) An object that specifies extra padding that should be given to the area around the pop-up when determining its placement. ![]() if the pop-up has not been started yet, start it now that it can be measured by the widget’s startup method wrap the pop-up widget and position it offscreen so
0 Comments
Leave a Reply. |