Module captures onclick handler return value
drinkypoo - February 9, 2007 - 16:42
| Project: | Double Click |
| Version: | 5.x-1.x-dev |
| Component: | Code |
| Category: | bug report |
| Priority: | normal |
| Assigned: | Unassigned |
| Status: | active |
Jump to:
Description
Just updated fasttoggle and still having problems. Autocomplete works for other things e.g. free tagging taxonomies. I am getting the confirmation page when I try to toggle. In addition, when I click the button to confirm, the page loads eternally, never coming up.

#1
(closing your other issue)
I really can't get any information from your description. I can't see why it does not work. Please send me a link where I can test it with my own browser to track down the bug.
#2
Sorry, I can't do that. I don't have it installed on any publically accessible webserver.
We will have to find another way to troubleshoot, or just give up.
#3
I'm sorry I can't help you :(
"when I click the button to confirm, the page loads eternally, never coming up." is like "My computer doesn't start up".
#4
It's okay, I'll just remove the module and try again later when it's had more debugging.
#5
Well, I don't know atm what to debug. From all other sources (the module is installed on groups.drupal.org), I don't get such reports. You could make your local web server web accessible (dyndns.org et al) to allow remote debugging.
#6
Actually, no I couldn't, because the webserver is on a network into which inbound connections are never permitted, and can not be permitted for us to be in accordance with security-related regulations (I work for a casino in California.) The website in question is for intranet use. So I simply cannot provide you any form of access to the server.
#7
I have experienced the exact same problem. For me it appears only when the Double Click module is enabled. With the Double Click module disabled, the Fasttoggle module works as expected. I have also noticed that the toggling actually took effect a split of a second before the confirmation dialog appeared, and that the dialog is about confirming undoing the just taken effect change.
#8
Good catch! I can confirm both parts of your report.
#9
After some serious debugging, I found that somehow the overall return value from all onclick handlers is true, even though dblclick module makes some efforts to prevent that. Could you look into that, jeff?