White Space Between <header> and <footer>
Reported by
azzaz...@gmail.com,
Aug 9 2017
|
||||||
Issue descriptionUserAgent: Mozilla/5.0 (Macintosh; Intel Mac OS X 10_12_6) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/60.0.3112.90 Safari/537.36 Steps to reproduce the problem: 1. header: position is relative and margin-bottom is 50vh. 2. footer: position is fixed, height is 50vh, bottom is 0 and width is 100%. What is the expected behavior? The white space between the <header> and <footer> should not exist in the 1st place. The latest versions of Firefox and Safari are working perfectly fine. Opera browser has the exact same bug as Chrome since both are built with Blink. What went wrong? Chrome adds a white space between the <header> and <footer> when browsing the page on fullscreen mode. Did this work before? N/A Does this work in other browsers? Yes Chrome version: 60.0.3112.90 Channel: stable OS Version: OS X 10.12.6 Flash Version: This issue only occurs when the <footer> height value equals exactly 50vh. No issues exist when the vh is given a different value. Also, assigning the same value of 50 with different units such as pixels, rems, etc. does not produce any bugs whatsoever. This is why I'm certain this is a bug related to VH units and it's specific to browsers using the Chrome Blink engine.
,
Aug 11 2017
Able to reproduce the issue on Mac 10.12.6, Win-10 and Ubuntu 14.04 using chrome reported version #60.0.3112.90 and latest canary #62.0.3182.0. This is a non-regression issue as it is observed from M45 old builds. Note: On OS-Win, the issue is only seen when the window is resized. Issue is not seen when maximized. Hence, marking it as untriaged to get more inputs from dev team. Thanks...!!
,
Aug 15 2017
This is a known problem sadly and has to do with rounding, if 50vh resolves to non-integer pixel value of 0.5 or less then it'll be rounded down for the fixed position element. It has proven pretty hard to fix due to the way fixed position is implemented so I'm afraid you'll have to wait a little longer. A possible workaround would be to inflate the size by a pixel using calc or negative margins.
,
Aug 15 2017
,
Aug 16
This issue has been Available for over a year. If it's no longer important or seems unlikely to be fixed, please consider closing it out. If it is important, please re-triage the issue. Sorry for the inconvenience if the bug really should have been left as Available. For more details visit https://www.chromium.org/issue-tracking/autotriage - Your friendly Sheriffbot
,
Aug 18
|
||||||
►
Sign in to add a comment |
||||||
Comment 1 by shrike@chromium.org
, Aug 10 2017