I’d like to use svh viewport units for the first section of my landing page, and while they work great on standard mobile browsers, they function the same as dvh units in in-app browsers like Google Search and Instagram. This causes some clunky snapping when I’m scrolling down through the rest of the landing page. How can I fix this to fully display the first section of the landing page (which is why we use svh units), without having it expand/change size with respect to the browser elements (like you’d expect to happen with dvh units)?

I’d like to use svh viewport units for the first section of my landing page, and while they work great on standard mobile browsers, they function the same as dvh units in in-app browsers like Google Search and Instagram. This causes some clunky snapping when I’m scrolling down through the rest of the landing page. How can I fix this to fully display the first section of the landing page (which is why we use svh units), without having it expand/change size with respect to the browser elements (like you’d expect to happen with dvh units)?

I’d like to use svh viewport units for the first section of my landing page, and while they work great on standard mobile browsers, they function the same as dvh units in in-app browsers like Google Search and Instagram. This causes some clunky snapping when I’m scrolling down through the rest of the landing page. How can I fix this to fully display the first section of the landing page (which is why we use svh units), without having it expand/change size with respect to the browser elements (like you’d expect to happen with dvh units)?

I’d like to use svh viewport units for the first section of my landing page, and while they work great on standard mobile browsers, they function the same as dvh units in in-app browsers like Google Search and Instagram. This causes some clunky snapping when I’m scrolling down through the rest of the landing page. How can I fix this to fully display the first section of the landing page (which is why we use svh units), without having it expand/change size with respect to the browser elements (like you’d expect to happen with dvh units)?

I’d like to use svh viewport units for the first section of my landing page, and while they work great on standard mobile browsers, they function the same as dvh units in in-app browsers like Google Search and Instagram. This causes some clunky snapping when I’m scrolling down through the rest of the landing page. How can I fix this to fully display the first section of the landing page (which is why we use svh units), without having it expand/change size with respect to the browser elements (like you’d expect to happen with dvh units)?

I’d like to use svh viewport units for the first section of my landing page, and while they work great on standard mobile browsers, they function the same as dvh units in in-app browsers like Google Search and Instagram. This causes some clunky snapping when I’m scrolling down through the rest of the landing page. How can I fix this to fully display the first section of the landing page (which is why we use svh units), without having it expand/change size with respect to the browser elements (like you’d expect to happen with dvh units)?

I’d like to use svh viewport units for the first section of my landing page, and while they work great on standard mobile browsers, they function the same as dvh units in in-app browsers like Google Search and Instagram. This causes some clunky snapping when I’m scrolling down through the rest of the landing page. How can I fix this to fully display the first section of the landing page (which is why we use svh units), without having it expand/change size with respect to the browser elements (like you’d expect to happen with dvh units)?