Last modified: 2012-03-13 21:48:22 UTC
Created attachment 10222 [details] How the bug displays I have been trying to develop an extension allowing for a more detailed and enhanced transclusion feature, among other things. It involves certain new tags, such as 'section'. I am aware that this tag is already defined in HTML5, but the problem persisted when it was changed to a different name. Apparently, there is a problem with the detection of nested tags. To illustrate this, consider the following wikitext (which renders as seen in the attachment): #start sample <section title="Test" headerlevel="2" name="testing">This is a test</section> <section name="name">This is a test <section name="sub">What should be a subsection</section> Some further text </section> #end sample As one sees, the parser handles perfectly the case where there is no nesting. But then the second section, containing the subsection, apparently greedily takes the first '/section' tag as its endpoint, while this is obviously not how HTML should be read. After a whole weekend, I decided to ask help here as I couldn't figure it out myself. Thanks in advance.
Having verified the persistence of the bug in various cases, I deem it appropriate to call this a 'new' rather than 'unconfirmed' bug.
Extension tag hooks cannot be nested (not that parser functions *can* be nested.) Duping this to classic bug 1310 where there's also some more recent discussion. *** This bug has been marked as a duplicate of bug 1310 ***
not that -> note that :P :)
