This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.
Specification: https://html.spec.whatwg.org/multipage/syntax.html Multipage: https://html.spec.whatwg.org/multipage/#concept-parser-marker Complete: https://html.spec.whatwg.org/#concept-parser-marker Referrer: Comment: A marker is not inserted when entering button [[ The markers are inserted when entering applet elements, buttons, ... ]] As far as I can tell the parser doesn't say "insert a marker" for <button>. Posted from: 90.230.218.37 by simonp@opera.com User agent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_10_2) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/42.0.2311.60 Safari/537.36 OPR/29.0.1795.30 (Edition beta)
I'll check more carefully when I get to this bug, but off hand, do you think this should be fixed by adding a marker or by fixing the note? I'm guessing the note...
I'd guess that as well but I don't know how to test this exactly
https://html.spec.whatwg.org/multipage/syntax.html#adoption-agency-algorithm step 5 [[ Let formatting element be the last element in the list of active formatting elements that: is between the end of the list and the last marker in the list, if any, or the start of the list otherwise, and has the tag name subject. If there is no such element, then abort these steps and instead act as described in the "any other end tag" entry above. ]] so <b><object></b>x has a marker, so </b> is handled like "any other end tag". vs <b><button></b>x has no marker, so AAA reparents. http://software.hixie.ch/utilities/js/live-dom-viewer/saved/4049
Tested by https://github.com/html5lib/html5lib-tests/blob/6234baeabc51f6d51d1cfc2c4e4656bd99531f2b/tree-construction/adoption01.dat#L30
<template> does insert a marker but was not mentioned. Also don't see a test for that in html5lib-tests.
https://github.com/whatwg/html/pull/1036
https://github.com/html5lib/html5lib-tests/issues/73