Closed Bug 65981 Opened 24 years ago Closed 8 years ago

Need to implement the unparsed-entity-uri() XSLT function

Categories

(Core :: XSLT, defect, P4)

defect

Tracking

()

RESOLVED WONTFIX
Future

People

(Reporter: peterv, Assigned: peterv)

References

(Depends on 1 open bug)

Details

Attachments

(2 files)

We need to implement the unparsed-entity-uri() XSLT extension function (http://www.w3.org/TR/xslt.html#function-unparsed-entity-uri) in Transformiix.
Summary: Need to implement the current() XSLT function → Need to implement the unparsed-entity-uri() XSLT function
Blocks: 63906
Target Milestone: --- → mozilla0.8
i should be able to do this...
Assignee: peterv → dr
accepting. the relevant info is at: http://www.w3.org/TR/xslt.html#function-unparsed-entity-uri http://www.w3.org/TR/xslt#unparsed-entities http://www.w3.org/TR/REC-DOM-Level-1/level-one-core.html#ID-527DCFF2 this should all be straightforward, except potentially for resolving relative vs. absolute uris. should be able to figure that out too, or at least get it mostly working.
Status: NEW → ASSIGNED
Priority: -- → P3
Pushing back due to lacking support in the mozilla DOM, bug 67784 filed and added to dependencies. Axel
Depends on: 67784
Target Milestone: mozilla0.8 → mozilla0.9
Pushing to sicking -- sorry for the delay, I need to focus more on toolkit priorities for the moment. Let me know what needs to be done with bug 67784.
Assignee: dr → sicking
Status: ASSIGNED → NEW
waaaah!!! why did *I* get this?!? Ok accepting for now, I actually think i know how to do it. I'll give it a try
Status: NEW → ASSIGNED
That's the downside of being an active contributor! ;-)
the applied patch *should* work but i'm currently blocked by bug 71686 so I cant really test it
still blocked by bug 71686... pushing to 0.9.1
Target Milestone: mozilla0.9 → mozilla0.9.1
removing milestone since this is still blocked by bug 71686
Target Milestone: mozilla0.9.1 → ---
No longer blocks: 63906
Priority: P3 → P4
Target Milestone: --- → mozilla1.1
Target Milestone: mozilla1.1 → Future
When this bug is fixed we should remove the code in ExprParser that deals with aContext->resolveFunctionCall returning NS_ERROR_NOT_IMPLEMENTED
reassining bugs i'm not working on to default owner
Assignee: bugmail → peterv
Status: ASSIGNED → NEW
QA Contact: keith → xslt
Here is a test case showing the possibilities when this issue gets resolved. http://araneda.web44.net/books.xml This is redered fine with Internet Explorer and Opera
Status: NEW → RESOLVED
Closed: 8 years ago
Resolution: --- → WONTFIX
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: