Bug 197611 - 'background:transparent' don't reliably work in IOS 12.2
Summary: 'background:transparent' don't reliably work in IOS 12.2
Status: RESOLVED DUPLICATE of bug 197654
Alias: None
Product: WebKit
Classification: Unclassified
Component: Compositing (show other bugs)
Version: Safari 12
Hardware: iPhone / iPad iOS 12
: P2 Normal
Assignee: Nobody
URL:
Keywords: InRadar
Depends on:
Blocks:
 
Reported: 2019-05-06 06:36 PDT by 刘桂彬
Modified: 2019-05-29 19:12 PDT (History)
4 users (show)

See Also:

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 an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description 刘桂彬 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
Comment 1 Radar WebKit Bug Importer 2019-05-07 13:13:54 PDT 
<rdar://problem/50552355>
Comment 2 Simon Fraser (smfr) 2019-05-07 13:27:17 PDT 
It looks like we're failing to update "contentsOpaque" on the header.
Comment 3 Simon Fraser (smfr) 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
Comment 5 Simon Fraser (smfr) 2019-05-29 19:12:52 PDT 
I fixed this via bug 197654.

*** This bug has been marked as a duplicate of bug 197654 ***