rasyahadlinugraha / wiquery

Automatically exported from code.google.com/p/wiquery
MIT License
0 stars 0 forks source link

Nested ListView and Accordion Component #245

Closed GoogleCodeExporter closed 9 years ago

GoogleCodeExporter commented 9 years ago
I am creating a dynamic Accordion Component with multiple sections and each 
sections content contains links.

I am using nested listviews to generate the Accordion Layout.

The issue, is when I set the initial active state of the accordion to false, 
using the following API Accordion.setActive(new AccordionActive(false).

The intent is to initially render all sections collapsed, which it does.
I can then click on a section header to expand the section but when I try to 
select a different header it doesn't expand.

The odd part is that if I click on one of the content links the Accordion 
starts working normally.  The only thing I do in the Ajax onClick callback is 
refresh the Accordion.

I created a quickstart using static html with 3 sections and the active state 
set to false.  This test worked just fine, it only seems to run into problems 
when I dynamically create the accordion layout using nested listviews (One 
Listview for the sections, and then a nested ListView (per category) with the 
Links).

I am using WiQuery 1.2.1 but tested this with WiQuery 1.2.3 and it behaves the 
same.

Original issue reported on code.google.com by jd.cor...@receptrix.com on 13 Apr 2012 at 7:43

GoogleCodeExporter commented 9 years ago
I was able to dynamically create my sample Accordion using nested listviews.  
When I do the same thing in my production code, I get the strange behavior I 
reported originally.  I suspect it is some javascript in the header that is 
messing with the JQuery stuff, but there is so much in the header I wouldn't 
know where to begin to isolate it.

Original comment by jd.cor...@receptrix.com on 16 Apr 2012 at 1:58

GoogleCodeExporter commented 9 years ago
Sorry for the late response, without any example there is not much we can do. 
This is why it has not been reported to be investigated...

WiQuery 1.2.x is an old version, and most of the client-side stuff is jQuery 
only. WiQuery generates init statements, thats about it.

Original comment by hielke.hoeve on 8 May 2012 at 4:26

GoogleCodeExporter commented 9 years ago
Hi, no worries.  I was able to address the issue.

Original comment by jd.cor...@receptrix.com on 12 May 2012 at 4:19

GoogleCodeExporter commented 9 years ago

Original comment by hielke.hoeve on 21 May 2012 at 4:19

GoogleCodeExporter commented 9 years ago

Original comment by hielke.hoeve on 22 May 2012 at 7:43