On 15/8/06 5:30 PM, "Christian Heilmann" <[EMAIL PROTECTED]> wrote:
>> [the classic terms and conditions] >> >>> But can anybody give me a reasonable example of solving this problem without >>> target=_blank? >> >> 1) Make the Terms and conditions a mandatory step before reaching the >> form - this is also legaly the most secure. As they are annoying show >> them upfront as a must rather than sneakily in a link that might make >> the user lose her data to boot. >> 2) Embed the terms and conditions in the same document and link them >> with an anchor - that also allows you to use any CSS magic to make >> them not take up too much screenspace (overflow) - if your argument is >> that they need to be maintained separately, use SSI to pull them in >> server-side. >> 3) Store the data already entered in a session via Ajax and retain it >> when the user comes back >> 4) Include the data in an IFRAME or via Ajax setting the focus to it >> when the user hits the T&C link (not that accessible, but does work) >> 5) Call the link next to the terms and conditions checkbox I agree >> with the _Terms and Conditions_ (shift-click to open in a new window) >> and remove the parenthesis when JS is available and you can apply a >> handler. > > ah (6) Make the terms and conditions link a terms and conditions > button that sends the data and stores it in the session or POST > arguments and retains them when you choose the form view again. No.6 sounds sensible to me. I like No.2 as well. -- Kevin Futter Webmaster, St. Bernard's College http://www.sbc.melb.catholic.edu.au/ ------------------------------------------ This e-mail and any attachments may be confidential. You must not disclose or use the information in this e-mail if you are not the intended recipient. If you have received this e-mail in error, please notify us immediately and delete the e-mail and all copies. The College does not guarantee that this e-mail is virus or error free. The attached files are provided and may only be used on the basis that the user assumes all responsibility for any loss, damage or consequence resulting directly or indirectly from the use of the attached files, whether caused by the negligence of the sender or not. The content and opinions in this e-mail are not necessarily those of the College. ****************************************************** The discussion list for http://webstandardsgroup.org/ See http://webstandardsgroup.org/mail/guidelines.cfm for some hints on posting to the list & getting help ******************************************************
