Closed (won't fix)
Project:
Terms of Use
Version:
6.x-1.12
Component:
Code
Priority:
Normal
Category:
Feature request
Assigned:
Issue tags:
Reporter:
Created:
12 Apr 2010 at 08:07 UTC
Updated:
26 May 2015 at 14:10 UTC
Jump to comment: Most recent, Most recent file
Comments
Comment #1
kars-t commentedI think this might be a nice option.
Please add a switch to the settings form and make a real patch out of this.
http://drupal.org/patch/create
Comment #2
shenzhuxi commentedThe register form shouldn't never be refresh when users look at the term of use.
So it's not necessary to keep it open in the some page.
Comment #3
kars-t commentedHi shenzhuxi
yes and your patch adds target="_blank" to the link.
Please add this as option to the admin form and create a patch for this. :)
Comment #4
venusrising commentedI tested this code and it seems to work well.
Comment #5
shenzhuxi commentedThe attach is the patch file for 1.12.
Comment #6
kwinters commentedThe patch is a little messy (whitespace mostly).
Kars-T was asking you to also add a setting to the admin config form, but I don't think that's all that beneficial. Accidentally losing all your info in the register form carries a huge usability cost, so it really needs to open in a new window. If you want to add a setting for it then fine, but that's minor compared to the impact of changing the default.
So, I'd much rather the change was committed as-is rather than wait on a setting.
Comment #7
kars-t commented@kwinters
Better use invalid HTML than loosing all data? Breaks my heart but I see your point. :)
I have some difficulties to deciede if its wise to change the behaviour as people are used to this. They don't like it but its expected to happen. I will talk in IRC about this a bit.
Comment #8
kwinters commentedI'd argue that most non-technical audiences are used to "new window" on pages with forms. See http://www.nytimes.com/gst/regi.html or http://commerce.wsj.com/entitlements/release_freereg_rel3/login.shtml?ro...
Comment #9
walden commented+1 for committing the change as is - since this feature is placed at the bottom of the registration form, users definitely pay the price (by loosing all of their entered data) for viewing the t&c.
Loading the t&c in a modal window would be really slick if lightbox/thickbox modules are present.
Comment #10
shenzhuxi commentedThe new patch add popups api support if the module is installed.
Comment #11
kars-t commentedDear shenzhuxi
I really appreciate your patch and I feel bad fro not playing nice but I won't apply this patch. :-/
The problem is that we would need to add any POP JS through PHP than. Maybe a big switch. And pop up API even is not supported any more. Please comment on #807600: RFC: Terms of use 2.0 so we quicker can get to a 2.0 that is pluggable and we can add any JS popups as we like :)
Comment #12
kwinters commentedWhat about a simple _blank implementation for 1.x? It's trivial to make the change, so it's just a matter of agreeing that it's a good idea.
Comment #13
kars-t commentedIMHO "_blank" is evil but as you say would be a nice mini thing to fix. If you provide a patch as an optional setting I will happily add it. :)
Comment #14
lpalgarvio commentedprovided there's a link to the terms, i don't think it makes sense to force open in a new window.
W3C HTML standards specifically advise against using target="_blank" and it doesn't even validate in the HTML/XHTML validators.
instead, they recommend you use the browser "open in new window". i think that is fair.
i would recommend you guys that a look on a few modules:
- Starbox API
- Colorbox (replaces Thickbox)
- Lightbox2
- Modalframe API
- Chaos Tools (might have something useful as an optional addon)
Thickbox and Popups API are deprecated.
I wouldn't recommend using Shadowbox module as it seems the developer is having problems with the creator of Shadowbox javascript library.
Comment #15
kwinters commentedShould this still be closed won't fix? That was added in response to a JS library addition.
I don't think that _blank should be required, but it (or something equivalent) is very frequently requested. A config option would be ideal, but a hook is also reasonable.
Recommending that visitors open something in a new window isn't something I can get behind in a form. Users don't read, and (as I've stated above), the losing-all-your-data penalty for a mistake is unreasonably high.
Comment #16
betoaveigaHi!
I found a very easy solution that could be good enough...
In your 'label for the checkbox' (see terms of use configuration) write something like:
I agree ... @link <a target='_blank' class='terms' href='/terms-of-use'>terms of use</a>.In your CSS you put this...
Hope that helps!
Comment #17
lpalgarvio commentedhum so to sum up options...
#1) leave as normal link
#2) change link to target="_blank"
#3) add CSS to display TOS right after clicking the link
#4) show TOS in a modal window/overlay
for window/overlay module suggestion, i'll drop in another one:
- Starbox API - meant to replace colorbox, thickbox, lightbox, shadowbox and other *box modules (D7)
- Colorbox (replaces Thickbox)
- Lightbox2
- Modalframe API - has multiple submodules and contrib modules, used by noderelations
- Chaos Tools (might have something useful as an optional addon) - used by panels
- Dialog API - has a few submodules, used by skinr 2.x
the first 3 options could be easily added to the configuration page in the next releases.
support for a modal window/overlay module is more complex.
Comment #18
benovic commenteddon't know if this is a bigger mess, but at least you do not have to hack the module. Plus i use the JS "onclick" to stay XHTML valid.
Workaround using HOOK_FORM_ALTER:
Comment #19
picxelplay commentedThis could all be avoided if the module would just allow html. It's just messy with @link. This would solve all the multiple terms and _blank issues.
Comment #20
kenorb commented