Bug 197611

Summary: 'background:transparent' don't reliably work in IOS 12.2
Product: WebKit Reporter: 刘桂彬 <liugb1101>
Component: CompositingAssignee: Nobody <webkit-unassigned>
Status: RESOLVED DUPLICATE    
Severity: Normal CC: dino, simon.fraser, webkit-bug-importer, zalan
Priority: P2 Keywords: InRadar
Version: Safari 12   
Hardware: iPhone / iPad   
OS: iOS 12   
See Also: https://bugs.webkit.org/show_bug.cgi?id=197654
Attachments:
Description Flags
video
none
Testcase none

刘桂彬
Reported 2019-05-06 06:36:59 PDT
Created attachment 369122 [details] video Since IOS12.2 relased ，our pages occur a bug like this： https://img.alicdn.com/tfs/TB18h_pUCzqK1RjSZPxXXc4tVXa-320-569.gif visit page below in safari and scroll the page , you can feel https://pages.tmall.com/wow/chaoshi/act/chaoshi-brand-test Depend on the distance that user scroll ，we change the css propety 'backgound:transparent' on the target dom node ，but it seem's not always work as we expected This bug only can be seen in those device that upgrade IOS12.2
Attachments
video (2.06 MB, video/mp4)
2019-05-06 06:36 PDT, 刘桂彬 		no flags
Details
Testcase (1.62 KB, text/html)
2019-05-11 11:47 PDT, Simon Fraser (smfr) 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Radar WebKit Bug Importer
Comment 1 2019-05-07 13:13:54 PDT
<rdar://problem/50552355>
Simon Fraser (smfr)
Comment 2 2019-05-07 13:27:17 PDT
It looks like we're failing to update "contentsOpaque" on the header.
Simon Fraser (smfr)
Comment 3 2019-05-11 11:47:30 PDT
Created attachment 369655 [details] Testcase
刘桂彬
Comment 4 2019-05-29 18:27:08 PDT
(In reply to Simon Fraser (smfr) from comment #3) > Created attachment 369655 [details] > Testcase Thanks for reply Some more details： After we add css property "box-shadow" on the header，this bug can be fixed https://img.alicdn.com/tfs/TB1AB_YaLWG3KVjSZPcXXbkbXXa-2650-936.png
Simon Fraser (smfr)
Comment 5 2019-05-29 19:12:52 PDT
I fixed this via bug 197654. *** This bug has been marked as a duplicate of bug 197654 ***
Note You need to log in before you can comment on or make changes to this bug.