Lines Matching full:dialog
38 // This means hosting a dialog containing HTML/JavaScript and using
40 // page setup settings from the dialog contents and provide the
41 // generated print data to the dialog contents for uploading to the
55 // show an HTML dialog using that class as the delegate. That class
62 // interactions with the dialog contents, including handing in the
63 // print data and getting any page setup parameters that the dialog
64 // contents provides. As part of bringing up the dialog,
72 // The WebUI continues dialog bring-up, calling
74 // additional object model capabilities are registered for the dialog
76 // dialog contents are adjusted to allow the dialog contents to close
79 // for notification of when the dialog contents finish loading, which
80 // is currently used to send the data to the dialog contents.
82 // In order to send the data to the dialog contents, the flow
88 // send that data to the dialog contents.
90 // When the dialog contents are finished (by either being cancelled or
92 // that the dialog should be closed, at which point things are torn
98 // bringing up the dialog) isn't what we want.
170 // sending to the dialog contents (and up to the cloud print server)
201 // We have the data in hand that needs to be pushed into the dialog
215 // Send the print data to the dialog contents. The JavaScript
288 // to the real server URL, now that we've gotten an HTML dialog
434 // This information is needed to show the dialog HTML content.
442 // If we're not modal we can show the dialog with no browser.
443 // We need this to keep Chrome alive while our dialog is up.
490 // Get the final dialog size and store it.
492 // If we're modal we can show the dialog with no browser.
514 // Called from the UI thread, starts up the dialog.
566 // the dialog.
570 // changing page setup parameters while the dialog is active.
