Timeline for Drupal.behavior unexpectedly triggered by Ajax callback
Current License: CC BY-SA 3.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 16, 2014 at 14:58 | vote | accept | Kojo | ||
| Jun 12, 2014 at 14:14 | answer | added | sanzante | timeline score: 1 | |
| Jun 12, 2014 at 14:09 | comment | added | Kojo | Amazing, that's it ! Once again you saved my day Clive !!! Would you like to post it as short answer ? Many thanks | |
| Jun 12, 2014 at 14:07 | comment | added | Clive♦ | Yep, just change the existing line to the new one | |
| Jun 12, 2014 at 14:06 | comment | added | Kojo | inside Drupal.behaviors you mean ? | |
| Jun 12, 2014 at 14:05 | comment | added | Clive♦ |
$(settings.responsive_tabstoaccordion_panels.tabstoaccordion_panel).once('my_module').easyResponsiveTabs({... should sort it
|
|
| Jun 12, 2014 at 14:02 | comment | added | Kojo | well, kind of. some Dom elts are added on page load by the tab fn, but unexpectedly added again whenever ajax callbacks... I hope you understand what I mean, I'm not very familiar with these concepts yet :( | |
| Jun 12, 2014 at 14:00 | comment | added | Clive♦ |
Yep, anything the uses Drupal behaviors will re-invoke Drupal.attachBehaviors() when its task has finished. What problem is this actually giving you, is your tab functionality being attached twice when you only want it attached once?
|
|
| Jun 12, 2014 at 13:57 | history | asked | Kojo | CC BY-SA 3.0 |