I am looking at bug 1310, which involves parser behavior such that
when given nested tag extensions, i.e.:
<tag>
AAA
<tag>BBB</tag>
CCC
</tag>
The parser selects the tag block as running from the first open tag to
the FIRST close tag, i.e. in the example it gives:
AAA
<tag>BBB
as the inner text of the first tag. It should be fairly
straightforward to modify this to handle nested tags by checking for
additional open tags in the inner string.
However, since this is parser behavior going back to the dawn of time
(first reported in MW 1.4), I wanted to ask if there are known use
cases where the current behavior is actually the expected behavior?
In other words, are there any use cases in the current code base or
extensions that would necessarily break if the parser were changed to
allow nested tags? I can't think of any right now, but I wouldn't
want to modify an old parser quirk without giving it a good look. For
the record, my particular interest is related to nested refs.
-Robert Rohde