Closed
Bug 1145969
Opened 9 years ago
Closed 3 years ago
[HTML5] successive tags of type command get nested
Categories
(Core :: DOM: HTML Parser, defect, P5)
Tracking
()
RESOLVED
INVALID
People
(Reporter: gorgonz, Unassigned)
Details
Attachments
(2 files)
User Agent: Mozilla/5.0 (X11; Linux x86_64; rv:36.0) Gecko/20100101 Firefox/36.0 Build ID: 2015022000 Steps to reproduce: FF 36.0 OS: OpenSUSE 13.1 64bit played around with html5 tags and used 3 tags of type menu successively, each with closing "/". Actual results: FF will nest them, also seen with firebug Expected results: There should have been 3 menu tags next to each other, especially, since i added the display: block attribute. Of course, I'm an early adapter, but this is a structural error ;-)
Reporter | ||
Updated•9 years ago
|
Summary: [HTML5] successive tags of type menu get nested → [HTML5] successive tags of type command get nested
Reporter | ||
Comment 1•9 years ago
|
||
sorry not the menu tag gets nested, but the command tag
Reporter | ||
Comment 2•9 years ago
|
||
Some hints: - using a closing command tag instead will solve the problem - the command tags have no height, I must enforce it with height attribute - using text between opening and closing command tag will give height
Comment 3•3 years ago
|
||
Bulk-downgrade of unassigned, >=5 years untouched DOM/Storage bugs' priority.
If you have reason to believe this is wrong (especially for the severity), please write a comment and ni :jstutte.
Severity: normal → S4
Priority: -- → P5
Reporter | ||
Comment 4•3 years ago
|
||
just walking through my old bugs to see, what might be able to get state "closed".
This one is not a big deal and needs no big priority. Only nasty thing is: "After" this tags the parser structure is broken until another closing tag helps to synchronize parsing again.
In order to see it in a detailed way I will add a screenshot of the parsers "red colored" characters, that shows the structure problem best, seen with ff 87.0b7
Reporter | ||
Comment 5•3 years ago
|
||
Reporter | ||
Comment 6•3 years ago
|
||
Ok, gave a try to the docs, result="The <command> element has now been dropped from the HTML5 specification"
will close this one
Status: UNCONFIRMED → RESOLVED
Closed: 3 years ago
Resolution: --- → INVALID
You need to log in
before you can comment on or make changes to this bug.
Description
•