Bug 183893
| Summary: | env() and constant() safe-aria at safari didn't work | ||
|---|---|---|---|
| Product: | WebKit | Reporter: | Bo <dr.boria> |
| Component: | CSS | Assignee: | Nobody <webkit-unassigned> |
| Status: | RESOLVED WORKSFORME | ||
| Severity: | Blocker | CC: | bdakin, thorton |
| Priority: | P2 | ||
| Version: | Safari 11 | ||
| Hardware: | iPhone / iPad | ||
| OS: | iOS 11 | ||
Bo
According to your block https://webkit.org/blog/7929/designing-websites-for-iphone-x/ you wrote that 'Safari displays your existing websites beautifully on the edge-to-edge display of the new iPhone X.'. But as fact is displays not like in your blog, but like this http://take.ms/wqGdb.
As a result env() (for 11.2 ios) and constant() (for 11.1 ios) didn't fork for cases when some data appears under safari bottom navigation bar.
And it produce bugs like this: http://take.ms/ECozf (textarea got dynamic height and button should be displayed on the screen, but it is under navigation bar).
Can you please fix env and constant attributes for displaying correct on the screen.
Grand thanks.
| Attachments | ||
|---|---|---|
| Add attachment proposed patch, testcase, etc. |
Tim Horton
Did you also opt in to viewport-fit=cover in your viewport meta tag?
If so, please provide a link to test content that reproduces this.
Bo
meta tag - yes, I did. I have no test content. I mean, I have no permissions to share this content with you. Have you got eny wswg online editor with examples of env() or constant(), wich I can edit to show you issue?
Tim Horton
Grab https://webkit.org/demos/safe-area-insets/safe-areas.html and see if that works?
Bo
This demo works only with fixed position and top/left coodinates. But in your blog you use paddings.
And with paddings this demo didn't works
Tim Horton
You can click on any of the pictures on the blog post to go to the sample page. The ones that use padding (like https://webkit.org/demos/safe-area-insets/4-min-max.html) work fine too. I think you’ll need to provide sample code that doesn’t work, you haven’t provided enough information yet to understand what is wrong in your case.