Summary: | Position: fixed elements with top: 0 can appear offset from top of viewport | ||||||
---|---|---|---|---|---|---|---|
Product: | WebKit | Reporter: | James Please <glads.logs0o> | ||||
Component: | Layout and Rendering | Assignee: | Nobody <webkit-unassigned> | ||||
Status: | RESOLVED DUPLICATE | ||||||
Severity: | Normal | CC: | bfulgham, cdumez, jonlee, simon.fraser, webkit-bug-importer, zalan | ||||
Priority: | P2 | Keywords: | InRadar | ||||
Version: | Other | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
URL: | https://moolah-app-staging-pr-784.herokuapp.com/terms | ||||||
Attachments: |
|
Description
James Please
2017-04-27 19:49:11 PDT
Whoops – forgot the link. Here it is: https://moolah-app-staging-pr-784.herokuapp.com/terms (is there a way to edit posts?) iOS 10.3 started to use the "visual viewports" model for position:fixed, which may have affected this, but only if the page has scale != 1. I can reproduce with https://moolah-app-staging-pr-784.herokuapp.com/terms (please keep that link live!) Possibly related to the fact that <header class="appHeader"> is position:fixed, and <div class="overlayNav"> is also position:fixed inside of it (so nested fixed, which is redundant). Simon, don't worry, I'll be sure to keep the link active. The nested position fixed could be the problem. I'll try nesting position: fixed in the reduced test case tonight to see if that causes the problem. Note that this also affects the nav items themselves, which do not have any nesting of position:fixed (but their container, a UL, does have position:absolute). So if nested position:fix causes it, there could be other things that cause it, too. Dup of bug 170280 *** This bug has been marked as a duplicate of bug 170280 *** |