22025 2013-05-14 04:19:50 +0000 For <menuitem>, "in body" mode redirects to "in head", which will cause an infinite loop. 2013-05-28 22:57:20 +0000 1 1 1 Unclassified WHATWG HTML unspecified Other other RESOLVED FIXED http://www.whatwg.org/specs/web-apps/current-work/#parsing-main-inbody P3 blocker Unsorted 1 contributor ian geoff ian mike mikeday contributor oldest_to_newest 87625 0 contributor 2013-05-14 04:19:50 +0000 Specification: http://www.whatwg.org/specs/web-apps/current-work/multipage/tree-construction.html Multipage: http://www.whatwg.org/C#parsing-main-inbody Complete: http://www.whatwg.org/c#parsing-main-inbody Referrer: http://www.whatwg.org/specs/web-apps/current-work/multipage/ Comment: For <menuitem>, "in body" mode redirects to "in head", which will cause an infinite loop. Posted from: 110.142.158.46 User agent: Mozilla/5.0 (X11; Ubuntu; Linux x86_64; rv:20.0) Gecko/20100101 Firefox/20.0 87939 1 geoff 2013-05-20 23:55:27 +0000 I've got the same problem. After bringing my parser up to date with the relevant changes, I got an infinite loop parsing a <menuitem> start tag. The spec change that caused this is in http://html5.org/r/7640 There are two places where the old <command> element was listed as a start tag to match in a state ("in head", and "in body"). The change renamed it to <menuitem> in the latter, but just removed it from the first. (There was a third list which is commented out.) I think we need <menuitem> added to that list in the "in head" insertion mode. 88322 2 ian 2013-05-28 22:55:55 +0000 Woops. I wasn't paying enough attention there. Fixed, I think. 88324 3 contributor 2013-05-28 22:57:20 +0000 Checked in as WHATWG revision r7871. Check-in comment: <menuitem> parsing bug http://html5.org/tools/web-apps-tracker?from=7870&to=7871