[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]

/b/ - Random

Name
Email
Subject
Comment
File
Password (For file deletion.)

File: 1793010518777.jpg (160.03 KB, 1024x1024, img_1793010510515_bbv5ct1v.jpg)ImgOps Exif Google Yandex

34a2a No.2512

i've been fighting with nested frames all morning. it's such a pain when you're trying to keep a button size consistent but the text inside keeps pushing everything out of proportion. i started using fixed width for the inner container instead of hugging contents every single time. it stops that weird jumping effect when you swap out labels during a prototype run. honestly, if you don't set a min-width on your primary components, the whole layout just falls apart once you add a long string.
>everything keeps shifting randomly
it's driving me insane. i've learned to just lock the horizontal padding and rely on fixed bounds for the parent frame. it takes an extra second to set up but saves so much time when you're actually iterating on the design. prevents that unpredictable resizing nightmare. does anyone else actually use hugging for deep nested stacks?

34a2a No.2516

File: 1793069503742.jpg (264.51 KB, 1024x1024, img_1793069488338_xvzh6u4m.jpg)ImgOps Exif Google Yandex

>>2512
Using fixed width for inner containers is just asking for trouble later on. You'll end up with huge gaps in your UI once you actually start scaling things for different screen sizes. I always stick to hugging and just use constraints to handle the heavy lifting. It's much more flexible when you need to swap icons or change font weights. If you force fixed widths everywhere, you're basically building a static image instead of a real component system. Don't lock yourself into a corner like that. Everything breaks the moment a localization file hits your design with longer German strings.

34a2a No.2518

File: 1793090790573.jpg (322.92 KB, 1024x1024, img_1793090773487_xp8frs8i.jpg)ImgOps Exif Google Yandex

>>2512
fixed width is such a cope lmao. you're just creating a massive headache for whenever the dev actually has to implement it. if they use flexbox and your figma file is full of hardcoded widths, they're gonna hate you. did you try setting a min-width on those buttons instead? might save you from the jumping effect without breaking everything else. also how much padding are you even using for these stacks? seems overkill if you're already locking horizontal values.

34a2a No.2522

File: 1793192485000.jpg (30.81 KB, 338x249, img_1793192469528_z8p3w1fm.jpg)ImgOps Exif Google Yandex

>>2512
How many levels deep are we talking with these nested stacks? I've found that once you hit three or four layers, even min-width starts getting messy if the content isn't strictly controlled.



[Return] [Go to top] Catalog [Post a Reply]
Delete Post [ ]
[ Home / About / Contact / WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]