Bug 16912

Summary: Corresponding text for images does not appear due to float:left
Product: WebKit Reporter: Anantha Keesara <anantha>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, ap, rniwa
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: PC   
OS: Windows XP   
URL: http://www.wretch.cc/blog/
Attachments:
Description Flags
Reduction
none
Safari 15.5 matches with other browsers none

Anantha Keesara
Reported 2008-01-17 14:28:29 PST
Steps: 1. Launch the above mentioned url. 2. Scroll towards right hand side of the page. 3. Notice that the corresponding text of some images is not rendered properly. Expected: The text should render next to the image and not below the image. Other browsers: IE/FF/Opera: No issues rendering the text next to image. Nightly tested: WebKit-r29546
Attachments
Reduction (306 bytes, text/html)
2008-01-17 14:30 PST, Anantha Keesara 		no flags
Details
Safari 15.5 matches with other browsers (362.18 KB, image/png)
2022-06-24 09:31 PDT, Ahmad Saleem 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Anantha Keesara
Comment 1 2008-01-17 14:30:09 PST
Created attachment 18511 [details] Reduction
Anantha Keesara
Comment 2 2008-01-17 14:30:55 PST
Firefox 3 renders the same as WebKit in this case.
Dave Hyatt
Comment 3 2008-01-17 14:40:16 PST
This bug probably won't be fixed. The pref widths model simply can't compute an accurate maximum width in the presence of complex float layouts. Firefox 3 moved to this model as well. It is likely the CSS spec for CSS3 is going to favor this model also.
Ahmad Saleem
Comment 4 2022-06-24 09:31:47 PDT
Created attachment 460480 [details] Safari 15.5 matches with other browsers I am not able to reproduce this bug in Safari 15.5 on macOS 12.4 and it matches with other browser in attached reduction test case. Please refer to attached screenshot to view zoom-in output of all browsers, which matches with each other (Chrome Canary 105 and Firefox Nightly 103). I think it can be marked as "RESOLVED CONFIGURATION CHANGED". Thanks!
Note You need to log in before you can comment on or make changes to this bug.