Published on 24.04.2024
TLDR: The CSS Working Group is seeking developer feedback on a proposed masonry layout feature for CSS Grid Level 3, which would finally bring native support for Pinterest-style layouts without JavaScript, while opening up creative possibilities beyond simple column-based layouts.
Link: Help us invent CSS Grid Level 3, aka "Masonry" layout
TLDR: Frontend Masters released a comprehensive 38,000-word guide covering the modern web development landscape, from core technologies to frameworks, tools, and career paths for frontend developers in 2024.
Link: The Front End Developer/Engineer Handbook 2024
TLDR: Despite modern frameworks gaining popularity, 90% of websites still use jQuery, with about a third running outdated versions that pose security risks - the jQuery team and OpenJS Foundation are pushing for upgrades as part of their Healthy Web campaign.
Link: Upgrading jQuery: Working Towards a Healthy Web
TLDR: Google has delayed the phase-out of third-party cookies in Chrome once again, pushing the timeline to early 2025 while they work through regulatory concerns and industry feedback.
Link: Update on the plan for phase-out of third-party cookies on Chrome
TLDR: April 24th is the inaugural "JS Naked Day," following the tradition of CSS Naked Day, encouraging developers to temporarily disable JavaScript to promote progressive enhancement and web standards.
Link: April 24 Is JS Naked Day
TLDR: Microsoft Edge team launched a dashboard tracking progress on top web platform developer pain points and interoperability gaps, focusing on features with stable specifications and cross-browser test results.
Link: Microsoft Edge - 2025 web platform top developer needs
TLDR: A frontend-focused adaptation of Jeff Dean's famous latency numbers, highlighting how network delays compound in web applications and emphasizing the importance of minimizing request waterfalls for user experience.
Link: Latency numbers every frontend developer should know
TLDR: The CSS scripting media feature now has broad browser support, allowing developers to provide alternative styles based on JavaScript availability, though implementation gotchas limit its practical utility.
Link: Detect JavaScript Support in CSS
TLDR: The maxlength HTML attribute creates poor user experience by silently truncating input, making interfaces feel broken and unresponsive - better to show errors and let users fix their input properly.
Link: Don't use the maxlength attribute to stop users from exceeding the limit
Disclaimer: This article was generated using newsletter-ai powered by claude-sonnet-4-20250514 LLM. While we strive for accuracy, please verify critical information independently.