Hi,
Off the top of my head I remember 2 concerns/problems that still aren't addressed:
* The actions are called hide/show and the events are called close/open (and consequently the wording wasn't consistent)
* We don't specify behaviour in relation to relevance (is the close event dispatched when the dialog or an ancestor becomes non relevant. Does that dialog becomes visible again when it becomes relevant again (if it was visible before it became non-relavant)?)
Kind regards,
Nick Van den Bleeken
R&D Manager
Phone: +32 3 425 41 02
Office fax: +32 3 821 01 71
nick.van.den.bleeken@inventivegroup.com<mailto:nick.van.den.bleeken@inventivegroup.com>
www.inventivedesigners.com
[cid:image001.png@01CBF2F8.1DA19110][cid:image002.png@01CBF2F8.1DA19110][cid:image003.png@01CBF2F8.1DA19110]
On 23 Jan 2013, at 20:40, Erik Bruchez <erik@bruchez.org<mailto:erik@bruchez.org>> wrote:
All,
This is mainly a question to Nick, which was raised by Uli and I in
today's short call: is there any reason not to integrate the XForms
Dialog Module?
http://www.w3.org/MarkUp/Forms/wiki/The_XForms_Dialog_Module
I don't recall there being blocking issues, but I might be wrong.
-Erik
________________________________
Inventive Designers' Email Disclaimer:
http://www.inventivedesigners.com/email-disclaimer
