On Saturday, June 20, 2015 at 10:23:19 AM UTC+2, Felix Küppers wrote: > > Walking up the dom-node tree and checking for a class is a nice idea. I > initially wanted to extract the information from the widget tree but your > idea is way easier. > If there is no better solution, I'll go with your suggestion! Thanks! >
I actually didn't suggest, to walk the browser DOM tree. I did suggest, that you only need to go up 2 parent nodes. IMO the widget gets a reference to the parent, and the nextSibling. So this should be every thing you need. Since TW builds the DOM from the widget tree, I used the DOM to find some info, that we can use. -m -- You received this message because you are subscribed to the Google Groups "TiddlyWikiDev" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/tiddlywikidev. To view this discussion on the web visit https://groups.google.com/d/msgid/tiddlywikidev/f8c75a07-39cc-4222-9931-2e6c3145584f%40googlegroups.com. For more options, visit https://groups.google.com/d/optout.
