Closed Bug 561785 Opened 15 years ago Closed 12 years ago

Make E4X XML objects non-native

Categories

(Core :: JavaScript Engine, defect)

Product:
Core
Component:
JavaScript Engine
Version:
Other Branch
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED WONTFIX

People

(Reporter: jorendorff, Unassigned)

References

Details

For sanity's sake, as proposed in bug 560101 comment 8. It seems like the complications would be the js_GetXMLMethod machinery, class initialization, and the function:: namespace, because all three involve ordinary non-E4X-magic properties. I think those could be implemented by giving each XML object, lazily, a proto-less plain old JSObject to use as backing store. js_GetXMLMethod might end up being a total rewrite, but it's worth it.
xml objects being native but not really makes the iteration code pretty ugly. Fixing this will allow us to remove some cruft there.
Plan is to do this via bug 485791. /be
Depends on: 485791
e4x is being removed (bug 788293).
Status: NEW → RESOLVED
Closed: 12 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.