Bug 101625

Summary: Relative positioned element can be positioned outside of it's parent container
Product: WebKit Reporter: edbaker
Component: Layout and RenderingAssignee: Takashi Sakamoto <tasak>
Status: UNCONFIRMED    
Severity: Normal CC: ahmad.saleem792, eric, jchaffraix, morrita, simon.fraser, tasak, webkit.review.bot, zalan
Priority: P2    
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
Test case
none
WIP
none
Patch
none
Patch none

edbaker
Reported 2012-11-08 11:11:22 PST
Created attachment 173075 [details] Test case With the test case click the set height button, scroll the relative positioned element into view then click reset height. The relative positioned element ends up positioned outside of parents container when the height and overflow properties are removed from the outer container
Attachments
Test case (1.42 KB, text/html)
2012-11-08 11:11 PST, edbaker
no flags
WIP (4.82 KB, patch)
2012-11-12 02:05 PST, Takashi Sakamoto
no flags
Patch (4.65 KB, patch)
2012-11-12 20:51 PST, Takashi Sakamoto
no flags
Patch (4.70 KB, patch)
2012-11-15 22:19 PST, Takashi Sakamoto
no flags
Takashi Sakamoto
Comment 1 2012-11-12 02:05:04 PST
Takashi Sakamoto
Comment 2 2012-11-12 20:51:09 PST
EFL EWS Bot
Comment 3 2012-11-12 22:39:09 PST
Takashi Sakamoto
Comment 4 2012-11-15 22:19:16 PST
Anders Carlsson
Comment 5 2014-02-05 11:05:54 PST
Comment on attachment 174608 [details] Patch Clearing review flag on patches from before 2014. If this patch is still relevant, please reset the r? flag.
Ahmad Saleem
Comment 6 2023-02-24 09:45:34 PST
I am not able to reproduce the issue of 'relative container' being outside of 'inner container' but we don't do repaint after height change and we still get 'scrollbar' width of space on right side of container after reset height empty and only page refresh bring it back (not even resizing browser window do anything). Chrome Canary 112 and Firefox Nightly 112 match each other and does not have 'scrollbar' width gap. CCing others to ask whether to track this issue in separat or in same.
Note You need to log in before you can comment on or make changes to this bug.