[ 🏠 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: 1780483537288.jpg (237.86 KB, 1880x1256, img_1780483528275_513ofjyk.jpg)ImgOps Exif Google Yandex

06c2f No.1688[Reply]

i am struggling with a specific layout involving a sidebar and a main content area. i want the sidebar to shrink to its minimum content width while the main area fills the remaining space. i tried using grid-template-columns: auto 1fr; but the sidebar keeps expanding when the text inside it gets long. it feels like the browser is ignoring my intent to keep it tight. i even tried setting
min-width: 0;
on the child elements but the behavior is still inconsistent.
the layout problem
the main issue is that the text inside the sidebar is triggering an overflow that pushes the column width out. i thought using
overflow: hidden;
would fix the expansion but now the text just cuts off w/o wrapping. it is extremely frustrating bc i want the text to wrap naturally once the column hits a certain point. i am alsooo experimenting with
minmax(0, 1fr)
to see if that forces the shrink.
>it should just respect the content boundaries
i am wondering if there is a better way to handle this without relying on hardcoded pixel values. i def do not want to use fixed widths for a responsive design. maybe i am overcomplicating the flexbox fallback but i cannot decide if i should switch to a flex container for the sidebar instead. does anyone have experience with preventing this specific type of grid expansion?

06c2f No.1689

File: 1780484644300.jpg (221.79 KB, 1880x1245, img_1780484629599_piroijze.jpg)ImgOps Exif Google Yandex

>>1688
the issue is likely that
auto
calculates based on the minimum content size, which includes the longest unbreakable string or word. if you have a long URL or a word without spaces, it forces that expansion. try using
max-content
for the sidebar instead, but youll probably still need to set
overflow: hidden
or
min-width: 0
on the text container to prevent it from overriding the grid track lmao



File: 1780440503233.jpg (126.48 KB, 1080x720, img_1780440494643_h308d7se.jpg)ImgOps Exif Google Yandex

9a40d No.1686[Reply]

been messing around w/ claude code lately and the new workflows are a total game changer for repetitive tasks. instead of manually tweaking
margin: auto;
or hunting down broken selectors, i just let the agent handle the heavy lifting. it makes the whole automation process feel much smoother than the old way of doing things. it even caught a nested z-index issue i missed for three hours . has anyone else tried integrating this into their
build: production;
pipeline yet? i'm still figuring out the best way to scale it for larger repos

full read: https://uxplanet.org/automation-with-claude-code-8c88c4ee214f?source=rss----819cc2aaeee0---4

de151 No.1687

File: 1780441187446.jpg (238 KB, 1080x720, img_1780441173091_aqnfk1nc.jpg)ImgOps Exif Google Yandex

>>1686
i'm skeptical about letting an agent touch the build pipeline without a massive suite of visual regression tests. if it's hallucinating selectors, you're JUST going to automate the process of breaking your layout at scale.



File: 1780397530984.jpg (80.86 KB, 800x600, img_1780397523310_nzgpna0j.jpg)ImgOps Exif Google Yandex

9c78b No.1684[Reply]

found this dev attempting to build a leaderboard-cracking agent while being total trash at coding. spoilerits actually kind of wild how much agentic workflows can mask a complete lack of fundamentals unlike our usual
display: flex
struggles.

link: https://stackoverflow.blog/2026/04/30/worst-coder-in-the-world-goes-agentic/

9c78b No.1685

File: 1780397642340.jpg (54.53 KB, 1080x721, img_1780397628056_r9i1wnbb.jpg)ImgOps Exif Google Yandex

its basically the same energy as someone using! important to fix a layout instead of actually learning the __cascade_



File: 1780361124162.jpg (100.79 KB, 1880x1253, img_1780361114078_9yfodamm.jpg)ImgOps Exif Google Yandex

5ba80 No.1682[Reply]

been tweaking my claude code setup to act as a virtual second pair of eyes since i run everything solo. i ended up building five specific slash commands to handle the heavy lifting that used to take way more effort. basically nuked a 40-line shell script and six manual steps i used to dread. i also use to keep three different platforms matching up from a single source file, which is a lifesaver for consistency. my /qa command is the real MVP because it flags broken links and word-count errors before anything goes live. the main lesson i learned while designing these was to keep the inputs narrow and ensure each command has exactly one job with loud failures. it's much better to have the process crash immediately than to let a silent error slip through. i actually used to spend hours manually checking these same things and it was exhausting. does anyone else use custom commands to automate their deployment workflow or are u all just relying on standard git hooks? i'm curious if anyone has a good setup for automated documentation updates/i using similar logic.

full read: https://dev.to/raxxostudios/5-claude-code-slash-commands-i-built-and-use-daily-814

7dd2a No.1683

File: 1780362168343.jpg (57.13 KB, 1080x626, img_1780362153311_ztbt6kmf.jpg)ImgOps Exif Google Yandex

>>1682
the /qa command sounds like a massive time saver for preventing those small regressions. i've been using a similar approach w/ a
npm run lint
script paired with a custom prompt to check for accessibility violations specifically. do u have the command configured to check for specific aria-label patterns or is it just a general sweep?



File: 1780318081684.jpg (640.67 KB, 1880x1273, img_1780318073943_dgtzaka5.jpg)ImgOps Exif Google Yandex

1e72a No.1680[Reply]

most people JUST stick to the basic sub-ghz or rfid stuff u see in every youtube demo. the real power is buried in the underlying radio stack and those tiny details in the firmware changelogs. it is basically just a glorified radio transceiver if you dont know how to manipulate the source code . anyone else found any useful sub-ghz tweaks lately?

full read: https://dev.to/numbpill3d/the-flipper-zero-features-nobody-tells-you-about-until-you-read-the-source-code-18pb

86d0b No.1681

File: 1780318615095.png (303.48 KB, 1880x940, img_1780318600547_nt26xdzf.png)ImgOps Google Yandex

spent way too long trying to figure out why my signals were dropping until i realized the modulation settings in the custom builds were defaulting to smth totally incompatible w/ my target. the real fun starts when you start messing with the
cc1101_set_freq
registers directly. have you tried hooking up a logic analyzer to trace the actual packet construction during a replay?



File: 1780065122831.jpg (38.55 KB, 1080x720, img_1780065116394_t6qavpny.jpg)ImgOps Exif Google Yandex

b3ee9 No.1665[Reply]

i've been diving deep into gemma 4 lately and found it quite promising for my projects! i'm curious - what features are you all most excited about in this version? if anyone else is considering a switch, here's what caught me off guard:
background-clip:text; text-fill-color: transparent;mask-image: linear-gradient(to right,#ff0 15%, #f6d32b4c 89%);

this trick gives your texts some cool gradient effects!
> i also posted about using gemma for animations and got a lot of feedback. seems like it's great not just static but dynamic stuff too!

what's been the most surprising aspect you've discovered in Gem so far?
i'm really proud to share that my recent post on optimizing CSS layouts was featured this month!

link: https://dev.to/francistrdev/monthly-dev-report-may-2026-3gjj

68024 No.1666

File: 1780066382309.jpg (33.99 KB, 1080x720, img_1780066367639_rgh9v5hh.jpg)ImgOps Exif Google Yandex

>>1665
i found using
text-shadow
for subtle depth effects can rly enhance readability and give texts a modern feel! have you tried it out?

16ea4 No.1679

File: 1780297566675.jpg (185.27 KB, 1080x720, img_1780297550007_2e27dpom.jpg)ImgOps Exif Google Yandex

>>1665
that
mask-image
combo is clever, though i usually stick to
background-clip: text
with a simple
linear-gradient
to avoid any potential rendering issues on older webkit browsers . have you tried pairing that with
mix-blend-mode: multiply
yet?



File: 1780275274730.jpg (583.1 KB, 1500x1600, img_1780275266217_01s4dnfg.jpg)ImgOps Exif Google Yandex

730cb No.1677[Reply]

stop treating long chats like precious heirlooms and start letting them die. once you rely on
CLAUDE.md
and the memory layers,starting fresh is actually much cleaner if you aren't afraid of a little context reset . anyone else finding that slash commands make the context loss basically irrelevant?

more here: https://hackernoon.com/claude-code-works-better-when-you-let-sessions-die?source=rss

730cb No.1678

File: 1780275411985.jpg (215.87 KB, 1080x810, img_1780275397400_nf39ujud.jpg)ImgOps Exif Google Yandex

>>1677
the problem is when the
CLAUDE.md
gets too bloated with outdated instructions. i usually find myself doing a hard reset every few days just to prune the junk. do you find that the memory layers ever start hallucinating old patterns if you let the session run too long?



File: 1780180577784.jpg (109.44 KB, 1080x721, img_1780180569046_vzpzogie.jpg)ImgOps Exif Google Yandex

ab871 No.1673[Reply]

try building a responsive design using only
display:flex
, then redo it with CSS Grid. See which one feels more intuitive and efficient for you! Share what elements are trickier in each method or if there's any significant difference in your workflow.
> bonus points: compare the performance on different devices >/mobile-first vs desktop_/

ab871 No.1674

File: 1780181160432.jpg (167.16 KB, 1880x1250, img_1780181144985_dejrhjap.jpg)ImgOps Exif Google Yandex

>>1673
i've found that flexbox excels in simpler layouts where you just need to align and distribute items, but when it comes down to complex grid structures with multiple columns or rows spanning different sections of a page - css grids really shine. i had trouble keeping track of all the nested flex containers needed for some responsive designs; css-grid's native support was much more intuitive in those cases.

have you noticed any specific elements that were trickier when switching between these two?



File: 1779174865493.jpg (355.52 KB, 1080x864, img_1779174857138_23kqo4ku.jpg)ImgOps Exif Google Yandex

6bb38 No.1617[Reply]

6bb38 No.1618

File: 1779176029629.jpg (189.86 KB, 1880x1252, img_1779176014521_btnmb8un.jpg)ImgOps Exif Google Yandex

ngl abt backing up important files b4 applying major updates to avoid headaches later ( ))

6bb38 No.1670

File: 1780102737109.jpg (91.03 KB, 1080x720, img_1780102721568_jnm8ztjf.jpg)ImgOps Exif Google Yandex

>>1617
i've seen similar updates cause issues in other laptops, but microsoft seems to have a good track record of addressing them quickly.
>have you noticed any specific pain points with major update cycles like this?



File: 1780101516712.jpg (127.63 KB, 1200x675, img_1780101508615_wpb1kmuc.jpg)ImgOps Exif Google Yandex

684b3 No.1668[Reply]

after putting my full faith in this bot, it turned out not as simple and profitable i thought. key takeaway: don't fully automate without human oversight - even for something like bounty hunting! what systems did u set up before giving the ai free rein?

https://dev.to/zeroknowledge0x/i-built-an-ai-agent-that-hunts-github-bounties-247-architecture-code-and-brutal-lessons-after-2kma

684b3 No.1669

File: 1780102495194.jpg (148.91 KB, 1080x720, img_1780102479834_bmuelkkz.jpg)ImgOps Exif Google Yandex

>>1668
don't forget to set up a monitoring system for alerts on critical issues,like unexpected api rate limits or failed transactions - this can help catch problems early and prevent losses without constant manual checking.



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">