hey sanford. yeah i checked out your fiddle, thanks. it worked nice but i have to come up with a solution that works in ie - which is also the answer to your question of why i went back to 1.2...
i wasn´t sure how serious the "1.3 Core/More loading problem before the XHR even fires" issue is (or what exactly the exactly issue is in the first place) but i needed a solution asap so i went back to 1.2 and then got forced into my dumb attribute selector. needless to say i am not pleased with my solution. i hope to fix it, and go back to slick, once i get passed my deadline (tomorrow). all that being said. what exactly is the the loading problem with 1.3 core/more? sadly i need to worry about ie in almost all my projects. cheers.b On Jul 21, 2:38 pm, Sanford Whiteman <[email protected]> wrote: > > since these werent added to the page the "class" was messing things > > up. > > Maybe it was optimized to native getElementsByClassName, which won't > work outside the DOM; likewise, getElementById is for the true DOM ID > type attribute. But [id=idname] is a "dumb" attribute selector that > will work on an island. > > Did you look at my Fiddle? I was using real XML, not HTML. I'm > confused about your switch back to 1.2 -- how is that using Slick? > > -- S.
