[WSG] Re: WSG Digest

2011-07-20 Thread Alan C. Whiteman




On 07/21/2011 09:48 AM, wsg@webstandardsgroup.org wrote:

*
WEB STANDARDS GROUP MAIL LIST DIGEST
*


From: "Stevio"
Date: Wed, 20 Jul 2011 16:45:33 +0100
Subject: Modal forms - what to call them?

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, what user-friendly descriptive name should I use for the modal
forms? I doubt many people know the word modal. Any suggestions?

It would be laid out as follows:
Add record (pop-up dialog box)?

Clicking on 'Add record' takes the user to a new page, while clicking on
'pop-up dialog box' opens the modal form.

However, I would like something shorter and simpler than 'pop-up dialog
box'. Any thoughts?

Thanks,
Stephen


*
From: "Nixon David"
Date: Wed, 20 Jul 2011 17:53:41 +0200
Subject: RE: [WSG] Modal forms - what to call them?

I usually go with business activity - business function with my modal
forms (SharePoint)
e.g. Records - Declare a new record

-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Stevio
Sent: 20 July 2011 16:46
To: Web Standards Group
Subject: [WSG] Modal forms - what to call them?

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, what user-friendly descriptive name should I use for the modal
forms? I doubt many people know the word modal. Any suggestions?

It would be laid out as follows:
Add record (pop-up dialog box)?

Clicking on 'Add record' takes the user to a new page, while clicking on
'pop-up dialog box' opens the modal form.

However, I would like something shorter and simpler than 'pop-up dialog
box'. Any thoughts?

Thanks,
Stephen



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


*
From: Hassan Schroeder
Date: Wed, 20 Jul 2011 09:18:29 -0700
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' ...



I agree that, from a usability point of view, having only one choice- 
one path- offers the best experience. It just sounds more efficient. So, 
yes, the modal form (no name) when JS is turned on, and the HTML form 
(again, no name) for when JS is off. To the user there is only one form.



--
Regards
~
Alan C Whiteman| Visualis Web Design
http://visualis.us | (562) 305-2862



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***<>

[WSG] Out of Office AutoReply: WSG Digest

2011-07-20 Thread Andy Dempster
I will be out of the office until Wednesday, July 27th. I will get back to you 
then. 






***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


[WSG] AUTO: Kirsten Tilgals is out of the office (returning 08/08/2011)

2011-07-20 Thread KirstenT
 

I am out of the office until 08/08/2011.

Thanks for your message. If you are emailing from within the Art Gallery of
NSW regarding the Gallery's website, please email 'Web Team'. Or you can
contact Brooke Carson-Ewart broo...@ag.nsw.gov.au or Jonathan Cooper
jonath...@ag.nsw.gov.au directly


Note: This is an automated response to your message  "WSG Digest" sent on
21/07/2011 7:48:41 PM.

This is the only notification you will receive while this person is away.

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


[WSG] Out of Office Reply Re: WSG Digest

2011-07-20 Thread Julien Viard
Hello!

I'm out of the office until Monday 15th August.

I'll respond to all emails on my return.

For more urgent assistance, please contact Georgie at
geor...@10collective.com.au or call the office on 03 9935 9409.

Cheers,
Julien


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] Modal forms - what to call them?

2011-07-20 Thread Jason Grant
Hi Stephen,

No it wouldn't be nice if Facebook offered a choice. It would be stupid and
annoying, hence they don't do it and hence noone else does that anywhere
online and hence Hassan is suggesting the same thing I am suggesting.

Usually anything that opens in a modal window may be denoted with a little
icon, but there isn't really a need for that these days as modal windows are
a perfectly fine aspect of Web2.0. Just use Google+ and knock yourself out
for 1000s of examples to support that statement.

Hope this helps. If you want a more in-depth conversation and advice from
me, send me a direct mail to avoid pissing off the mailing list.

Cheers,

Jason

On Wed, Jul 20, 2011 at 6:01 PM, Stevio  wrote:

> **
> Hi Jason, I was just using that as an example, that users may prefer one
> way over the other, and so I wish to offer them a choice. It would be nice
> if Facebook offered the choice!
>
> See my original email - it needs a name because the word modal is not one
> that I think users would be familiar with. I need something to differentiate
> between opening the form in a separate page and in a modal form, preferably
> something short and to the point.
>
> Thanks,
> Stephen
>
> - Original Message -
> *From:* Jason Grant 
> *To:* wsg@webstandardsgroup.org
> *Sent:* Wednesday, July 20, 2011 5:49 PM
> *Subject:* Re: [WSG] Modal forms - what to call them?
>
> 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  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: 
>> 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
>> Unsubscribe: 
>> http://webstandardsgroup.org/**join/unsubscribe.cfm
>> Help: memberhelp@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
> ***
>
>
> ***
> List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
> Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.

Re: [WSG] Modal forms - what to call them?

2011-07-20 Thread Stevio
Hi Jason, I was just using that as an example, that users may prefer one way 
over the other, and so I wish to offer them a choice. It would be nice if 
Facebook offered the choice!

See my original email - it needs a name because the word modal is not one that 
I think users would be familiar with. I need something to differentiate between 
opening the form in a separate page and in a modal form, preferably something 
short and to the point.

Thanks,
Stephen
  - Original Message - 
  From: Jason Grant 
  To: wsg@webstandardsgroup.org 
  Sent: Wednesday, July 20, 2011 5:49 PM
  Subject: Re: [WSG] Modal forms - what to call them?


  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  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" 

To: 
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
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: 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
  *** 

***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***


Re: [WSG] Modal forms - what to call them?

2011-07-20 Thread Jason Grant
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  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: 
> 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
> Unsubscribe: 
> http://webstandardsgroup.org/**join/unsubscribe.cfm
> Help: memberhelp@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
***

Re: [WSG] Modal forms - what to call them?

2011-07-20 Thread Stevio
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" 

To: 
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
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



Re: [WSG] Modal forms - what to call them?

2011-07-20 Thread Jason Grant
+1 to Hassan's comment.
There is no point in having two options.
Just have one chunky button called 'Add record' which takes user to modal
form with JS on and separate page with JS off.
As long as this is coded in progressive enhancement manner everything should
be fine.

On Wed, Jul 20, 2011 at 5:18 PM, Hassan Schroeder wrote:

> 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' ...
>
> --
> Hassan Schroeder - has...@webtuitive.com
> webtuitive design ===  (+1) 408-621-3445   === http://webtuitive.com
> http://about.me/**hassanschroeder 
> twitter: @hassan
>  dream.  code.
>
>
> ***
> List Guidelines: 
> http://webstandardsgroup.org/**mail/guidelines.cfm
> Unsubscribe: 
> http://webstandardsgroup.org/**join/unsubscribe.cfm
> Help: memberhelp@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
***

Re: [WSG] Modal forms - what to call them?

2011-07-20 Thread Hassan Schroeder

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' ...

--
Hassan Schroeder - has...@webtuitive.com
webtuitive design ===  (+1) 408-621-3445   === http://webtuitive.com
http://about.me/hassanschroeder
twitter: @hassan
  dream.  code.


***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



RE: [WSG] Modal forms - what to call them?

2011-07-20 Thread Nixon David
I usually go with business activity - business function with my modal
forms (SharePoint)
e.g. Records - Declare a new record

-Original Message-
From: li...@webstandardsgroup.org [mailto:li...@webstandardsgroup.org]
On Behalf Of Stevio
Sent: 20 July 2011 16:46
To: Web Standards Group
Subject: [WSG] Modal forms - what to call them?

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, what user-friendly descriptive name should I use for the modal
forms? I doubt many people know the word modal. Any suggestions?

It would be laid out as follows:
Add record (pop-up dialog box)?

Clicking on 'Add record' takes the user to a new page, while clicking on
'pop-up dialog box' opens the modal form.

However, I would like something shorter and simpler than 'pop-up dialog
box'. Any thoughts?

Thanks,
Stephen 



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***



[WSG] Modal forms - what to call them?

2011-07-20 Thread Stevio
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, what user-friendly descriptive name should I use for the modal 
forms? I doubt many people know the word modal. Any suggestions?


It would be laid out as follows:
Add record (pop-up dialog box)?

Clicking on 'Add record' takes the user to a new page, while clicking on 
'pop-up dialog box' opens the modal form.


However, I would like something shorter and simpler than 'pop-up dialog 
box'. Any thoughts?


Thanks,
Stephen 




***
List Guidelines: http://webstandardsgroup.org/mail/guidelines.cfm
Unsubscribe: http://webstandardsgroup.org/join/unsubscribe.cfm
Help: memberh...@webstandardsgroup.org
***