Adoption Agency Algorithm: limits lead to out-of-logical order insertions

>From bug https://www.w3.org/Bugs/Public/show_bug.cgi?id=20319

(Repeating on this list to get a broader set of eyes/thoughts on this topic)

Issue: this input to the parser "<b><i><a><s><tt><div></b>first</b></div></tt></s></a>second</i>" results in rendering:
second
first

See also: http://html5.org/tools/web-apps-tracker?from=5641&to=5642

It seems a little weird to want to "fix" this bug when all of the major recent browsers are 100% consistent on their parsing behavior in this scenario--e.g., we've successfully achieved an interoperable HTML5 parser!

What's so bad about leaving the current limits in place? I.e., is there a site compatibility bug that is motivating this change, or is it simply altruistic? The linked bug above describes "practical limits" for the AAA which seem to have resulted in this problem. Yet, if this isn't really a "problem" for web content somewhere, then why fix it?

My inclination is to Won't Fix this bug and call this an interesting anomaly of the AAA (and move on). There's enough other bizarre features of the HTML5 parser that I'm pretty comfortable with that idea.