This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 10617 - 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,
Summary: I believe <kbd><table></kbd> gets the parsing algorithm into a bad state. Wh...
Status: VERIFIED INVALID
Alias: None
Product: HTML WG
Classification: Unclassified
Component: pre-LC1 HTML5 spec (editor: Ian Hickson) (show other bugs)
Version: unspecified
Hardware: Other other
: P3 normal
Target Milestone: ---
Assignee: Ian 'Hixie' Hickson
QA Contact: HTML WG Bugzilla archive list
URL: http://www.whatwg.org/specs/web-apps/...
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2010-09-12 23:14 UTC by contributor
Modified: 2010-12-01 15:30 UTC (History)
7 users (show)

See Also:

Attachments

Description contributor 2010-09-12 23:14:05 UTC 
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
Comment 1 Adam Barth 2010-09-12 23:20:47 UTC 
Minefield appears to ignore the </kbd>, at least in the examples I've looked at.
Comment 2 Adam Barth 2010-09-12 23:36:36 UTC 
My mistake.  It appears table is in this list http://www.whatwg.org/specs/web-apps/current-work/multipage/parsing.html#special