[SOLVED] Some mousing irregularities on Registration Page

test.sag.org.au/joining/join-us-now.html - ie the registration page. I have two exclusive subscription plans and an optional donation plan.

J1.5.25
CB1.8.0RC2
CBS1.3.0RC1

A tester has reported (and I have confirmed using Chrome 17, IE9 and FF10 on Win7 64b) the following anomalous behaviour
---
I have noticed some odd behaviour with the Donation checkbox:
• The form opens with Donation unchecked & $50 showing in the drop-down list – OK
• I was able to click to the right of the drop-down list (in blank space) – which turned on Donation – this was unexpected
• HOWEVER, I was not able to click in the same spot to turn off Donation – I had to click on the word Donation or the checkbox to turn it off – this was confusing
---

Is this anomalous behaviour manageable in the configuration or are there any workarounds? If so how?

Confirmed bug. Seams toggling of plan selection is 1 way when clicking the whitespace. Have created bug ticket #3343 for further investigation.

That is implemented that way on purpose, to simplify selecting a plan, but avoiding unselecting it by mistake, when people click on description text while reading it (some users do that...)

Thanks for the quick responses.

In my view it would be better 1. for there to be consistency in the click areas that turns the selection on and off, and 2. for the click area not to include the white-space adjacent to the label.

In the immediate term, can you confirm that this is not a behaviour that can be controlled by configuration at our end, ie that it is not something we can control or work around?

This behavior is controlled by the Javascript. The Javascript is released in full source-code format in the release. Search for "paidsubsClickDescription" in cbpaidsubscription.js for the code for that.

In Joomla debug mode that file is used, and in non-debug the minified file cbpaidsubscription.min.js (you can copy cbpaidsubscription.js to the min.js file if needed.

That's something that will evolve, so you'll need to make your changes at each upgrade.

Thanks again. That is probably not an ongoing code-tweaking/maintenance task that I would want to establish for my client.