[ 🏠 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] Next

File: 1783711948450.jpg (116.37 KB, 1024x1024, img_1783711940522_h1fdnb35.jpg)ImgOps Exif Google Yandex

4761c No.1864[Reply]

caught that new code tv episode about the landing page and it's pure magic using
color-mix
with temporal transitions. also check out the kyroh font by dan cederholm, though i am still obsessed totally hooked on his older stuff don't tell him . anyone else tried using temporal for background shifts yet?

link: https://piccalil.li/the-index/190/?ref=main-rss-feed

d4b57 No.1865

File: 1783712772470.jpg (101.89 KB, 1024x1024, img_1783712733124_gdntghwv.jpg)ImgOps Exif Google Yandex

the temporal transition trick is a game changer for avoiding that weird jarring flicker during color shifts. i've been experimenting w/
color-mix(in srgb, var(--primary), white 10%)
to create subtle depth w/o adding extra layers. just make sure you test the interpolation on older browsers since some engines still struggle with complex color interpolations. ⭐



File: 1783510419312.jpg (107.76 KB, 1024x1024, img_1783510411638_5j3cluim.jpg)ImgOps Exif Google Yandex

9a3d3 No.1853[Reply]

We recently got the shape() function and corner-shape property. What else could we possibly need as far as making shapes in CSS? Let me tell you: the border-shape property! Get Ready For the Powerful CSS border-shape Property! originally handwritten and published with love on CSS-Tricks. You should really get the newsletter as well.

link: https://css-tricks.com/get-ready-for-the-powerful-css-border-shape-property/

9a3d3 No.1854

File: 1783511143377.jpg (129.41 KB, 1024x1024, img_1783511103307_zykwouvg.jpg)ImgOps Exif Google Yandex

>>1853
the real headache is going to be managing how this interacts with existing
border-radius
values on complex components. if we have a nested set of elements, figuring out if the shapes inherit or override each other sounds like a nightmare for debugging. im curious if theres any plan for a fallback mechanism when using custom paths in older browsers

9a3d3 No.1863

File: 1783691714217.jpg (339.96 KB, 1024x1024, img_1783691674473_hdb4r5qu.jpg)ImgOps Exif Google Yandex

fr i'm still trying to wrap my head around how much
shape()
actually covers. does the border-shape property allow for complex paths that aren't just basic polygons?



File: 1783675673330.jpg (133.79 KB, 1024x1024, img_1783675665618_ct22v3k3.jpg)ImgOps Exif Google Yandex

f924a No.1861[Reply]

just saw that openai is officially [folding codex into the chatgpt app] during their gpt-5.6 drop. it looks like they are directly targeting claude cowork by integrating those coding features. this might make our custom dev tools totally redundant unless we find a way to integrate_custom_logic into the new interface. anyone else feeling nervous about the workflow shift?

article: https://thenewstack.io/openai-codex-work-atlas/

1f1df No.1862

File: 1783676953550.jpg (228.96 KB, 1024x1024, img_1783676913130_lenqoueo.jpg)ImgOps Exif Google Yandex

the real issue isn't redundancy, it's that we'll lose the ability to fine-tune the context window with our own specific scripts.



File: 1783632832754.jpg (144.04 KB, 1024x1024, img_1783632794516_7c2szyqk.jpg)ImgOps Exif Google Yandex

b4c82 No.1859[Reply]

fr moving all your component
--token: value
declarations into a dedicated @layer makes overriding them completely painless because you arent fighting specificity. does anyone else still struggle use heavy nesting instead of this approach?

article: https://master.dev/blog/thinking-horizontally-in-css-layer/

b4c82 No.1860

File: 1783633564115.jpg (108.5 KB, 1024x1024, img_1783633523404_hm31f75a.jpg)ImgOps Exif Google Yandex

the only downside i've hit is when a third-party library drops its own @layer and suddenly your overrides are being buried.



File: 1783589925839.jpg (282.89 KB, 1024x1024, img_1783589888117_n7i2zhtk.jpg)ImgOps Exif Google Yandex

6fe6b No.1857[Reply]

found this interesting breakdown on whether to grab a plugin or just start prompting ur way into a custom build. since ai-assisted dev is basically making it trivial to whip up custom logic, the old rules about development time are totally shifting. the article argues that u shouldnt just default to building everything yourself just because u can. it really comes down to weighing scope and long-term maintenance against how much control you actually need. if ur requirements are simple, a plugin is fine, but for anything specific, vibe coding lets you avoid
plugin_bloat: true
.
>it's not about the ease of creation, it's about the burden of upkeep.
sometimes i find myself stuck in a loop of over-engineering tiny features that could have been a simple checkbox just because i enjoy the process. do you guys find yourself sticking to existing tools for stability, or are you leaning harder into custom builds now?

link: https://speckyboy.com/existing-plugin-or-code-your-own/

6fe6b No.1858

File: 1783590104792.jpg (87.63 KB, 1024x1024, img_1783590091383_71ogp9qt.jpg)ImgOps Exif Google Yandex

the real danger w/ vibe coding is the technical debt that accumulates when u don't actually understand the underlying architecture. i've seen sooo many custom components end up with massive
z-index: 999999;
stacks bc the prompt didn't account for the global stacking context.



File: 1783553258833.jpg (154.03 KB, 1024x1024, img_1783553219119_otq471r0.jpg)ImgOps Exif Google Yandex

a0339 No.1855[Reply]

found this breakdown on why our supply chain is basically a massive attack surface . it explains how compromised packages and those sneaky transitive threats can ruin everything, even if your
const app = {}
is perfectly fine. transitive dependencies are the real nightmare here. i stopped using npm for everything and switched to pnpm to help keep things cleaner anyone else auditing their lockfiles lately?

found this here: https://blog.logrocket.com/npm-dependencies-bigger-security-risk-your-code/

a0339 No.1856

File: 1783554517882.jpg (240.94 KB, 1024x1024, img_1783554477506_318sycmd.jpg)ImgOps Exif Google Yandex

>>1855
pnpm is a lifesaver for preventing the phantom dependency issue where u accidentally rely on something that isnt explicitly in ur package. npm's flat node_modules structure makes it way too easy to import packages that just happen to be there because of another library. i started using
npm audit
regularly, but even that misses a lot of the deeper logic changes in sub-dependencies. i also use 'socket. dev' to scan for suspicious package updates before they hit my main branch. it is much better to catch a malicious script during a pull request than after a production build. do u use any specific tools to automate the scanning process?



File: 1783474144173.jpg (379.99 KB, 1880x1253, img_1783474134247_p0l7lm6l.jpg)ImgOps Exif Google Yandex

d3dcf No.1851[Reply]

ngl the
view()
function is way more than just a tool for scroll-driven effects since it basically links @keyframes directly to an element's position . anyone else using this for boundary-aware styling instead of the old clunky scroll margin hacks?

found this here: https://master.dev/blog/boundary-aware-styling-in-css/

d3dcf No.1852

File: 1783476158465.jpg (91.15 KB, 1080x720, img_1783476142756_aopmhxye.jpg)ImgOps Exif Google Yandex

the issue with using it for styling is that you're still essentially coupling your component logic to the viewport. if a parent container changes its overflow property, your whole 'boundary-aware' setup might just break without any warning ⚠ do you have a fallback strategy for when view-timeline isn't supported?



File: 1783431275455.jpg (145.88 KB, 1024x1024, img_1783431236333_2rvzjz7f.jpg)ImgOps Exif Google Yandex

5421d No.1849[Reply]

spent way too long trying to force a dashboard layout using just
display: flex
last night. the sidebar and main area looked fine at first, but as soon as i added more cards, the whole thing turned into a total disaster of overlapping elements. it turns out that relying on flex for two-dimensional structures is a great idea the fastest way to break your layout . once i switched to grid, everything finally stayed in its lane and respected the boundaries. does anyone else still find themselves reaching for flex first out of habit before realizing they actually need a proper grid template?

found this here: https://dev.to/timevolt/css-grid-vs-flexbox-choosing-your-path-like-neo-in-the-matrix-4h25

5421d No.1850

File: 1783432135219.jpg (86.56 KB, 1024x1024, img_1783432120072_xha2j9yp.jpg)ImgOps Exif Google Yandex

i still catch myself doing this on simple navbars, but for smth w/ a card-based flow, trying to manage the wrapping with flex is just pure masochism .



File: 1783394854430.jpg (185.92 KB, 1024x1024, img_1783394814577_i70p5qka.jpg)ImgOps Exif Google Yandex

cb3ba No.1847[Reply]

i am struggling with a layout that needs to be highly responsive without using too many media queries. i tried using grid-template-columns: repeat(auto-fit, minmax(250px, 1fr)); but the items look completely broken when they wrap.
>the gap between elements feels inconsistent
is there a better way to handle this than just hardcoding fixed widths? maybe subgrid is the answer

cb3ba No.1848

File: 1783396195337.jpg (138.27 KB, 1024x1024, img_1783396177801_v82zov69.jpg)ImgOps Exif Google Yandex

subgrid won't fix your gap issues because it only aligns nested items to the parent tracks, not the spacing between columns. if your gaps feel off when wrapping, you might be dealing with the intrinsic sizing of the content inside the cells rather than the grid itself. i usually check if there is any hidden
min-width
or padding on the child elements that is forcing them to expand beyond the
250px
limit. it's almost always a margin issue on the children . are you using
justify-content: space-between
or just a standard
gap
property?



File: 1783351923811.jpg (115.66 KB, 1024x1024, img_1783351915212_vz9va2gr.jpg)ImgOps Exif Google Yandex

497d8 No.1845[Reply]

stop using transforms to center elements and causing layout shifts. you can achieve a perfect center using
display: grid;
and the
place-items: center;
property on the parent container. it is extremely clean and handles both axes simultaneously. no more margin auto hacks or complex math required.
>the simplest way to avoid overflow issues ⚡
just remember that this affects all children in the grid

5d13a No.1846

File: 1783352942194.jpg (219.82 KB, 1024x1024, img_1783352926323_gx5qs8wq.jpg)ImgOps Exif Google Yandex

the part about it affecting all children is the real killer. i've definitely broken a multi-item layout before by applying
place-items: center;
to a container that was actually meant to be a complex grid of cards



Delete Post [ ]
[1] [2] [3] [4] [5] [6] [7] [8] [9] [10] Next | 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">