Does roll-your-own hurt SEO when display:none is used for nesting?

After some more digging, I found a newer post ( http://spacedonkey.de/2432/nested-collapse-elements-with-highlander-grouping/ ) which shows nested roll-your-own expands WITHOUT inline display:none styling on the target elements — so I updated to 1.7.3, removed display:none on the target elements, and the nesting seems to work OK with the roll-your-own approach. Maybe the inline display:none from the older post mentioned above were just there for flicker prevention, but I thought that when I tried deleting display:none before doing the version update, the expand content showed by default — maybe something else was going on.

Anyway, perhaps my concern about SEO is gone now, since I now have the option to operate with display:none removed, as long as I can live with flicker.

Thanks Baden for the clarifications and tip about maptastic class. I tried maptastic but had a new problem surface as follows:
After your suggestion I did add maptastic inline as a class to the roll-own target divs (ie, ‘<div class=”maptastic collapseomatic_content etc… ‘). And, on the same page, where shortcodes were used for other expands, I applied it as a special class using targclass=”maptastic” in the expand shortcode, per the documentation. The result was good as far as it preventing flicker in both cases, and the content showed fine when the individual triggers were clicked. However, my page-wide expand-all link stopped working (implemented as ‘<span class=expandall”>Expand All</span>’) — with the addition of these maptastic classes, the expand-all now does not cause the content to be displayed, but it does trigger the swaptitle for the trigger text/arrow in all cases — it’s as if the maptastic class is not being managed properly (not being removed?) when expandall is clicked. Any idea on why this might be happening?

Thanks for looking into this Baden. Yes, the missing quote was just a typo in my post.
In the meantime, I have developed a workaround that seems to work, and also made one more odd discovery that I also worked around, as follows:
– As described, the maptastic class does not get removed when clicking the expand-all span (although the swaptitle trigger text and arrow both change normally). To work around this, I created a simple jQuery onclick function to remove the maptastic class from all collapseomatic_content divs when the expand-all span is clicked — this seems to work OK.
– I noticed a second problem that also seemed related to the expand-all/collapse-all functionality: I use an additional close trigger at the bottom of my expand content per the documentation (ie, id=bot-… with class colomat-close) and they work great with normal expand actions. But, when using collapse-all, for some reason the colomat-close class is getting removed from these bottom close triggers every time collapse-all is clicked – the result is that after expanding normally following a collapse-all, the bottom trigger arrow png was pointing the wrong way (ie, down for open, not up for close as it should be) Again I used jQuery to work around this by adding back the colomat-close class to elements with id containing “bot-” anytime collapse-all span is clicked (after a short time delay to allow the plugin to do its mysterious removal of this class before my jQ would restore it)

So, with the above workarounds, I seem to have things behaving the way I want, but I’d be interested if you find anything or have any further insights on these items. My site is in private devel so no readily available link, but if you are unable to reproduce, I may be able to provide access for you to take a look at the behavior.