Bug 125671

Summary: Overlay scrollbars of "overflow:scroll" appear over the overlapped "position:absolute" element
Product: WebKit Reporter: Jaehun Lim <ljaehun.lim>
Component: Layout and RenderingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, bdakin, dbates, donggwan.kim, hi, jonlee, simon.fraser, thorton, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: 528+ (Nightly build)   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
testcase
none
screenshot none

Jaehun Lim
Reported 2013-12-12 19:11:16 PST
Created attachment 219141 [details] testcase In Safari, overlay scrollbars has wrong layer ordering. Please see my test case, screenshot.
Attachments
testcase (309 bytes, text/html)
2013-12-12 19:11 PST, Jaehun Lim 		no flags
Details
screenshot (211.02 KB, image/png)
2013-12-12 19:12 PST, Jaehun Lim 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Jaehun Lim
Comment 1 2013-12-12 19:12:22 PST
Created attachment 219142 [details] screenshot
Jaehun Lim
Comment 2 2014-01-03 00:12:42 PST
Any comments ? Is it a bug or the concept of overlay scrollbar ?
Tim Horton
Comment 3 2014-01-03 00:27:32 PST
(In reply to comment #2) > Any comments ? > > Is it a bug or the concept of overlay scrollbar ? Pretty sure it's a bug. Overlay scrollbars are supposed to overlay the content in their scrollable area, NOT content in a totally different element which is above it in z.
Jon Lee
Comment 4 2014-01-03 00:44:32 PST
<rdar://problem/15650063>
Radar WebKit Bug Importer
Comment 5 2014-01-03 09:55:22 PST
<rdar://problem/15744338>
jonjohnjohnson
Comment 6 2018-12-10 08:07:29 PST
https://bugs.webkit.org/show_bug.cgi?id=65259 Duplicate?
Ahmad Saleem
Comment 7 2023-06-15 12:21:16 PDT
I am not able to reproduce this bug in Safari 16.5 and it does not show 'scrollbar' on top of Green Rect like reference image. Chrome Canary 116 and Firefox Nightly 116 are matching Safari as well.
Simon Fraser (smfr)
Comment 8 2023-06-15 12:55:01 PDT
This is fixed now.
Note You need to log in before you can comment on or make changes to this bug.