One advantage of this pattern is not having to write client-side logic for what happens when a user navigates away from an input form after making changes but not indicating to save or cancel. Since some users may assume that clicking another link is a safe way to get out of a form without saving anything, I think logic to handle this in a traditional in-page form is helpful if the form in question requires a bit of work and the user might accidentally click another link. By having an X to close the flyout in a corner of the layer set away from where the user is working, the user still has a way to explicitly escape from what they are doing without doing so by accident, and you don't have to write the code to trap for that.
I also think this technique helps remove distractions when concentration is essential to completing a task. I prefer a slightly grayed out background (the disabled look) to the blacked out backgrounds used on many sights but don't think black is a problem if the user can still complete their task. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . Posted from the new ixda.org http://www.ixda.org/discuss?post=44487 ________________________________________________________________ Welcome to the Interaction Design Association (IxDA)! To post to this list ....... disc...@ixda.org Unsubscribe ................ http://www.ixda.org/unsubscribe List Guidelines ............ http://www.ixda.org/guidelines List Help .................. http://www.ixda.org/help
