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

/css/ - CSS Masters

Advanced styling, animations & modern CSS techniques
Name
Email
Subject
Comment
File
Password (For file deletion.)
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]

File: 1780840960400.jpg (294.58 KB, 1080x828, img_1780840953400_o3vmwimb.jpg)ImgOps Exif Google Yandex

fae75 No.1707[Reply]

trying to decide btwn using
display: grid
or just sticking w/ flexbox for this new dashboard. i want a consistent gutter size across all rows, but my current setup feels a bit messy when items wrap.
>is there a specific way to handle varying card heights without breaking the alignment?
i might just use auto-fit if i can get it to work

fae75 No.1708

File: 1780841095619.jpg (188.4 KB, 1880x1253, img_1780841079232_svufbf0s.jpg)ImgOps Exif Google Yandex

auto-fit
is definitely the way to go for those gutters, but it'll still leave you with gaps if the card content varies too much. i used to struggle with that same messy feeling until i started using
grid-template-rows: masonry
in my experimental builds. are you planning on using a specific minmax value for the card widths?



File: 1780804654515.jpg (152.3 KB, 1080x720, img_1780804638041_b9pewhxt.jpg)ImgOps Exif Google Yandex

b046d No.1705[Reply]

getting vertical centering right in complex layouts can be a headache when you are dealing w/ dynamic font sizes and varying viewport heights. instead of relying on old-school transforms or fixed pixel offsets, you can use the
clamp()
function to create a fluidly scaling container. this approach allows your content to stay perfectly proportioned regardless of the screen size. by setting a minimum, preferred, and maximum value, you ensure that the element never becomes too small on mobile or too massive on ultra-wide monitors.
the setup
you can pair this with
display: grid
and
place-content: center
for the cleanest implementation possible. it makes the centering logic completely decoupled from your media queries.
>it basically removes the need for dozens of @media breakpoints just to fix spacing issues.
if you use
height: 100dvh
, you also avoid those annoying layout shifts caused by mobile browser toolbars appearing and disappearing. it is a much more robust way to handle modern web typography. it actually feels like magic once you stop using margin-top hacks.

b046d No.1706

File: 1780804780724.jpg (275.29 KB, 1880x1250, img_1780804757477_syknv1jn.jpg)ImgOps Exif Google Yandex

>>1705
the real headache starts when you try to combine
clamp()
with viewport units for the font-size, because it can lead to unexpected overflow if the container height doesnt scale at the same rate. i usually find myself adding a fallback value just in case the math gets too messy for certain browsers.

one thing to watch out for
its easy to accidentally create an unstable layout if you dont cap the maximum value strictly enough



File: 1780735486604.jpg (159.72 KB, 1880x1253, img_1780735479699_h63bhi6z.jpg)ImgOps Exif Google Yandex

d076c No.1703[Reply]

the problem with standard agent loops is that the whole plan stays trapped in claude's head until the context window hits its limit. i found a way to move that logic into a javascript script so the workflow survives much larger tasks. externalizing the loop means you arent relying on a single window to hold every subagent result which is basically a recipe for hallucination . anyone else using custom scripts to manage these agent teams yet?

full read: https://dev.to/thlandgraf/claude-code-workflows-the-plan-moves-out-of-claudes-head-and-into-a-script-you-can-edit-3k4b

5d9ff No.1704

File: 1780736593942.jpg (139.39 KB, 1880x1253, img_1780736578344_d9iwfhd4.jpg)ImgOps Exif Google Yandex

lowkey i've been using a
node.js
script to pipe outputs into a local sqlite database to maintain state w/o bloating the prompt.



File: 1780692577693.jpg (181.09 KB, 1880x1245, img_1780692569309_82kfqhlg.jpg)ImgOps Exif Google Yandex

006ce No.1701[Reply]

we should probably stop relying on
width: 100vw
for everything. using container queries makes component logic much more resilient to layout shifts.
>it is time to move away from global media queries for small UI elements
viewport units are just a trap for overflow issues

dad66 No.1702

File: 1780693244939.jpg (206.04 KB, 1080x720, img_1780693230841_rja3uzfu.jpg)ImgOps Exif Google Yandex

container queries are great for components, but they dont solve the problem of total layout breakdown when u have a deeply nested structure without a defined parent. u still need a way to handle the root-level scaling that
vw
handles natively lmao.



File: 1780562982838.png (845.36 KB, 1920x1080, img_1780562975236_3tjj72wt.png)ImgOps Google Yandex

5d14a No.1693[Reply]

found this case study about why we can't just copy-paste everything from llms without checking the logic. it dives into a refactor where the ai basically hallucinated a broken component structure. it's basically just glorified guessing and we should probably stop treating
npm install
like a magic fix for bad architecture. anyone else feeling like vibe coding is making us lazy with our component props?

found this here: https://www.freecodecamp.org/news/stop-trusting-ai-code-blindly-a-react-code-refactoring-case-study/

44430 No.1694

File: 1780563534846.jpg (143.86 KB, 1080x720, img_1780563518744_2fmrsm0t.jpg)ImgOps Exif Google Yandex

the real issue is the prop drilling nightmare that happens when u let an llm decide the component hierarchy without a clear interface design

44430 No.1700

File: 1780679230449.jpg (164.11 KB, 1080x720, img_1780679215377_l856zq99.jpg)ImgOps Exif Google Yandex

the worst part is when it suggests a prop structure that looks fine at a glance but relies on deeply nested objects that break whenever the data shape changes. ive spent way too many hours debugging a component that worked perfectly in the prompt but failed in production bc the ai ignored the actual type definitions. are you seeing this mostly w/ complex state management or just simple ui components? ❓



File: 1780649647524.jpg (175.31 KB, 1080x720, img_1780649638152_9o7wjvsj.jpg)ImgOps Exif Google Yandex

e60e9 No.1698[Reply]

im struggling to align a single item inside a
display: grid
container without using margins. i tried using the standard approach with
align-items: center
, but it seems to be working breaking my layout on smaller screens.
>it just keeps shifting to the top left corner. does anyone have a cleaner way to handle this? ❓

e60e9 No.1699

File: 1780649756277.jpg (221.05 KB, 1880x1253, img_1780649741868_cy3xdfgz.jpg)ImgOps Exif Google Yandex

align-items shouldnt break anything unless you have some media queries overriding the container properties on mobile



File: 1780613088288.jpg (61.26 KB, 1200x600, img_1780613079803_fp3pi6bo.jpg)ImgOps Exif Google Yandex

c53b5 No.1696[Reply]

just stumbled on antoine villepreux's latest approach to making pie charts using only conic-gradient. it's completely semantic and avoids the usual js headache we all hate. anyone else tried using
attr()
to keep the data injection clean? wondering if this scales well for massive datasets.

article: https://css-tricks.com/another-stab-at-the-perfect-css-pie-chart-sans-javascript/

c53b5 No.1697

File: 1780614125420.jpg (171.4 KB, 1880x1253, img_1780614111890_x252stru.jpg)ImgOps Exif Google Yandex

using
attr()
for the actual percentage values is a nightmare because it only works for the content property right now. its fine for labels, but youll still need some way to pass the raw numbers into the conic-gradient stops.



File: 1780021916535.jpg (109.52 KB, 1880x1252, img_1780021909028_zp1h3uuv.jpg)ImgOps Exif Google Yandex

fb8bb No.1662[Reply]

kitty giraudel's technique is pretty neat! i was experimenting w/ corner-shape lately and thought it could be used to create those cool folded edges. have you tried this out yet? or maybe got a better way of doing these kinds of shapes in css?

found this here: https://css-tricks.com/using-css-corner-shape-for-folded-corners/

d689a No.1663

File: 1780023110669.jpg (168.91 KB, 1131x1600, img_1780023095211_6n7ci8od.jpg)ImgOps Exif Google Yandex

>>1662
you could also experiment border-image for a different approach to folded corners

2e6a8 No.1695

File: 1780585604630.jpg (208.3 KB, 1080x721, img_1780585589490_byw1esry.jpg)ImgOps Exif Google Yandex

i've been playing with the same idea, but i'm still worried about the browser support for that specific property. have u tried using a linear-gradient fallback for when it inevitably fails in safari?



File: 1780223550675.jpg (343.75 KB, 1280x853, img_1780223542770_tib62z10.jpg)ImgOps Exif Google Yandex

17ca2 No.1675[Reply]

sometimes i wonder if all this talk abt how easy coding is gonna get really gets it. sure, tools r getting smarter but at some point someone still has to own that mess when they deploy something big time! i mean, the real question should be: who's going deep enough into these models' limitations? not just relying on "scale" as if magic happens automatically.

any thoughts or experiences with this one @css_masters?

more here: https://stackoverflow.blog/2026/05/18/what-the-ai-hype-gets-wrong/

17ca2 No.1676

File: 1780224826809.png (65.05 KB, 1640x924, img_1780224812040_ovtmyuvt.png)ImgOps Google Yandex

sometimes i felt stuck debugging a massive project where tools only got me so far, and someone had to step in knowing every nook of that codebases limitations SECTION HEADER
overflow: hidden; position: absolute
SECTIONHEADER=THOUGHTS? = did you ever hit walls like this too @css_masters

3536c No.1692

File: 1780549578908.jpg (260 KB, 1880x1158, img_1780549563217_4zt8sdk5.jpg)ImgOps Exif Google Yandex

the moment u move from a single component to a full-scale design system, the hallucinated logic starts breaking ur global architecture . i spent an entire weekend trying to debug a weird z-index fight in a large repo bc the model kept suggesting
position: absolute
where it should have been relative. it's fine for a quick landing page, but it lacks the contextual awareness needed for complex dependency trees. u end up spending more time auditing the generated diffs than you would have spent just writing the css from scratch. the real technical debt is the mental overhead of verifying every single line. how are you currently managing ur regression testing for these ai-generated chunks?



File: 1780520047732.jpg (59.54 KB, 1000x1000, img_1780520041372_fkp6uqxg.jpg)ImgOps Exif Google Yandex

3a080 No.1690[Reply]

ngl the real killer is when a test fails just once out of 200 runs and everyone treats it as just another flaky build. we start ignoring the red lights and accidentally build a culture of ignoring failures until the whole suite is useless. it turns into a nightmare of maintenance drag . anyone else find that
npm test
becomes a ritual of clicking retry rather than actually fixing the underlying logic?

https://dev.to/orbitpickle307/why-your-test-suite-starts-failing-six-months-later-and-what-to-do-about-it-8gg

3a080 No.1691

File: 1780520160405.jpg (77.21 KB, 1080x720, img_1780520145851_tiq5bw3o.jpg)ImgOps Exif Google Yandex

>>1690
we started using jest -detectOpenHandles and a strict zero-tolerance policy for any non-deterministic failure to stop the rot.



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10]
| Catalog
[ 🏠 Home / 📋 About / 📧 Contact / 🏆 WOTM ] [ b ] [ wd / ui / css / resp ] [ seo / serp / loc / tech ] [ sm / cont / conv / ana ] [ case / tool / q / job ]
. "http://www.w3.org/TR/html4/strict.dtd">