auto-fill vs auto-fit: One CSS Word That Breaks Your Responsive Grid

·1 views

A widely shared CSS one-liner using repeat() with minmax() creates responsive card grids without media queries, but a subtle keyword choice can cause layout issues when fewer items are displayed. The difference lies in how auto-fill and auto-fit handle empty grid columns: auto-fill retains invisible placeholder tracks that consume available space, pushing visible cards to the left. auto-fit, by contrast, collapses empty tracks to zero width, allowing real cards to expand and fill the entire row evenly. Both keywords calculate the same number of columns upfront, so the bug only surfaces when item count drops below the maximum columns that fit. Swapping auto-fill for auto-fit in the grid-template-columns declaration is the only change needed to fix the layout for variable-count grids like search results or product listings.

Read the full story at DEV Community

This is an AI-generated summary. ShortSingh links to the original source for the complete article.

Discussion (0)

Differential Testing Method Catches Hidden Bugs in AI-Generated Code Patches

A software engineering approach called differential testing can expose behavioral regressions introduced by AI agent patches that conventional test suites miss. The method works by running both the original and patched code against identical inputs — including sequences of calls — and comparing outputs byte-for-byte. Standard unit tests often fail to catch bugs like faulty caching or shared state because they test single calls rather than call sequences, which is precisely where agent-generated patches tend to break behavior. The proposed gate involves freezing a baseline of recorded outputs from the original binary, then replaying a diverse corpus of inputs against the patched binary to detect any divergence. A reproducible corpus covering edge cases such as empty inputs, maximum lengths, and repeated keys is central to making the gate reliable.

0 comments Read more at DEV Community

ProgrammingDEV Community ·

Apple Launches ARKit 3.2 with Real-Time Motion Capture Ahead of iPhone 16

Apple introduced ARKit 3.2 at its WWDC 2026 keynote on June 5, 2026, ahead of the iPhone 16's planned September launch. The updated framework brings real-time skeletal motion capture at 60 fps, dual-camera depth tracking using the iPhone 16's front and rear sensors, and AI-driven AR personalization powered by Core ML. These capabilities are now bundled into a single framework, eliminating the need for third-party SDKs that developers previously relied on for motion capture and depth sensing. Apple will open the ARKit 3.2 beta to developers on June 12, 2026, with a full public release expected alongside the iPhone 16. Early industry interest is strong, with 68% of mobile developers surveyed by AppMaiters saying they plan to incorporate the new framework into upcoming projects.

0 comments Read more at DEV Community

ProgrammingHacker News ·

How to Stop Your Smart TV From Spying on You

Smart TVs are increasingly capable of collecting user data, raising privacy concerns among consumers. A technical guide outlines practical steps users can take to limit data collection and surveillance by their smart TV devices. Recommended measures include network-level controls, disabling certain features, and restricting internet access for the TV. The discussion on Hacker News attracted community interest, with users sharing additional tips and experiences. The guide aims to help everyday users take back control of their viewing privacy without necessarily replacing their devices.

0 comments Read more at Hacker News

ProgrammingDEV Community ·

CS Student Builds AI Agent That Turns Construction Site Updates Into Coordinated Actions

Daries, a computer science student and AI engineer from Accra, Ghana, developed OG Foreman, an AI-powered construction site coordinator submitted to the AllThingsAgentic Hackathon. The tool allows site teams to submit a single plain-language update, which the system then breaks down into structured project actions such as marking tasks complete, logging blockers, tracking material stock, and flagging shortages. Built on Google's Gemini, Agent Development Kit, Cloud Firestore, and a Next.js front end, the system deliberately separates language understanding from database write access to prevent errors. Consequential actions like material procurement are prepared and explained by the AI but require approval from an authorized human before execution. The project aims to solve a common construction management problem where critical site information gets lost across chat messages, calls, and spreadsheets rather than being captured in a central project record.

0 comments Read more at DEV Community