Interesting; that works for IE8, but not IE9: http://jsfiddle.net/HVSQZ/1/
I'm I've hit issues with IE treating XML islands as non-element nodes before; are you aware of anyone have dealt with a cross-browser treatment of XML parsing? If not, I'll take a stab at it. Thanks, Eric On Jul 6, 12:47 pm, Fábio M. Costa <[email protected]> wrote: > Eric, > > Looks like the xml node is not extendable, making it impossible to select it > by id or anything else, just like what happens with the object and applet > nodes. > > Using like this, works: > > alert(Slick.search(Slick.find(document, '#Config'), 'Testing > > test').length); > > -- > Fábio Miranda Costa > frontend@portalpadroes > Globo.com > *github:* fabiomcosta > *twitter:* @fabiomiranda > *ramal:* 6476 > > > > > > > > On Wed, Jul 6, 2011 at 1:16 PM, Eric Patrick <[email protected]> wrote: > > I am trying to parse an XML document using Slick. > > >http://jsfiddle.net/HVSQZ/ > > > Results: expected a length of 2 from the array returned by > > Slick.search(): > > > - Chrome, Safari, FF: returns 2 (expected) > > - IE 9: returns 0 > > - IE 8: raises an error on page load (seems to be a 1.3.2 issue?) > > > Suggestions on what I'm doing wrong, or a workaround? > > > Eric Patrick
