RESOLVED INVALID 10790
Empty PRE elements should have a non-zero height 
https://bugs.webkit.org/show_bug.cgi?id=10790
Summary Empty PRE elements should have a non-zero height
Alexey Proskuryakov
Reported 2006-09-09 11:07:18 PDT
In the attached test case, WinIE gives all three boxes the same height. Firefox collapses the second one, and Safari collapses first and second ones.
Attachments
test case (434 bytes, text/html)
2006-09-09 11:07 PDT, Alexey Proskuryakov 		no flags
Details
strict mode test (567 bytes, text/html)
2006-09-10 00:49 PDT, Alexey Proskuryakov 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Alexey Proskuryakov
Comment 1 2006-09-09 11:07:44 PDT
Created attachment 10477 [details] test case
Dave Hyatt
Comment 2 2006-09-09 15:48:48 PDT
The second one should be collapsed. WinIE is clearly crazy on the second one. I'm not sure why we would be collapsing the first one though. That seems like a bug.
Dave Hyatt
Comment 3 2006-09-09 15:49:56 PDT
Oh oops missed the dynamic part. Our behavior is clearly correct in strict mode, and this doesn't strike me as important enough to create a quirk for.
Dave Hyatt
Comment 4 2006-09-09 15:50:46 PDT
(Test Firefox and WinIE in strict mode.)
Alexey Proskuryakov
Comment 5 2006-09-10 00:49:21 PDT
Created attachment 10485 [details] strict mode test Firefox and IE still give the same results in strict mode. I have stumbled upon this issue when the results of fast/dom/xmlhttprequest-get.xhtml changed in bug 4872 - statusText is now an empty string instead of undefined there, so one block of output suddenly collapsed.
Dave Hyatt
Comment 6 2006-09-10 01:11:44 PDT
I don't really understand why a pre would have a non-zero height when empty. Maybe Hixie has some thoughts on this one.
Robert Hogan
Comment 7 2013-07-23 11:27:35 PDT
There doesn't seem to be a case for a bug here - WebKit's behaviour looks correct. FF should collapse the first box when it's content is removed but doesn't. IE10 doesn't even remove the content. I'm going to close. There's nothing to do here.
Note You need to log in before you can comment on or make changes to this bug.