10617 2010-09-12 23:14:05 +0000 I believe <kbd><table></kbd> gets the parsing algorithm into a bad state. When we see </kbd> we process it using the rules for "any other end tag" of the inbody mode, which pops off the table and the kbd element from the stack of open elements. However, 2010-12-01 15:30:43 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified Other other VERIFIED INVALID http://www.whatwg.org/specs/web-apps/current-work/#isindex P3 normal --- 1 contributor ian eric hsivonen mike Ms2ger public-html-admin public-html-wg-issue-tracking w3c public-html-bugzilla oldest_to_newest 38946 0 contributor 2010-09-12 23:14:05 +0000 Section: http://www.whatwg.org/specs/web-apps/current-work/#isindex Comment: I believe <kbd><table></kbd> gets the parsing algorithm into a bad state. When we see </kbd> we process it using the rules for "any other end tag" of the inbody mode, which pops off the table and the kbd element from the stack of open elements. However, we remain in the InTableBody insertion mode, which cases disaster as we're no longer in a table. Posted from: 67.169.42.39 by w3c@adambarth.com 38947 1 w3c 2010-09-12 23:20:47 +0000 Minefield appears to ignore the </kbd>, at least in the examples I've looked at. 38948 2 w3c 2010-09-12 23:36:36 +0000 My mistake. It appears table is in this list http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#special