[TIMOB-6534] Android: Rhino: Drillbit test for XML fails
| GitHub Issue | n/a |
|---|---|
| Type | Bug |
| Priority | High |
| Status | Closed |
| Resolution | Fixed |
| Resolution Date | 2012-02-14T23:29:03.000+0000 |
| Affected Version/s | Release 1.8.0 |
| Fix Version/s | Sprint 2012-03, Release 2.0.0, Release 1.8.2 |
| Components | Android |
| Labels | n/a |
| Reporter | Opie Cyrus |
| Assignee | Ping Wang |
| Created | 2011-12-09T11:12:37.000+0000 |
| Updated | 2012-02-14T23:29:03.000+0000 |
Description
Running the XML drillbit test under Rhino will result in a failure for the last two tests. Results from a recent update for the XML element tests.
NOTE: remove the !android checks put in with TIMOB-6627
There are two failures in xml.js. 1) line 1284. It throws DOMException with error code INUSE_ATTRIBUTE_ERR which is raised if newAttr is already an attribute of another Element object. The DOM user must explicitly clone Attr nodes to re-use them in other elements. It should not throw exception because this test is replacing an attribute node by itself and it should has no effect based on the doc http://developer.android.com/reference/org/w3c/dom/Element.html#setAttributeNode(org.w3c.dom.Attr). 2) line 1372. It throws the same exception as above. Based on the JS code, throwing the exception is expected. But the odd thing is in this test, it uses setAttributeNodeNS and setAttributeNode for the same attribute node.
We need a test "if (!android)" only for 1_8_X to verify we're running the rest of the XML drillbit tests. Do not resolve for 1_8_x merge
Failed: Tested XML with drillbit using: version=1.9.0 module_apiversion=2 timestamp=01/23/12 15:04 githash=72b3e82 fails to run
XML test passes using latest master on HTC 2.3.4 phone.
Retested with version=1.9.0 module_apiversion=2 timestamp=01/23/12 15:04 githash=72b3e82 with rhino and emulator 2.2 all test passed