RESOLVED CONFIGURATION CHANGED 71531
overflow in inline blocks does not affect y position of block siblings 
https://bugs.webkit.org/show_bug.cgi?id=71531
Summary overflow in inline blocks does not affect y position of block siblings
Gosha Vasin
Reported 2011-11-03 18:10:57 PDT
If element is inline-block and pseudo-classes is :hover css property margin-bottom is not work, if value < 0 and element is conteiner for IMG tag. See example in attachment file. Sorry me for my bad English.
Attachments
example for bug 71531 (611 bytes, text/html)
2011-11-03 18:13 PDT, Gosha Vasin 		no flags
Details
Reduction (2.47 KB, text/html)
2013-09-16 12:20 PDT, Robert Hogan 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Gosha Vasin
Comment 1 2011-11-03 18:13:10 PDT
Created attachment 113600 [details] example for bug 71531
Robert Hogan
Comment 2 2013-09-16 12:20:01 PDT
Created attachment 211816 [details] Reduction
Robert Hogan
Comment 3 2013-09-17 11:06:03 PDT
WebKit might be correct here. The red img inside the inline-block is overflow as the inline block's neighbours are concerned. Unlike the case where the img is an inline the inline-block has its own height and it's that height the neighbours should respect. There's no reason why they should move below the overflow instead.
Robert Hogan
Comment 4 2013-09-17 13:29:05 PDT
Let me correct a few typos in that comment: WebKit might be correct here. The red img inside the inline-block is overflow as far as the inline block's neighbours are concerned. Unlike the case where the img is in an inline element the inline-block has its own height and it's that height the neighbours should respect. There's no reason why they should move below the overflow instead.
Ahmad Saleem
Comment 5 2022-08-20 12:03:50 PDT
I am not able to reproduce this bug in Safari 15.6.1 and Safari Technology Preview 151 and both browser render the text line below red box and it is matching with other browsers (Chrome Canary 106 and Firefox Nightly 105). Since all browsers are matching, I am going to mark this as "RESOLVED CONFIGURATION CHANGED", please reopen if I understood the test case wrong or I am testing it incorrectly. Thanks!
Note You need to log in before you can comment on or make changes to this bug.