Samuel Baldus

Try this:

//content-node/@comment

You don't need to use ancestor.

Lovely, thanks Paul.

Ah, hold on.

That parses all comments into each segment:

Is it possible to only show the relative parent node comment? 

Lovely, thanks Paul.

Ah, hold on.

That parses all comments into each segment:

Is it possible to only show the relative parent node comment? 

Samuel Baldus

That's funny... I actually raised a support ticket for this very thing when I tested this for you earlier!  I also tried using this:

//text-node/../@comment

Just in case it helped to keep the focus on the text node selected and traverse back up to the parent content-node for the comment, but that gives me the same problem.  Unless Patrik Mazanek has some idea of what could be used here I think think we'll need to wait for a comment from the support team.

As a workaround you could try making this part of the DSI info and then see the comments with the DSI Viewer, or in the navigation pane... or even better just create a simple stylesheet to preview them as you work.

PaulSamuel Baldus

You are getting these results because you not referencing your XPath expression of the current node.

Nice!

Makes sense since I should have not used a relative path indeed.  But I'm still not sure why I cannot make this work with an absolute path instead as opposed to traversing.

Glad you took another look look at this though.  Thank you!

Paul

Well, the XPath expression will match everything that is //text-node/../@comment, which means it matches all comments. I am not the great XPath guru, but from my understanding I would say that this kind of expression has to start "here", which is . or ..

Unknown said:

I am not the great XPath guru

Me neither!

But that would be a relative path which I noted I should not have used.  I didn't understand why this wouldn't work for example, /text-node/../@comment or /content-node/@comment.  But the more I think about it the less I understand my own reasoning!

Unknown said:

I would say that this kind of expression has to start "here"

I think this is best way to look at it indeed!