Issue metadata
Sign in to add a comment
|
Pull-to-refresh causes `position: fixed` headers to move a few pixels down from `top: 0`, creating a gap
Reported by
ja...@lengstorf.com,
Apr 28 2016
|
||||||||||||||||||||||||
Issue descriptionSteps to reproduce the problem: 1. Open a site with an element that is `position: fixed; top: 0` (I put up http://chromebug.herokuapp.com/ to demonstrate this) 2. Do a pull-to-refresh motion, but DO NOT actually refresh the page 3. Scroll down and the fixed element will now have a gap above it, even though it's set to `top: 0` What is the expected behavior? The fixed element should always remain at `top: 0`. What went wrong? The position of the fixed element, despite the CSS still instructing `top: 0`, is nudged down the page by 1–5px. Did this work before? N/A Chrome version: 50.0.2661.77 Channel: stable OS Version: iOS 9.3.1 Flash Version: n/a
,
Apr 29 2016
Please triage.
,
Jun 7 2016
This issue is reproducible with the fixed navs on jcrew.com and bounceexchange.com.
,
Jul 20 2016
Also reproducible on nytimes.com mobile. Example URL: http://mobile.nytimes.com/2016/07/20/us/politics/melania-trump-convention-speech.html
,
Jul 20 2016
srikanthg@, do you think it is a dup of 574561?
,
Jul 20 2016
Yes this is a dup of Issue 574561 . I have tried steps mentioned in the original report above with chromebug.herokuapp.com and not able to reproduce the issue on M53.
,
Jul 20 2016
|
|||||||||||||||||||||||||
►
Sign in to add a comment |
|||||||||||||||||||||||||
Comment 1 by ja...@lengstorf.com
, Apr 29 2016