RESOLVED CONFIGURATION CHANGED 18114
misalignment issue in webkit
https://bugs.webkit.org/show_bug.cgi?id=18114
Summary misalignment issue in webkit
jasneet
Reported 2008-03-26 10:45:42 PDT
I Steps: Go to http://www.eurosport.fr/golf/news_page2.shtml Scroll to the bottom of the page. II Issue: The page no.s for navigation are not aligned horizontally. III Conclusion: The page numbers are in a <div> with width set to 50px (in the original code, they were in a table). FF and Opera preserve the spacing of the contents as laid out in the HTML code even when the contents overflow the width of the <div> whereas IE and Safari do not. IV Other browsers: IE7: not ok FF3: ok Opera9.24: ok V Nightly tested: 31238
Attachments
screenshot (148.67 KB, image/jpeg)
2008-03-26 10:46 PDT, jasneet
no flags
reduction (297 bytes, text/html)
2008-03-26 10:46 PDT, jasneet
no flags
jasneet
Comment 1 2008-03-26 10:46:09 PDT
Created attachment 20086 [details] screenshot
jasneet
Comment 2 2008-03-26 10:46:34 PDT
Created attachment 20087 [details] reduction
Deepak Mittal
Comment 3 2014-02-06 05:19:34 PST
nbsp is used to stop the browser from breaking a line in the wrong place. please refer http://www.htmlbasictutor.ca/non-breaking-space.htm nbsp is used to create whitespace with non breaking space. as nbsp is their so isBreakable() getting called from BreakingContext::handleText() in BreakingContextInlineHeaders.h which calls nextBreakablePositionIgnoringNBSP() and in turn call's, isBreakableSpace() that returns treatNoBreakSpaceAsBreak and shouldBreakAfter() return false, so end of the line length will getting return as nextBreakable position and line will not break. So this is intended behaviour..
Ahmad Saleem
Comment 4 2022-08-29 14:43:32 PDT
I am unable to reproduce this issue in Safari Technology Preview 152 using attached reduction and it shows all numbers in one line at top of the box and it has "2" as bold and it is similar with other browsers (Chrome Canary 107 and Firefox Nightly 106). Since all browsers are matching, I am going to mark this as "RESOLVED CONFIGURATION CHANGED". If you think it is still reproducible, please reopen with updated test case. Thanks!
Note You need to log in before you can comment on or make changes to this bug.