Closed Bug 592219 Opened 14 years ago Closed 14 years ago

stange behaviour of the <address> tag

Categories

(Core :: DOM: HTML Parser, defect)

defect
Not set
normal

Tracking

()

RESOLVED FIXED

People

(Reporter: voltterra, Unassigned)

References

Details

Attachments

(1 file)

User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; ru; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 6.1; ru; rv:1.9.2.8) Gecko/20100722 Firefox/3.6.8 i've encoutered a problem during developing my own site. I tried to add a display:inline-block or at least display:block property for <address> but the result was different than i expected. The first two nested elements were inside the address' box while the next one formed their own box below it. The layout was as follow: <html> <head> <meta http-equiv="Content-Type" content="text/html; charset=iso-8859-1"> <title>Untitled Document</title> <style> address { display: block; border: 1px solid; margin: 20px; } </style> </head> <body> <address class="vcard"> <span class="fn org">Some info here</span> <span>New info</span> <div class="tel"> <span class="type">work</span> <span class="value">(343) 344-98-90</span> </div> <div class="tel"> <span class="type">work</span> <span class="value">(343) 344-98-91</span> </div> </address> </body> </html> Reproducible: Always Steps to Reproduce: 1.just try the layout i've provided 2.or you may build your own one, just include some block element there (like div etc) 3. Actual Results: block elements like divs are rendered outside the address box Expected Results: the <address> tag should include all descendant elements into parent box This example works fine in the latest Safari, Chrome, Opera and IE.
Version: unspecified → 3.6 Branch
Attached file testcase (deleted) —
For your future reference, you can attach testcases using the 'Add an attachment' link on the bug page. It makes it easier to test.
I can reproduce on Mozilla/5.0 (Macintosh; Intel Mac OS X 10.5; rv:2.0b6pre) Gecko/20100904 Firefox/4.0b6pre with html5.enable=false, but not with the html5.enable=true (which is now the default). Fixed by the HTML5 parser. You can check the Firefox 4 beta to see for yourself.
Status: UNCONFIRMED → RESOLVED
Closed: 14 years ago
Component: General → HTML: Parser
Depends on: html5-parsing
OS: Windows 7 → All
Product: Firefox → Core
QA Contact: general → parser
Hardware: x86_64 → All
Resolution: --- → FIXED
Version: 3.6 Branch → Trunk
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: