comment on

Actually your approach is better to see whitespaces and linebreaks directly inside the browser, since the XML view in FF doesn't show it.

FWIW here a nodelet hack which opens a JS.alert() with the HTML of the post you are trying to reply to.

<script><!--
function show_quote() {
alert(document.querySelector("div.preview").innerHTML.match(/^[^]*?(?=
+<hr> <div class="editnodetext">)/)[0]);
}
--></script>

<a href='javascript:show_quote()'> show_quote</a>
[download]

(you need to be in a "comment on" node to make it work)

it was part of my plans to extend my wiki-syntax with comfortable quoting of a users post...

... of course milking the XML-displaytype would be more reasonable here.

Cheers Rolf
_{(addicted to the Perl Programming Language and ☆☆☆☆ :)

Je suis Charlie!}

In reply to Re^2: How to get raw node content (whitespace and nodelet hack) by LanX
in thread How to get raw node content by roboticus

Are you posting in the right place? Check out Where do I post X? to know for sure.
Posts may use any of the Perl Monks Approved HTML tags. Currently these include the following:
<code> <a> <b> <big> <blockquote> <br /> <dd> <dl> <dt> <em> <font> <h1> <h2> <h3> <h4> <h5> <h6> <hr /> <i> <li> <nbsp> <ol> <p> <small> <strike> <strong> <sub> <sup> <table> <td> <th> <tr> <tt> <u> <ul>
Snippets of code should be wrapped in <code> tags not <pre> tags. In fact, <pre> tags should generally be avoided. If they must be used, extreme care should be taken to ensure that their contents do not have long lines (<70 chars), in order to prevent horizontal scrolling (and possible janitor intervention).
Want more info? How to link or How to display code and escape characters are good places to start.


"be consistent"
	PerlMonks