Willson: Bprompt: For me, the scroll bar only move 2 pixels max
Brannick: It is actually scrolling down the main page content that reveals the last menu item
Macek: It begs the question of why the position: fixed; height: 100%; div is responding as though it’s height is greater than the viewport
Turbiner: Height must be 100% as the content doesn’t live in overflow, it continues down the page, greater than the height of the viewport
Rzepka: Bprompt: Can you confirm the middle mouse button allowed full access to the menu, without moving the menu icon off screen?
Kirgan: Droopy: yeap, just for your info, there are other browsers besides chromium ones, ***uming that’s all you’re testing for, unless you’re only expecting chromium-based browsers users
Landrian: And yes, the mouse wheel works well, in firefox emulation
Sukovaty: Why does chrome have worse overflow management than firefox?
Vitela: How can I address this?
Lubbert: For some reason, for chrome to reach the bottom of an overflown div, you need to scroll to the very bottom of the page
Bogema: How do I resolve this so one can access all of an overflow’d divs contents without scrolling through the rest of the page’s content?
Kagay: This bug is specific to chrome and does not reproduce in firefox
Zesati: Droopy: resolve the overflow issue completely then
Waynick: Lemondom_: I want overflow, the presence of overflow is not the issue
Bullin: The issue is that chrome seems to force fixed divs with 100% height to have greater than 100% when the content overflows the div
Sunderland: More like 110%, where the first 100% may be scrolled through with overflow’s scrollbar, but the last 10% requires scrolling to the bottom of the page
Delross: Droopy: you say overflow, so the parent element got less height than its child element, right?
Casillo: That is correct. There is a div with 100% height, and a ul tag with no height restriction. The content of ul causes the overflow
Maher: Droopy: so when you leave out the UL tag, will the height of the div be still the same in both browsers?
Bergsjo: After ‘display: none’-ing the ul tag, the div is still 100px greater height than the viewport
Pech: So the issue is not coming from the overflowing element
Esquiuel: What does the div contain else?
Merkle: I suppose if I figure out why 100% height doesn’t actually mean 100% height, I’ll have my fix
Liddie: The structure is: nav div div div ul
Greeson: So the div that got different height in the browsers has only ul element as child only
Larusch: So the element itself causing trouble with different height in those different browsers.
Chelton: Then focus on it instead
Karz: What display mode? block?
Irizarry: Each div has a height of 0px. The nav has a height of 100%
Spille: What is the purpose of this?
Mariska: It is their inherited value. No height is ***igned to those divs, so seeing as I hid the ul tag, they inherit 0
Efford: What gets me is that chrome interprets 100% of 375px as 477px
Knower: If that style is removed, nav height becomes 0px
Radden: Box-sizing: border-box?
Jenrette: Also, display: inline-block helps sometimes
Connet: Yes, this strange behaviour some other user encountered, too, that heights are different in browsers in some special “undefined” states
Jindra: Droopy: hm, when you could put that isolated in a fiddle, I can directly see the issue and apply styles to it
Fisherman: Http://dev.hendricksweb.com/other/temp/ how can i remove the gap at the top of the page? notice the strings of the image are not at the very top
Glumac: Lemondom_: Made a fiddle: https://jsfiddle.net/hashem/351bj7k4/10/
Blankumsee: Z1haze the body element has margins