On Wed, 15 Nov 2006 11:17:48 -0500, Steve Sanbeg wrote:
On Wed, 15 Nov 2006 21:15:19 +1100, Nick Jenkins wrote:
[snip]
I've had a second quick look, and something separate is this:
In [[Main Page]] I have a bit of the page that contains:
<section begin=ownage /> <script>alert("Ownage!");</script> <section end=ownage /> ------------------------------------
Then in another page I have:
{{#lst:Main Page|ownage}}
The result is that on saving or previewing that page, I get a JavaScript popup dialog box saying "Ownage!". That should not happen; instead what I should get is the following non-executable HTML in the output:
<p><script>alert("Ownage!");</script> </p> ------------------------------------
Related to this and probably the same issue, is that if there is an image <gallery> wrapped in <section> tags, then the image gallery should display on the page that includes it via the {{#lst)).
All the best, Nick.
Oh, that's not good. Setting noparse=>false in the return will fix that, but will also cause it to change the edit section links to point to the main document. I expect there's no way to get those right and resolve the edit sections correctly without some enhancement to the parser, such as allowing the parser function to return a title, or call back into the extension when it's done parsing.
Although at least that doesn't change the syntax, like when this enhancement was hooked directly into the parser, so maybe that could be done.
Thanks -Steve
OK, I seem to have found a better hook for the recursive parsing (as well as a competent newsreader), so we may be back in business. The new version seems to address these issues.
Thanks much! -Steve