2006/9/5, Sean Schofield <[EMAIL PROTECTED]>:

We might want to revisit the one dialog per JSF view assumption.  I'm
playing with the new stuff in shale-petstore and I have run into some
unexpected behavior.  I have a commandLink that kicks off a "checkout"
dialog.  This command link is located in a "menu" bar that is
displayed on every page using a facelets layout scheme (for those not
familiar with facelets, the reusable layouts are similar to Tiles.)

Lets suppose there are a few more "menu" options, such as logout, my
account, etc.  I've already made the argument that you should be able
to "cancel" the dialog by clicking som other command link in the menu
that has nothing to do with the dialog outcomes (SHALE-276).  While
this might be a PITA to support, its pretty common in a webapp to want
to click on something else on the screen other then the previous, next
buttons of your dialog.  IMO, the expected behavior would be that the
dialog stops and the new view is loaded.


One way or another, we've got to support non-dialog outcomes during the
course of a dialog. Halting the dialog seems to make sense, but of course,
there will be users that link out of a dialog and then hit the back button
expecting to be back in the dialog.


david


Sean

Reply via email to