9 Answers

• I again confirm. A slightly different issue: TiDOMNodeList.item(int index) errors out. Try pasting this at line 113 in examples/xml_dom.js in Kitchen Sink 1.1.x:

  112:  elements = nodes.item(0).childNodes;
  113:  result = result && (elements!=null && elements.length==3);
  #new code
  Titanium.API.debug(elements);
  Titanium.API.debug(typeof elements.item);
  Titanium.API.debug(elements.item(0).nodeName);
  

  Outputs:

  [DEBUG] [object TiDOMNodeList]
  [DEBUG] function
  [DEBUG] Was set was set to 1
  2010-03-24 12:03:01.649 KitchenSink[63649:854f] *** -[TiDOMElementProxy kind]: unrecognized selector sent to instance 0x5375080
  [ERROR] Script Error = *** -[TiDOMElementProxy kind]: unrecognized selector sent to instance 0x5375080 at xml_dom.js (line 116).
  

• it also seems as though with 1.1.2 android is not parsing CDATA wrappers correctly.

• I can confirm this issue. My application which parses feeds now displays the feed <title> rather than the <item>'s <title>. Worked fine in 1.0 but not 1.1.0.

• Yea, my app's xml parsing is toast under 1.1 iPhone BUT it still works ok on the Android.

• Having the same problem and reported separately:

  http://developer.appcelerator.com/question/6001/trouble-parsing-xml-since-upgrading-to-110

  Even the example in Kitchen Sink 1.1.0 fails to parse correctly. :(

• Ditto. All broken for me as well. I can retrieve attributes of nodes OK. If I am looping through a node list and using firstChild,lastChild for referencing nodes in the loop it's fine, but trying to use getElementsByTagName on any node I'm looking on (say if I am looking for a set of child nodes in th current node), just returns the first node every time.

• We're working on a fix. We're likely to do a 1.1.1 maintenance push to resolve these and other critical issues found ASAP.

• This is still broken in 1.2.0 for the iPhone.

• This is still broken in 1.2.0 for the iPhone.