The XSLT function unparsed-entity-uri() needs mozilla to handle unparsed entities like in the following xml: <?xml version="1.0"?> <!DOCTYPE doc [ <!NOTATION gif SYSTEM "../www.foo.com" > <!ENTITY hatch-pic SYSTEM "../grafix/OpenHatch.gif" NDATA gif > <!ELEMENT doc (#PCDATA)> ]> <doc> </doc> We currently only get a NS_NOTYETIMPLEMENTED("Error: nsExpatTokenizer::HandleUnparsedEntityDecl() not yet implemented."); I'm not too sure, what's supposed to be in the DOM for this, any tips?
This is heikki's realm.
Assignee: harishd → heikki
heikki: this blocks 65981 (moz0.9), which is required for xslt conformance. (sorry to bother you, just checking up on my 0.9 bugs). let me know how i can help.
Dan, I have currently about maxed bug buckets for 0.9 and 0.9.1, so if you can take this it would be great. I am tentatively reassigning this to you. So anybody got any ideas what should be in the DOM in this case?
Assignee: heikki → dr
I don't see anything weird about this from a DOM point of view, the document should contain a DocumentType that contains the entity and the notaion declared in the internal subset, did I miss something, or is that it?
tentatively accepting this, but futured. i know xslt needs this for conformance in 0.9, but let me know what priority this really is. (in my experience with xslt, i've never had to use the unparsed-entity-uri() function...)
Status: NEW → ASSIGNED
Component: Parser → XML
Priority: -- → P4
Target Milestone: --- → Future
not mine, handing off to petersen
QA Contact: janc → petersen
over to peterv, who will probably be able to do this sometime in the forseeable future ;)
Assignee: dr → peterv
Status: ASSIGNED → NEW
You need to log in before you can comment on or make changes to this bug.