8375 2009-11-25 12:46:24 +0000 Mention that when in "in select in table", there is always a "select" element in table scope 2011-04-20 09:04:46 +0000 1 1 1 Unclassified HTML WG pre-LC1 HTML5 spec (editor: Ian Hickson) unspecified PC All RESOLVED NEEDSINFO P3 normal --- 1 hsivonen ian brunoaiss ian mike mjs public-html-admin public-html-wg-issue-tracking public-html-bugzilla oldest_to_newest 29730 0 hsivonen 2009-11-25 12:46:24 +0000 It seems to me that a start tag for CAPTION, TBODY, THEAD, TFOOT, TR, TD, TH, TABLE in 'in select in table' causes an infinite loop in the fragment case when there's no <select> in table scope, because the "as if" </select> doesn't change any state before the token is reprocessed. Maybe it's impossible to reach this state in the fragment mode. If that's the case, the assertion about fragment mode in the spec should be replaced with a "this can't happen" assertion. 30616 1 hsivonen 2010-01-06 09:29:44 +0000 Sorry about the bad bug report. I inlined the bit from "An end tag whose tag name is "select"" from "in select" into the "Act as if an end tag with the tag name "select" had been seen" part of "in select in table". This resulted in a non-sensical "(fragment case)" assertion, but as a result of inlining, it isn't really a spec bug. It would be nice to mention that it's impossible to reach "in select in table" without having a "select" element in table scope, though. (If that's true!) 31509 2 ian 2010-02-05 20:43:23 +0000 Am I correct in assuming that > It would be nice to mention that it's impossible to reach "in select in table" > without having a "select" element in table scope, though. (If that's true!) ...is the only request here? If so it would be helpful to understand where such a mention should be placed. 31615 3 mjs 2010-02-07 07:01:27 +0000 Marking this NEEDSINFO since Ian asked for info. Henri, I hope you're ok with this lacking the formal response template.