Closed Bug 270779 Opened 21 years ago Closed 7 years ago

[TRACKER] Open E4X issues in Rhino 1.6R1

Categories

(Rhino Graveyard :: E4X, defect, P5)

Product:
Rhino Graveyard
Component:
E4X
Platform:
x86
Linux
Type:
defect

Tracking

(Not tracked)

Status:
RESOLVED INACTIVE

People

(Reporter: igor, Unassigned)

References

Details

This is a meta bug to track E4X issues in Rhino 1.6R1
Here is a list of known issues with E4X implementation in Rhino 1.6R1 at the release time: [Bug 257679] Standalone <![CDATA[ .... ]]> or <?...> should be allowed [Bug 263934] XMLList assign produces bogus result [Bug 263935] Bogus namespace match with qualified name [Bug 263936] Bogus list element replace [Bug 264369] Escaping of '>' not compliant with 10.2.1.1 of ECMA 357
Depends on: 257679
Depends on: 277935, 278112
New entries: [Bug 277935] Assignments to descendants like "msg..s = something" => failed assert [Bug 278112] setNamespace() should not affect namespaceDeclarations()
[Bug 277537] isXMLName() should be properly implemented
Depends on: 277537
Reassigning to please_see_bug_288433@eml.cc pending resolution of bug 288433
Assignee: igor.bukanov → please_see_bug_288433
Assignee: please_see_bug_288433 → nobody
Summary: Open E4X issues in Rhino 1.6R1 → [TRACKER] Open E4X issues in Rhino 1.6R1
Changing priority to P5 based on recent bug triage.
Priority: -- → P5

Closing. Bug management is now done here:
https://github.com/mozilla/rhino

Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → INACTIVE
You need to log in before you can comment on or make changes to this bug.