Subject: Re: [xsl] Unexpected result from <a href="...">...</a> in some cases From: Quinn Taylor <quinntaylor@xxxxxxx> Date: Tue, 19 Aug 2008 21:02:56 -0600 |
What result to you expect for your test string "/path/to/resource"?
<a href="../../../">[root]</a> / <a href="../../">path</a> / <a href="../">to</a> / resource
What result to you expect for "/to/resource"?
<a href="../../">[root]</a> / <a href="../">to</a> / resource
What result to you expect for "/resource"?
<a href="../">[root]</a> / resource
Got it.
I also got lost in your code with the definition of the variable "recursiveResult" and pulling it apart again ... I couldn't see why the variable would be necessary and not just generate each step as required.
Below is what I think is a complete result, without the need for such a variable. I've tried to document it to explain the approach.
I hope this helps.
. . . . . . . . . . . Ken
<snip>
Current Thread |
---|
|
<- Previous | Index | Next -> |
---|---|---|
Re: [xsl] Unexpected result from <a, G. Ken Holman | Thread | Re: [xsl] Unexpected result from <a, Quinn Taylor |
Re: [xsl] Unexpected result from <a, G. Ken Holman | Date | Re: [xsl] Unexpected result from <a, Quinn Taylor |
Month |