W3C home > Mailing lists > Public > public-qt-comments@w3.org > March 2014

[Bug 24551] Enhancement: a function for getting the base output uri

From: <bugzilla@jessica.w3.org>
Date: Wed, 26 Mar 2014 18:22:13 +0000
To: public-qt-comments@w3.org
Message-ID: <bug-24551-523-wXpNcPnmNb@http.www.w3.org/Bugs/Public/>
https://www.w3.org/Bugs/Public/show_bug.cgi?id=24551

--- Comment #4 from Abel Braaksma <abel.braaksma@xs4all.nl> ---
We also say about a primed stylesheet that all global variables, function
invocations and stylesheet parameters remain stable. Hence, when you evaluate a
primed stylesheet multiple times, you cannot change a stylesheet parameter.

I think there is a difference between compiling a stylesheet and priming a
stylesheet. When you compile a stylesheet, stylesheet parameters and other
environmental information remain volatile, they can change for each invocation
of the compiled stylesheet. A primed stylesheet on the other hand, has its
global variables and stylesheet parameters fixed.

In fact, I don't think there is a problem with (potential) stability of
fn:base-output-uri(), not more than there is for fn:system-property() or
fn:environment-variable(). The functions are stable after priming, but not
after compiling (a phase that is not defined in the spec). Currently there is
nothing in the spec that says that the Base Output URI can change on multiple
evaluations of a primed stylesheet, but frankly, I think it shouldn't.

On a new fn:current-mode(), I concur ;), but other than fn:base-output-uri(),
this cannot be a static function.

-- 
You are receiving this mail because:
You are the QA Contact for the bug.
Received on Wednesday, 26 March 2014 18:22:17 UTC

This archive was generated by hypermail 2.4.0 : Friday, 17 January 2020 16:57:46 UTC