# Web Developers Published articles for Web Developers. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Shopify extends lifeline to Tailwind as vibe coding erodes web dev platform's bottom line DevFeed: [Shopify extends lifeline to Tailwind as vibe coding erodes web dev platform's bottom line]() Original publisher: [Read original article]() Author: Brandon Vigliarolo Published: 2026-09-10T19:43:55Z Content type: news Language: en Sources: [www.theregister.com - Articles]() Topics: [Web Development](), [modern web development]() Tags: [acquisition](), [acquisitions](), [ai-and-ml](), [css](), [devops](), [foss](), [framework](), [open-source](), [shopify](), [tailwind](), [vibe-coding](), [web](), [web-developers]() ### AI overview Shopify's acquisition gives the open-source CSS framework Tailwind a stable long-term home amid pressure on web development platforms from vibe coding. ### Source excerpt Acquisition gives open source CSS framework 'a stable long-term home' ## Opaque, Interoperable Passkey Records (and a Go API) DevFeed: [Opaque, Interoperable Passkey Records (and a Go API)]() Original publisher: [Read original article]() Author: Filippo Valsorda Published: 2026-07-20T22:33:32Z Content type: article Language: en Sources: [Filippo Valsorda]() Topics: [WebAuthn](), [Passkeys](), [Go Language](), [Security](), [API](), [passwords]() Tags: [api](), [authentication](), [go](), [password](), [security](), [web](), [web-developers]() ### AI overview The article proposes interoperable passkey record encodings for WebAuthn credentials, allowing applications to store records as opaque strings similar to password hashes. It also presents a potential Go API for handling these records. ### Source excerpt Passkey records are an interoperable format for WebAuthn credentials, similar to password hash strings. I propose a potential crypto/passkey Go API based on them. ## Experimenting with the proposed Cross-Origin Storage API in Transformers.js DevFeed: [Experimenting with the proposed Cross-Origin Storage API in Transformers.js]() Original publisher: [Read original article]() Author: Thomas Steiner Published: 2026-06-23T00:00:00Z Content type: tutorial Language: en Sources: [Hugging Face - Blog]() Topics: [AI, ML & Data Engineering]() Tags: [ai-models](), [announcement](), [api](), [artificial-intelligence](), [asr](), [browser](), [cache](), [chrome](), [chrome-extension](), [cos](), [cross-origin-storage](), [inference](), [javascript](), [on-device](), [open-source](), [storage](), [transformers](), [transformers-js](), [wasm](), [web](), [web-apps](), [web-developers](), [web-standards](), [webassembly]() ### AI overview A tutorial that uses Transformers.js browser inference examples to examine duplicate model and WebAssembly downloads across origins and the proposed Cross-Origin Storage API. ### Source excerpt We're on a journey to advance and democratize artificial intelligence through open source and open science. ## Goodbye innerHTML, Hello setHTML: Stronger XSS Protection in Firefox 148 DevFeed: [Goodbye innerHTML, Hello setHTML: Stronger XSS Protection in Firefox 148]() Original publisher: [Read original article]() Author: Tom Schuster Published: 2026-02-24T13:00:02Z Content type: tutorial Language: en Sources: [Mozilla Hacks - the Web developer blog]() Topics: [Vulnerabilities](), [Web platform](), [Web Development]() Tags: [api](), [browser](), [featured-article](), [firefox](), [firefox-releases](), [html](), [javascript](), [security](), [vulnerabilities](), [web-developers]() ### AI overview Firefox 148 ships the standardized Sanitizer API, including setHTML(), to sanitize untrusted HTML and reduce XSS risk. The article explains replacing innerHTML assignments, configuring allowed elements and attributes, and combining the API with Trusted Types for stronger protection. ### Source excerpt Cross-site scripting (XSS) remains one of the most prevalent vulnerabilities on the web. The new standardized Sanitizer API provides a straightforward way for web developers to sanitize untrusted HTML before inserting it into the DOM. Firefox 148 is the first browser to ship this standardized security enhancing API, advancing a safer web for everyone. We [...] The post Goodbye innerHTML, Hello setHTML: Stronger XSS Protection in Firefox 148 appeared first on Mozilla Hacks - the Web developer blog. ## Launching Interop 2026 DevFeed: [Launching Interop 2026]() Original publisher: [Read original article]() Author: Jake Archibald Published: 2026-02-12T17:07:24Z Content type: article Language: en Sources: [Mozilla Hacks - the Web developer blog]() Topics: [Web](), [Web platform](), [web-standards](), [browsers](), [Test coverage](), [dashboards](), [WebRTC](), [view transitions](), [CSS]() Tags: [apple](), [browser](), [css](), [featured-article](), [firefox](), [google](), [interop](), [microsoft](), [mozilla](), [uncategorized](), [view-transitions](), [web](), [web-developers](), [web-platform](), [webrtc]() ### AI overview Mozilla's Interop Project is launching Interop 2026, continuing its cross-browser effort to improve web compatibility through shared priorities and Web Platform Tests. The article reviews Interop 2025's progress, including higher overall scores, broader cross-browser support for major web platform features, and improved reliability for existing features such as WebRTC, CSS Flexbox, and CSS Grid. ### Source excerpt The Interop Project is a cross-browser initiative to improve web compatibility in areas that offer the most benefit to both users and developers. The group, including Apple, Google, Igalia, Microsoft, and Mozilla, takes proposals of features that are well defined in a sufficiently stable web standard, and have good test suite coverage. Then, we come [...] The post Launching Interop 2026 appeared first on Mozilla Hacks - the Web developer blog. ## Rendering on the Web DevFeed: [Rendering on the Web]() Original publisher: [Read original article]() Author: Addy Osmani X GitHub Bluesky Jason Miller X GitHub Homepage Published: 2026-01-05T08:00:00Z Content type: article Language: en Sources: [web.dev: Articles]() Topics: [Server-side rendering](), [Web Development](), [HTML](), [JavaScript](), [Web](), [browser](), [Document Object Model (DOM)](), [Interaction to Next Paint]() Tags: [article](), [browser](), [developers](), [html](), [interaction-to-next-paint](), [javascript](), [performance](), [web](), [web-developers]() ### AI overview This article explains how web developers can choose where application logic and rendering should run. It defines server-side rendering, client-side rendering, prerendering, hydration, and rehydration, and discusses their tradeoffs using page-performance metrics such as TTFB, FCP, INP, and TBT. ### Source excerpt Recommendations for implementing logic and rendering in apps. ## How Interrupting Your Users Can Create Accessibility Concerns DevFeed: [How Interrupting Your Users Can Create Accessibility Concerns]() Original publisher: [Read original article]() Author: Chris Published: 2025-12-22T12:30:00Z Content type: article Language: en Sources: [Blog-Main]() Topics: [Web Accessibility (a11y)](), [Web Content Accessibility Guidelines](), [digital accessibility](), [Website](), [Users](), [notifications]() Tags: [accessibility](), [accessibility-guidelines](), [accessibility-ux](), [automatic](), [digital-accessibility](), [display](), [people-with-disabilities](), [send](), [stop](), [time](), [timeout](), [web-accessibility](), [web-content-accessibility-guidelines](), [web-developers](), [websites]() ### AI overview The article explains how dynamic website behavior, including unexpected notifications, automatic refreshes, and other interruptions, can create accessibility barriers for screen reader users and people with attention disorders. It discusses WCAG Success Criterion 2.2.4, which says interruptions can be postponed or suppressed except in emergencies, while noting that this Level AAA criterion is not generally required for conformance goals. ### Source excerpt If you're building a dynamic website, there are plenty of valid reasons to interrupt your users. You might need to tell someone if their session is about to timeout, for example, or you might want your content to refresh periodically in order to show more up-to-date information. ## Celebrating 20 years of MDN DevFeed: [Celebrating 20 years of MDN]() Original publisher: [Read original article]() Author: joe-walker Published: 2025-07-23T00:00:00Z Content type: article Language: en Sources: [MDN Blog]() Topics: [Interop2027]() Tags: [collaboration](), [community](), [contributors](), [developers](), [docs](), [documentation](), [ecosystem](), [firefox](), [github](), [mozilla](), [open](), [platform](), [web](), [web-developers](), [web-platform](), [web-standards]() ### AI overview MDN marks its 20th anniversary, reflecting on its evolution from a community wiki into a broad resource for web developers and web-platform documentation. The article thanks its contributors and celebrates collaboration across the open web. ### Source excerpt MDN turns 20! Let's look at how we started, how MDN became the most trusted resource for web developers, the impact it's had on the open web, and yes, there's cake, too. ## Giving V8 a Heads-Up: Faster JavaScript Startup with Explicit Compile Hints DevFeed: [Giving V8 a Heads-Up: Faster JavaScript Startup with Explicit Compile Hints]() Original publisher: [Read original article]() Author: Marja Hölttä Published: 2025-04-29T00:00:00Z Content type: article Language: en Sources: [V8]() Topics: [V8](), [JavaScript](), [Chrome](), [Web app](), [Web Development]() Tags: [chrome](), [javascript](), [main-thread](), [performance](), [speed](), [thread](), [web-app](), [web-developers]() ### AI overview The article explains how V8 chooses between eager and deferred JavaScript compilation and how Explicit Compile Hints can improve startup performance. It describes Chrome 136 support for selecting individual files for eager compilation, while warning that compiling too much can increase time and memory use. ### Source excerpt Getting JavaScript running fast is key for a responsive web app. Even with V8's advanced optimizations, parsing and compiling critical JavaScript during startup can still create performance bottlenecks. Knowing which JavaScript functions to compile during the initial script compilation can speed up web page loading. When processing a script loaded from the network, V8 has to choose for each function: either compile it immediately ("eagerly") or defer this process. If a function that hasn't been compiled is later called, V8 must then compile it on demand. If a JavaScript function ends up being called during page load, compiling it eagerly is beneficial, because: During the initial processing of the script, we need to do at least a lightweight parse to find the function end. In JavaScript, finding the function end requires parsing the full syntax (there are no shortcuts where we could count the curly braces - the grammar is too complex). Doing the lightweight parsing first and the actual parsing afterwards is duplicate work. If we decide to compile a function eagerly, the work happens on a background thread, and parts of it are interleaved with loading the script from the network. If we instead compile the function only when it's being called, it's too late to parallelize work, since the main thread cannot proceed until the function is compiled. You can read more about how V8 parses and compiles JavaScript in here. Many web pages would benefit from selecting the correct functions for eager compilation. For example, in our experiment with popular web pages, 17 out of 20 showed improvements, and the average foreground parse and compile times reduction was 630 ms. We're developing a feature, Explicit Compile Hints, which allows web developers to control which JavaScript files and functions are compiled eagerly. Chrome 136 is now shipping a version where you can select individual files for eager compilation. This version is particularly useful if you have a "core file" wh ## Launching Interop 2025 DevFeed: [Launching Interop 2025]() Original publisher: [Read original article]() Author: James Graham Published: 2025-02-13T16:59:13Z Content type: article Language: en Sources: [Mozilla Hacks - the Web developer blog]() Topics: [Web Development]() Tags: [accessibility](), [browsers](), [css](), [featured-article](), [firefox](), [interop](), [interoperability](), [storage](), [view-transitions](), [web](), [web-developers](), [web-platform](), [webrtc](), [zoom]() ### AI overview Interop 2025 coordinates browser vendors around 19 web-platform focus areas to improve cross-browser compatibility. It follows Interop 2024, whose shared test pass rate reached 95% in current browser releases. ### Source excerpt Interop 2025 continues the mission to make the web more consistent across browsers, building on 2024's 95% interoperability score. This year, 19 focus areas target key developer needs and long-standing issues, including WebRTC improvements, Storage Access API, and CSS Zoom. The post Launching Interop 2025 appeared first on Mozilla Hacks - the Web developer blog. ## Platform Strategy, JavaScript-First Development, and the Web's Mobile Constraints DevFeed: [Platform Strategy, JavaScript-First Development, and the Web's Mobile Constraints]() Original publisher: [Read original article]() Author: Alex Russell Published: 2024-10-27T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [JavaScript](), [Front end](), [Web Development](), [Development](), [Mobile](), [Web](), [React]() Tags: [browsers](), [competition](), [cost](), [development](), [ecosystems](), [frontend](), [javascript](), [legacy](), [mobile](), [performance](), [speed](), [strategy](), [web](), [web-developers](), [webdev]() ### AI overview The article argues that JavaScript-first frontend practices and desktop-oriented tools have contributed to increasingly costly failures to deliver usable web experiences on phones. It frames platform strategy around making the web easier, faster, and more secure for everyday tasks. ### Source excerpt This post is an edited and expanded version of a now-mangled Mastodon thread. Contents Platforms Are Competitions ...and We're Losing Win Condition You Do It To Yourself, And That's What Really Hurts Groundhog Day Reboot Some in the JavaScript community imagine that I harbour an irrational dislike of their tools when, in fact, I want nothing more than to stop thinking about them. Live-and-let-live is excellent guidance, and if it weren't for React et. al.'s predictably ruinous outcomes, the public side of my work wouldn't involve educating about the problems JS-first development has caused. But that's not what strategy demands, and strategy is my job.1 I've been holding my fire (and the confidences of consulting counterparties) for most of the last decade. Until this year, I only occasionally posted traces documenting the worsening rot. I fear this has only served to make things look better than they are. Over the past decade, my work helping teams deliver competitive PWAs gave me a front-row seat to a disturbing trend. The rate of failure to deliver usable experiences on phones was increasing over time, despite the eye-watering cost of JS-based stacks teams were reaching for. Worse and costlier is a bad combo, and the opposite of what competing ecosystems did. Native developers reset hard when moving from desktop to mobile, getting deeply in touch with the new constraints. Sure, developing a codebase multiple times is more expensive than the web's write-once-test-everywhere approach, but at least you got speed for the extra cost. That's not what web developers did. Contemporary frontend practice pretended that legacy-oriented, desktop-focused tools would perform fine in this new context, without ever checking if they did. When that didn't work, the toxic-positivity crowd blamed the messenger.2 Frontend's tragically timed turn towards JavaScript means the damage isn't limited to the public sector or "bad" developers. Some of the strongest engineers I know find thems ## Announcing Official Puppeteer Support for Firefox DevFeed: [Announcing Official Puppeteer Support for Firefox]() Original publisher: [Read original article]() Author: James Graham Published: 2024-08-07T15:44:40Z Content type: article Language: en Sources: [Mozilla Hacks - the Web developer blog]() Topics: [Puppeteer](), [Firefox](), [Automation](), [webDriver](), [Chrome](), [Web]() Tags: [automation](), [blog](), [browser](), [chrome](), [featured-article](), [firefox](), [mozilla](), [testing](), [web](), [web-developers](), [webdriver]() ### AI overview Puppeteer version 23 adds first-class Firefox support, enabling browser automation and end-to-end testing against both Firefox and Chrome. The implementation uses the cross-browser WebDriver BiDi protocol, with examples including console log capture and device emulation. ### Source excerpt We're pleased to announce that, as of version 23, the Puppeteer browser automation library now has first-class support for Firefox. This means that it's now easy to write automation and perform end-to-end testing using Puppeteer, and run against both Chrome and Firefox. The post Announcing Official Puppeteer Support for Firefox appeared first on Mozilla Hacks - the Web developer blog. ## MDN partners with Scrimba to enhance web development learning DevFeed: [MDN partners with Scrimba to enhance web development learning]() Original publisher: [Read original article]() Author: hermina-condei Published: 2024-07-09T00:00:00Z Content type: article Language: en Sources: [MDN Blog]() Topics: [Web Development](), [Learning](), [Development](), [Web](), [modern web development]() Tags: [blog-post](), [course](), [education](), [learning](), [partnership](), [web](), [web-developers](), [web-development]() ### AI overview MDN announces Scrimba as its recommended course partner for the MDN Curriculum. The partnership aims to provide web developers with a complete, high-quality learning experience aligned with MDN's standards and curriculum, including some free content for registered users. ### Source excerpt We have chosen Scrimba as a course partner for the MDN Curriculum. This blog post explores what the partnership means practically, and how we will provide an even better web education experience together. ## Why Browsers Get Built DevFeed: [Why Browsers Get Built]() Original publisher: [Read original article]() Author: Alex Russell Published: 2024-03-10T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [browsers](), [Web platform]() Tags: [browsers](), [competition](), [platform](), [strategy](), [web-developers](), [web-platform](), [webdev]() ### AI overview The article presents two-and-a-half reasons for building a browser and proposes ways to distinguish them. It argues that browser-building strategies differ by their relationship to operating systems, team composition, and whether the browser serves a broader web-platform strategy or another agenda. ### Source excerpt There are only two-and-a-half reasons to build a browser, and they couldn't be more different in intent and outcome, even when they look superficially similar. Learning to tell the difference is helpful for browser project managers and engineers, but also working web developers who struggle to develop theories of change for affecting browser teams. Like Platform Adjacency Theory and The Core Web Platform Loop, this post started1 as a set of framing devices that I've been sketching on whiteboards for the best part of a decade. These lenses aren't perfect, but they provide starting points for thinking about the complex dynamics of browsers, OSes, "native" platforms, and the standards-based web platform. Contents Web As Platform Distinguishing Traits The OS Agenda Browsers as Bridges Browsers as Moats Tipping Points Distinguishing Traits Searchbox Pirates Distinguishing Traits Implications The reasons to build browsers are most easily distinguished by the OSes they support and the size and composition of their teams ("platform" vs. "product"). Even so, there are subtleties that throw casual observers for a loop. In industrial-scale engineering projects like browser construction, headcount is destiny, but it isn't the whole story. Web As Platform This is simultaneously the simplest and most vexing reason to build a browser. Under this logic, browsers are strategically important to a broader business, and investments in platforms are investments in their future competitiveness compared with other platforms, not just other browsers. But none of those investments come good until the project has massive scale. This strategy is exemplified by the ambitions of Netscape, crisply captured by Andreesen's quip that the goal was to render Windows "a poorly debugged set of device drivers". The idea is that the web is where the action is, and that the browser winning more user Jobs To Be Done follows from increasing the web platform's capability. This developer-enabling flywheel aim ## The Performance Inequality Gap, 2024 DevFeed: [The Performance Inequality Gap, 2024]() Original publisher: [Read original article]() Author: Alex Russell Published: 2024-01-31T00:00:00Z Content type: article Language: en Sources: [Alex Russell]() Topics: [modern web development](), [JavaScript](), [Web Development](), [CSS](), [HTML]() Tags: [browsers](), [complexity](), [css](), [html](), [javascript](), [performance](), [web-developers](), [webdev]() ### AI overview The 2024 update presents performance budgets for first loads under five seconds on P75 devices and networks, with separate guidance for JavaScript-heavy and markup-centric sites. It recommends global baseline budgets when audience data is unavailable and emphasizes the cost of JavaScript on low-end hardware. ### Source excerpt The global device and network situation continues to evolve, and this series is an effort to provide an an up-to-date understanding for working web developers. So what's changed since last year? And how much HTML, CSS, and (particularly) JavaScript can a new project afford? Contents The Budget, 2024 JavaScript-Heavy Markup-Heavy Calculate Your Own Situation Report Mobile Desktop Takeaways The Great Branch Mispredict The Budget, 2024 In a departure from previous years, two sets of baseline numbers are presented for first-load under five seconds on 75th (P75) percentile devices and networks1; one set for JavaScript-heavy content, and another for markup-centric stacks. Budget @ P75 Markup-based JS-based Total Markup JS Total Markup JS 3 seconds 1.4MiB 1.3MiB 75KiB 730KiB 365KiB 365KiB 5 seconds 2.5MiB 2.4MiB 100KiB 1.3MiB 650KiB 650KiB This was data was available via last year's update, but was somewhat buried. Going forward, I'll produce both as top-line guidance. The usual caveats apply: Performance is a deep and nuanced domain, and much can go wrong beyond content size and composition. How sites manage resources after-load can have a big impact on perceived performance. Your audience may justify more stringent, or more relaxed, limits. Global baselines matter because many teams have low performance management maturity, and today's popular frameworks - including some that market performance as a feature - fail to ward against catastrophic results. Until and unless teams have better data about their audience, the global baseline budget should be enforced. This isn't charity; it's how products stay functional, accessible, and reliable in a market awash in bullshit. Limits help teams steer away from complexity and towards tools that generate simpler output that's easier to manage and repair. JavaScript-Heavy Since at least 2015, building JavaScript-first websites has been a predictably terrible idea, yet most of the sites I trace on a daily basis remain mired in script. ## Saying goodbye to third-party cookies in 2024 DevFeed: [Saying goodbye to third-party cookies in 2024]() Original publisher: [Read original article]() Author: chris-mills Published: 2023-12-08T00:00:00Z Content type: article Language: en Sources: [MDN Blog]() Topics: [Chrome](), [Web](), [browser](), [Firefox](), [personalization]() Tags: [analytics](), [browser](), [chrome](), [firefox](), [personalization](), [privacy](), [web](), [web-developers]() ### AI overview The article explains Chrome's plan to deprecate third-party cookies, beginning with 1% of users in Q1 2024 and increasing thereafter. It describes how cookies support website state and personalization, distinguishes first-party from third-party cookies, and outlines legitimate cross-site uses as well as privacy risks such as tracking. ### Source excerpt The tail end of 2023 welcomes positive news for web privacy, as Chrome announces it is to join Firefox and Safari in deprecating third-party cookies in 2024. Find out more details about these changes, and what they mean for web developers. ## Announcing The Astro Technology Company DevFeed: [Announcing The Astro Technology Company]() Original publisher: [Read original article]() Author: Fred Schott Published: 2022-01-12T00:00:00Z Content type: article Language: en Sources: [The Astro Blog]() Topics: [Astro](), [Web Development](), [Open Source](), [Developer experience]() Tags: [astro](), [community](), [funding](), [open-source](), [technology](), [web-developers](), [web-development]() ### AI overview The Astro Technology Company has launched with $7 million in seed funding to develop Astro, grow its open source community, and build a stronger platform for web development. Astro is a modern web build tool that uses partial hydration to reduce unused JavaScript and improve website performance, while supporting components from React, Preact, Svelte, and Vue. ### Source excerpt The Astro Technology Company has formed to support the Astro open source project and build a better platform for web developers everywhere. ## How We Share Knowledge as a Web Collective DevFeed: [How We Share Knowledge as a Web Collective]() Original publisher: [Read original article]() Published: 2021-07-14T00:00:00Z Content type: article Language: en Sources: [SoundCloud Backstage Blog]() Topics: [Web](), [Frameworks]() Tags: [best-practices](), [collective](), [developers](), [europe](), [knowledge-sharing](), [learn](), [platform](), [projects](), [remote-work](), [web](), [web-developers](), [work]() ### AI overview SoundCloud describes how its Web Collective shares knowledge across cross-functional teams. The weekly meeting focuses on web topics, internal frameworks, technical challenges, platform-specific best practices, and open discussion, with an intentionally low-pressure format that welcomes questions, unfinished ideas, and participants from different platforms. ### Source excerpt There's no single platform team that consists of only web engineers at SoundCloud, even though we consider ourselves to be part of the "Web... ## Designing Marketing Emails via predefined Modules in Salesforce Email Studio DevFeed: [Designing Marketing Emails via predefined Modules in Salesforce Email Studio]() Original publisher: [Read original article]() Author: Steffen Mueller GitHub profile Linkedin profile Published: 2021-04-19T00:00:00Z Content type: article Language: en Sources: [Trivago]() Topics: [email](), [modules](), [HTML](), [CSS](), [Web Development]() Tags: [article](), [css](), [email](), [engineering](), [frontend](), [html](), [modules](), [salesforce](), [web-developers]() ### AI overview The article explains trivago's approach to helping marketers design HTML emails with predefined modules in Salesforce Email Studio. It describes the technical constraints of email clients and devices, and discusses automating repetitive personalized email workflows at scale. ### Source excerpt When techies hear about email marketing and designing HTML emails, they typically roll their eyes and think of a very boring field of work. In this article, we hopefully can explain to you why t... ## Responsive Components: a Solution to the Container Queries Problem DevFeed: [Responsive Components: a Solution to the Container Queries Problem]() Original publisher: [Read original article]() Published: 2018-02-27T08:12:12Z Content type: article Language: en Sources: [Philip Walton]() Topics: [Responsive Design](), [CSS](), [Web APIs](), [Document Object Model (DOM)](), [web design]() Tags: [components](), [css](), [demo](), [developer](), [responsive-design](), [web-apis](), [web-developers]() ### AI overview This article explains how to build responsive components that adapt to their containing environment without waiting for CSS container queries. It proposes using currently available web APIs as a progressive enhancement, with generic base styles and environment-specific overrides that continue to work when JavaScript or newer browser features are unavailable. ### Source excerpt Container queries is a proposal that would allow web developers to style DOM elements based on the size of a containing element rather than the size of the browser viewport. If you're a web developer, you've probably heard about container queries before. For about as long as we've had responsive web design, we've had developers asking for them (initially element queries, then changing to container queries). ## Why Web Developers Need to Care about Interactivity DevFeed: [Why Web Developers Need to Care about Interactivity]() Original publisher: [Read original article]() Published: 2017-12-19T17:25:23Z Content type: article Language: en Sources: [Philip Walton]() Topics: [interactive website](), [Web Development](), [JavaScript](), [Document Object Model (DOM)](), [browser]() Tags: [browser](), [javascript](), [main-thread](), [technical](), [time-to-interactive](), [web-developers]() ### AI overview The article explains web interactivity as a page's ability to respond quickly to user input. It identifies delayed JavaScript loading and a busy browser main thread as the two primary causes of poor responsiveness, while focusing mainly on main-thread work. ### Source excerpt Anyone who's browsed the web on their phone has, at one point or another, experienced this situation: You open a web page and click on something, but nothing happens. You click on it again--still nothing. ## The Google Analytics Setup I Use on Every Site I Build DevFeed: [The Google Analytics Setup I Use on Every Site I Build]() Original publisher: [Read original article]() Published: 2017-02-08T18:45:45Z Content type: tutorial Language: en Sources: [Philip Walton]() Topics: [Google Analytics](), [Web](), [Code](), [async](), [Script](), [HTTP]() Tags: [async](), [code](), [google-analytics](), [http](), [libraries](), [web-developers]() ### AI overview A practical guide to configuring Google Analytics for web developers, covering how developers can use analytics to understand site usage and how to load analytics.js asynchronously without degrading user experience or blocking critical resources. ### Source excerpt Google Analytics is a powerful yet quite complicated tool. And unfortunately, the truth is most people who use it don't reap its full benefits. There's a lot of excellent and free content out there that explains how to use Google Analytics, but most of it is rather narrowly focused on use cases that primarily apply to marketers and advertisers; very little is geared toward web developers who simply want to better understand how people are using the sites they build. ## Lake Wobegon Web Development DevFeed: [Lake Wobegon Web Development]() Original publisher: [Read original article]() Author: Edward Faulkner Published: 2016-12-30T16:23:02Z Content type: opinion Language: en Sources: [Edward Faulkner]() Topics: [Development](), [Web Development](), [developer tooling](), [web applications]() Tags: [ci](), [developer-tools](), [developers](), [development](), [layout](), [test](), [tools](), [web-developers](), [web-development](), [xss]() ### AI overview This commentary argues that comprehensive developer tools are essential for improving web user experiences. Because the average development team's skills will remain uneven as more people enter web development, tools can package best-practice knowledge and sensible defaults for building capable, reliable applications. ### Source excerpt There is a strain of thought in the web development community that believes there's a tension between having comprehensive developer tools and delivering good user experiences: This is exactly backwards. At the scale of the entire web, better tools are the only way to deliver better experiences. The ## CSS Houdini Task Force and Its Significance for Web Styling DevFeed: [CSS Houdini Task Force and Its Significance for Web Styling]() Original publisher: [Read original article]() Published: 2016-03-24T22:43:07Z Content type: article Language: en Sources: [Philip Walton]() Topics: [CSS](), [web-standards](), [Web Development]() Tags: [css](), [standards](), [web-developers]() ### AI overview The article introduces the CSS Houdini Task Force, explains its connection to browser rendering engines and the web standards process, and discusses why web developers should care about it. ### Source excerpt Earlier this year I had the privileged of attending the CSS Houdini Task Force face-to-face meeting in Sydney, Australia. While there I got to meet many of the Houdini members (most of whom work on browser rendering engines), and I got to see a bit of how the standards process works. [Next page]()