Closed
Bug 571700
Opened 14 years ago
Closed 14 years ago
Use of <strong/> tag without proper open and close tags break rendering after it
Categories
(Core :: DOM: HTML Parser, defect)
Tracking
()
VERIFIED
INVALID
People
(Reporter: mozbugz, Unassigned)
References
Details
Attachments
(2 files)
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a6pre) Gecko/20100611 Minefield/3.7a6pre Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.3a6pre) Gecko/20100611 Minefield/3.7a6pre Use of <strong/> still allows the text to be bold after it. Though the proper use of <strong> </strong> should be used. Testcase coming up. Reproducible: Always Actual Results: The rest of the text is rendered as strong text. Expected Results: Work around parsing errors like this. Could the parser ignore invalid tags? What does W3C spec say about it?
Reporter | ||
Comment 1•14 years ago
|
||
Reporter | ||
Comment 2•14 years ago
|
||
Reporter | ||
Comment 3•14 years ago
|
||
Henri, do you have an idea on what the proper way to handle bad tag use is?
Comment 4•14 years ago
|
||
Everything about the content (parsing, networking, layout, images) are Core
Component: General → HTML: Parser
Product: Firefox → Core
QA Contact: general → parser
Version: unspecified → Trunk
This is expected behaviour. <strong/> is the same as <strong> in HTML, the slash is ignored. (HTML is not XML)
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Resolution: --- → INVALID
Comment 6•14 years ago
|
||
> What does W3C spec say about it?
To do what we do.
Status: RESOLVED → VERIFIED
Reporter | ||
Comment 7•14 years ago
|
||
Thanks guys, It wasn't obvious to me what the issue was. I been trying to figure that out how it fits together and why it was still parsed when you think it should be something else by viewing it than what its allowed to do.
You need to log in
before you can comment on or make changes to this bug.
Description
•