Bug 187151

Summary: css env() support seems disabled on some iPhones
Product: WebKit Reporter: Rick Byers <rbyers>
Component: CSSAssignee: Nobody <webkit-unassigned>
Status: RESOLVED CONFIGURATION CHANGED    
Severity: Normal CC: ahmad.saleem792, ap, bfulgham, dino, rniwa, simon.fraser, thorton, zalan
Priority: P2    
Version: Safari 11   
Hardware: Unspecified   
OS: Unspecified   
Attachments:
Description Flags
screenshot in Safari
none
screenshot in Chrome none

Rick Byers
Reported 2018-06-28 12:37:49 PDT
Created attachment 343834 [details] screenshot in Safari Simple test page for CSS env(): http://output.jsbin.com/qenayuq On my iPhone with AppleWebKit/605.1.15 and Safari iOS 11.4 it shows disabled. Running Chrome on the same device (i.e. same WebKit) it's enabled.
Attachments
screenshot in Safari (30.80 KB, image/png)
2018-06-28 12:37 PDT, Rick Byers 		no flags
Details
screenshot in Chrome (26.77 KB, image/png)
2018-06-28 12:38 PDT, Rick Byers 		no flags
Details
View All Add attachment proposed patch, testcase, etc.
Rick Byers
Comment 1 2018-06-28 12:38:11 PDT
Created attachment 343835 [details] screenshot in Chrome
Rick Byers
Comment 2 2018-06-28 12:41:17 PDT
Also tested a different iPhone 6 device and it was enabled there. Explicitly turning on the flag in "experimental features" also makes it work. This was hit when evaluating the web-platform-tests we landed for shipping the feature in Chrome: https://groups.google.com/a/chromium.org/d/msg/Blink-dev/Fim-KmT08PE/LIHNNXALBAAJ
Ahmad Saleem
Comment 3 2022-07-24 08:58:20 PDT
I am not sure on previous version since I have only one device and iPhone 13 Pro Max with iOS 15.6 is showing that CSS env() is supported based on test case in Comment 0. I think since old versions are not supported and only receive security updates, I think this can be closed. Further - caniuse.com shows clearly that it was from Safari 11.3 onward for iOS - https://caniuse.com/?search=env() Can this be marked as "RESOLVED INVALID" or "RESOLVED CONFIGURATION CHANGED". Thanks!
Note You need to log in before you can comment on or make changes to this bug.