Stephen, I think we are talking about different context with regards to Facebook example.
You don't really get side by side options on Facebook to open in separate page or open in modal window. Why does this thing need to have a 'name' anyway? Cheers, Jason On Wed, Jul 20, 2011 at 5:43 PM, Stevio <redea...@freeuk.com> wrote: > User choice basically. They may prefer to see more of a form in its own > page, or they may prefer to use a modal form to add the record. > > If JavaScript is disabled, the system still works fine with the non-modal > form option. > > Take Facebook's current implementation of photos for example. A while back > they introduced a modal viewing box for images. However, if you click F5 to > refresh Firefox, you go back to the old style viewing of the image in it's > own page. Often I do this because I prefer it, other times I persist with > their viewing box. > > As for a user-friendly name for the modal link, so far I've come up with > "coolbox", "float", or using an icon with an arrow. > > Any better suggestions? > > Thanks, > Stephen > > > ----- Original Message ----- From: "Hassan Schroeder" < > has...@webtuitive.com> > To: <wsg@webstandardsgroup.org> > Sent: Wednesday, July 20, 2011 5:18 PM > Subject: Re: [WSG] Modal forms - what to call them? > > > > On 7/20/11 8:45 AM, Stevio wrote: >> >>> I am working on a CMS and within it, when a user wishes to add a record, >>> I give them two options: >>> 1) Add record - this goes to a new web page with a form. >>> 2) Add record modally - this brings up a modal dialog box containing the >>> form which allows them >>> to add the record without leaving the page they were on (this page lists >>> the current records). >>> This uses jQuery. Once they add the record, the list of records is >>> updated using AJAX. >>> >> >> However, I would like something shorter and simpler than 'pop-up dialog >>> box'. Any thoughts? >>> >> >> Just curious -- why offer a choice? >> >> Why not just offer the modal version if JS is enabled and the other >> if not? >> >> What is the user benefit of the non-modal option? And is it enough >> to justify introducing an extraneous decision into the workflow? >> >> Will the target user understand the implications of the choices and >> pick one unhesitatingly? Or think "eh? what?" :-) >> >> Just askin' ... >> > > > > *********************************************************************** > List Guidelines: > http://webstandardsgroup.org/**mail/guidelines.cfm<http://webstandardsgroup.org/mail/guidelines.cfm> > Unsubscribe: > http://webstandardsgroup.org/**join/unsubscribe.cfm<http://webstandardsgroup.org/join/unsubscribe.cfm> > Help: memberhelp@webstandardsgroup.**org<memberh...@webstandardsgroup.org> > *********************************************************************** > > -- Jason Grant BSc [Hons], MSc [Hons] Customer Experience Architect Flexewebs Ltd. www.flexewebs.com ja...@flexewebs.com +44 (0)7748 591 770 www.flexewebs.com/semantix www.twitter.com/flexewebs www.linkedin.com/in/flexewebs ******************************************************************* List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm Help: memberh...@webstandardsgroup.org *******************************************************************
