Bug 5066 - Line breaks are allowed between images when they shouldn't be
Summary: Line breaks are allowed between images when they shouldn't be
Status: RESOLVED DUPLICATE of bug 10517
Alias: None
Product: WebKit
Classification: Unclassified
Component: Layout and Rendering (show other bugs)
Version: 420+
Hardware: Mac OS X 10.4
: P2 Major
Assignee: Nobody
URL: http://www.snehvide.dk/default.asp?pa...
Keywords: HasReduction
Depends on:
Blocks:
 
Reported: 2005-09-20 08:55 PDT by Peter Larsen
Modified: 2007-02-02 07:08 PST (History)
2 users (show)

See Also:


Attachments
Testcase (160 bytes, text/html)
2005-12-28 05:34 PST, Joost de Valk (AlthA)
no flags Details

Note You need to log in before you can comment on or make changes to this bug.
Description Peter Larsen 2005-09-20 08:55:05 PDT
Not much to say exept that graphics clutter. It works perfectly fine in Opera 8.5.2173.

I have tested with latest nightly from 17th september and Safari 2.0.1 (412.5)
Comment 1 Joost de Valk (AlthA) 2005-10-06 01:25:39 PDT
Confirmed in ToT. Moving to p2 since i think p1 is a big tough here.
Comment 2 Eric Seidel (no email) 2005-12-27 15:22:13 PST
Agreed.  Layout is wrong.  We need a reduced test case before we can do much with this bug however:
http://webkit.opendarwin.org/quality/reduction.html
Comment 3 Joost de Valk (AlthA) 2005-12-28 05:34:18 PST
Created attachment 5335 [details]
Testcase

for some reason, safari puts these images below eachother, instead of next to
each other.
Comment 4 Joost de Valk (AlthA) 2005-12-28 05:35:07 PST
I don't know if this is a bug, the table has width 10%, and safari is obeying that it seems. Changing 
keyword to HasReduction.
Comment 5 Dave Hyatt 2007-01-06 16:58:16 PST
This really has nothing to do with tables.  We allow line breaks between images that have no whitespace between them.  Firefox, WinIE, and Opera don't.  This is a file bug in Radar from years ago... not sure if it ever made it into Bugzilla.

Comment 6 Dave Hyatt 2007-01-06 16:59:52 PST
This behavior is actually completely unspecified in CSS unfortunately, but I agree we should match WinIE and Firefox.  Unfortunately their treatment of replaced elements is completely inconsistent (form controls behave differently than images, etc.), but I guess we have to match.


Comment 7 Dave Hyatt 2007-01-06 17:02:38 PST
Need a giant matrix basically of every possible replaced element type next to every other possible type, e.g., image-image, select-image, image-select, select-select, button-image, image-button, etc.

Then after doing that, need to see what the behavior is when white-space:pre is put on one of the elements (on only the one before, on only the one after, etc.).

Note we have some form control-related issues already from the use of white-space:pre.
Comment 8 mitz 2007-02-02 07:08:51 PST
I think this bug was about the tables case, which was duplicated in bug 10517. The general behavior for replaced elements has already been addressed by a different patch.

*** This bug has been marked as a duplicate of 10517 ***