2009/9/20 Robert Rohde rarohde@gmail.com:
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.
What's the actual use case for nested refs? (Do you have an example page or two where they're useful and there's no way to do it right without nesting the refs?)
- d.