[whatwg] RE: modal and modeless windows

Klotz, Leigh Leigh.Klotz at XEROX.COM
Tue Jun 28 11:14:18 PDT 2005

This use case is exactly why browsers allow XForms controls inside
One minor quibble is that the message is not a different XForms
document, but is part of the same host document (XHTML probably), and
operates on the same model.
You can use xf:duplicate from Xforms 1.1 to implement the undo/cancel
button, to save away a copy of the data before and restore it on cancel.
Or you can save away a copy of the data on open of the xf:message,
operate on it, and copy it back on save.
Your choice! 


-----Original Message-----
From: www-forms-request at w3.org [mailto:www-forms-request at w3.org] On
Behalf Of Karl Pongratz
Sent: Monday, June 27, 2005 7:24 AM
To: Mark Birbeck
Cc: www-forms at w3.org; whatwg-whatwg.org at lists.whatwg.org; dean at w3.org
Subject: Re: modal and modeless windows


I appreciate that Xforms supports modal and modeless messages, yet I
miss it in the web browser.

I could envision that as follows, lets take the address book of
Microsoft Outlook, the desktop application, as an example.

You have a page (resource) my_addresses.html, a simple document that
shows you all your addresses without any form fields. If you want to
edit an address you click on it, which will open a modal window, this
modal window should then contain the xforms document to edit the
address, with a "Save and Close" and "Cancel" button. Cancel will close
the modal window, no other action is taken. Save and Close will save the
form data, closes the modal window and it will update the changes in the
underlying my_addresses.html document, i.e. by reloading it.

You can do the same without modal windows, the traditional approach, see
Views and Forms: Principles of Task Flow for Web Applications Part 1
(Bob Baxley)

Though I believe the modal window approach would be much cleaner and
saver, maybe Bob Baxley would have chosen that way, if modal windows


More information about the whatwg mailing list