[TIMOB-9278] IOS XML Limitations
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | Low |
| Status | Closed |
| Resolution | Won't Do |
| Resolution Date | 2020-01-09T22:02:43.000+0000 |
| Affected Version/s | n/a |
| Fix Version/s | n/a |
| Components | iOS |
| Labels | api |
| Reporter | Vishal Duggal |
| Assignee | Unknown |
| Created | 2012-05-25T11:45:06.000+0000 |
| Updated | 2020-01-09T22:02:43.000+0000 |
Description
IOS has a lot on limitations in the XML implementation. It is a partial DOM2 implementation.
It has no DTD support so notations, entities, entity references may not work at all. Also node mutation is only supported on the Ti.XML.Element so the following methods -
appendChild, removeChild, insertBefore and replaceChild, although defined for type Ti.XML.Node will only work for Ti.XML.Element. They will throw an exception on all other kinds of nodes.
The prefix property for type Ti.XML.Node is read-write by definition but IOS defines it as read-only.
The method normalize is not implemented in IOS.
This has been open for 4 months and was first noted in the commonity QA one year ago. Why is there no response? I've created a ticket for support based on this same issue. http://support.appcelerator.com/tickets/APP-971557
This issue is out of date with our current supported SDK release (7.5.2.GA as of the date of closure), and out of date with mobile OS versions. If community members feel that the issue is still valid, please create a new ticket. Please reference this closed ticket number, include SDK used, comments, and code that demonstrates/reproduces the issue.