This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 2874 - unparsed-text and unparsed-text-available not repeatable
Summary: unparsed-text and unparsed-text-available not repeatable
Status: CLOSED FIXED
Alias: None
Product: XPath / XQuery / XSLT
Classification: Unclassified
Component: XSLT 2.0 (show other bugs)
Version: Candidate Recommendation
Hardware: PC All
: P4 minor
Target Milestone: ---
Assignee: Michael Kay
QA Contact: Mailing list for public feedback on specs from XSL and XML Query WGs
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2006-02-13 08:39 UTC by Colin Adams
Modified: 2006-03-22 22:38 UTC (History)
0 users

See Also:

Attachments

Description Colin Adams 2006-02-13 08:39:05 UTC 
I have just realised that unparsed-text is not guarenteed to return the same
text for the same argument, if called twice.
Likewise, unparsed-text-available is not guarenteed to return the same answer
twice, for the same argument.

This is inconsistent with the document() function.

I'm not claiming this is a bug necessarily. Just checking that this is the
intended behaviour.
Comment 1 Michael Kay 2006-02-17 18:35:06 UTC 
The XSL Working Group reviewed this comment on 16 Feb 2006 and agreed to make
the proposed change. The unparsed-text() and unparsed-text-available() functions
will therefore be brought into line with document() and other similar functions
as regards the need for stability. Note that an earlier decision of the working
groups has relaxed the requirement for stability of all these functions: they
are now stable by default, but implementors are allowed to provide options for
users to select a reduced level of isolation.

I am marking this as FIXED, and if you are happy with this disposition, please
mark it as CLOSED.

Thank you for raising the comment.

Michael Kay
for the XSL Working Group