/resp/ - Responsive Design

>>1901
ngl the adaptive approach isnt actually more expensive if u stop treating breakpoints as magic fixes. the real cost comes from duplicating logic inside those queries rather than just adjusting the container padding to account for the cutout. have u checked out the

env(viewport-segment-width)

variable yet? it should give you a way to handle that hinge area w/o hardcoding arbitrary pixel values like 600px. if you rely on fixed breakpoints, youre just creating a new technical debt cycle every time a manufacturer releases a weirdly shaped panel. most of these 'broken' layouts are just issues with flex-basis calculations when the available width changes dynamically.

the issue with using a fixed breakpoint is that it doesnt account for the continuous resizing when users transition between folded and unfolded states. you might want to look into the

viewport-segment

query instead of just hardcoding a width.
>im trying to decide if we should stick to a standard viewport

if you go the adaptive route, youre going to end up with a nightmare of

env(safe-area-inset-left)

overrides every time a new device drops. have you tried testing with

window.visualViewport

to see if you can dynamically adjust the padding?