# Web platform Published articles for Web platform. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Calling for Interop 2027 proposals DevFeed: [Calling for Interop 2027 proposals]() Original publisher: [Read original article]() Author: Patrick Brosset Published: 2026-09-03T16:09:17Z Content type: article Language: en Sources: [Microsoft Edge Blog]() Topics: [Interop2027](), [interoperability](), [Web platform](), [web-standards](), [Web Development]() Tags: [browsers](), [developer](), [interop](), [interop2027](), [interoperability](), [uncategorized](), [web-platform]() ### AI overview The article opens the proposal process for Interop 2027, inviting submissions that address inconsistent implementation of standards-based web-platform features across browsers. ### Source excerpt The Interop 2027 call for proposals is open, submit your ideas now! Over the past six years, the I The post Calling for Interop 2027 proposals appeared first on Microsoft Edge Blog. ## How Baseline Can Help You Ship Less JavaScript DevFeed: [How Baseline Can Help You Ship Less JavaScript]() Original publisher: [Read original article]() Author: hello@smashingmagazine.com (Jad Joubran) Published: 2026-08-07T13:00:00Z Content type: tutorial Language: en Sources: [Articles on Smashing Magazine -- For Web Designers And Developers]() Topics: [JavaScript](), [Web platform](), [browser](), [Web](), [modern web development](), [Web Development]() Tags: [article](), [browser](), [coding](), [guide](), [javascript](), [techniques](), [web-platform]() ### AI overview A practical guide to auditing JavaScript dependencies against modern browser capabilities using Baseline. It explains how to identify libraries that the web platform can replace, estimate bundle-size savings, and account for browser support and fallback needs. ### Source excerpt The gap between "you need a library for this" and "the browser does this" keeps closing. A practical guide to auditing your dependencies and finding what the web platform can now handle for you. ## June in Servo: real world compat, media queries, SharedWorker, and more! DevFeed: [June in Servo: real world compat, media queries, SharedWorker, and more!]() Original publisher: [Read original article]() Author: The Servo Project Developers Published: 2026-07-31T00:00:00Z Content type: release Language: en Sources: [Servo Blog]() Topics: [servo engine]() Tags: [apis](), [release](), [rust](), [servo](), [servo-engine](), [servo-rendering-engine](), [web-browser](), [web-browser-engine](), [web-engine](), [web-platform](), [web-rendering-engine]() ### AI overview Servo 0.4.0 summarizes June changes, including web-platform features, media queries, and DOM APIs such as SharedWorker. ### Source excerpt Servo 0.4.0 contains all of the changes we landed in June, which came out to yet another record 558 commits (April: 534, May: 391). For security fixes, see § Security. We've shipped several new web platform features: 'attr()', in experimental mode (@Loirooriol, #45041) 'image()', 'closest-corner', and 'farthest-corner' in 'ellipse()' and 'circle()' (@Loirooriol, #45421) 'calc()' and other mathematical expressions can now be resolved later than parse time, e.g. sign(1em - 32px) (@Loirooriol, #45421) 'font-feature-settings' in '@font-face' (@simonwuelker, #45393) '@media (device-width)', '@media (device-height)', '@media (height)', '@media (aspect-ratio)', and their min- and max- variants (@jdm, @mrobinson, @nicoburns, @jschwe, #44978, #45707, #45490) '@media (orientation)' (@nicoburns, #45707) '@media (pointer)' and '@media (any-pointer)' (@nicoburns, #45681) '@media (hover)' and '@media (any-hover)' (@nicoburns, #45681) Plus a bunch of new DOM APIs: SharedWorker (@Taym95, #45786) console.dir() (@Taym95, #45109) customElementRegistry on Document and ShadowRoot (@shubhamg13, #45872) initialize() on CustomElementRegistry (@shubhamg13, @yezhizhen, #45903) new CustomElementRegistry() (@shubhamg13, #45791, #45550) textStream() on Request, Response, and Blob (@yezhizhen, #45864, #45861) setPointerCapture(), releasePointerCapture(), hasPointerCapture() on Element (@webbeef, #45048) ontouchstart, ontouchend, ontouchmove, ontouchcancel on Element (@stevennovaryo, #45049) crypto.subtle.digest() for KT128 and KT256 (@kkoyung, #45699) crypto.subtle.getPublicKey() for ML-KEM and ML-DSA (@kkoyung, #45252) This is another big update, so here's an outline: You can help! Security Real world compat Work in progress Embedding API For users and developers More on the web platform Garbage collection safety Performance and stability New contributors You can help! Servo is steadily becoming a bigger and busier project every month, and by June 2026, we'v ## How to use Chrome's Modern Web Guidance to prevent AI agents from writing legacy frontend code DevFeed: [How to use Chrome's Modern Web Guidance to prevent AI agents from writing legacy frontend code]() Original publisher: [Read original article]() Author: Emmanuel John Published: 2026-07-22T13:00:25Z Content type: tutorial Language: en Sources: [LogRocket Blog]() Topics: [AI-assisted coding](), [Agent Skills](), [Web platform](), [Front end](), [Web Development](), [CSS](), [HTML](), [browser](), [Retrieval Augmented Generation (RAG)]() Tags: [agent-skills](), [ai](), [ai-agents](), [ai-coding](), [browser](), [css](), [dev](), [frontend](), [how-to](), [html](), [retrieval-augmented-generation-rag](), [uncategorized](), [web-platform]() ### AI overview Chrome's Modern Web Guidance adds current web platform guidance, browser compatibility data, and best practices to AI coding workflows. The article explains how this can help agents favor simpler native HTML, CSS, and browser API solutions over unnecessary legacy JavaScript, dependencies, and outdated patterns. ### Source excerpt Chrome's Modern Web Guidance embeds modern web platform skills into AI coding agents, helping them choose native HTML, CSS, and browser APIs over legacy patterns. The post How to use Chrome's Modern Web Guidance to prevent AI agents from writing legacy frontend code appeared first on LogRocket Blog. ## New in Edge for developers - Style layout gaps, improve keyboard accessibility and migrate your PWA to a new origin DevFeed: [New in Edge for developers - Style layout gaps, improve keyboard accessibility and migrate your PWA to a new origin]() Original publisher: [Read original article]() Author: Patrick Brosset Published: 2026-07-07T16:04:36Z Content type: article Language: en Sources: [Microsoft Edge Blog]() Topics: [Edge](), [Web platform](), [Accessibility](), [CSS](), [PWA](), [Web Development](), [Agent Skill]() Tags: [accessibility](), [agent-skill](), [css](), [developers](), [edge](), [platform](), [release-notes](), [uncategorized](), [updates](), [web-platform]() ### AI overview This first edition of a Microsoft Edge developer series covers recent web platform updates: CSS gap decorations, the focusgroup attribute for keyboard navigation, same-site PWA origin migration, and additional rendering, text, layout, clipboard, and performance improvements. It also highlights upcoming features and a broader ecosystem update involving an AI coding agent skill. ### Source excerpt Welcome to New in Edge for developers, a new series featuring recent web platform updates in Microsoft Edge that help web developers build better sites and apps. In this first edition, we'll look at CSS gap de The post New in Edge for developers - Style layout gaps, improve keyboard accessibility and migrate your PWA to a new origin appeared first on Microsoft Edge Blog. ## Safari 27's Web Platform Test progress compared with Firefox and Chromium DevFeed: [Safari 27's Web Platform Test progress compared with Firefox and Chromium]() Original publisher: [Read original article]() Author: Alex Russell Published: 2026-07-06T00:00:00Z Content type: opinion Language: en Sources: [Alex Russell]() Topics: [browser](), [Web platform](), [Chromium](), [Firefox]() Tags: [browsers](), [chromium](), [competition](), [firefox](), [openweb](), [safari](), [test](), [web-platform](), [webdev]() ### AI overview An opinion article argues that Safari 27's quality and Web Platform Test improvements should be assessed against its slower release cadence and compared with Firefox and Chromium. It says Safari's time-weighted rate of improved tests is lower than those competitors. ### Source excerpt It's perilous to disagree with someone as wise and thoughtful as Jeremy, but for the past fortnight his post in response to Apple's iOS 27 marketing invades my quiet moments like a cricket in the attic. "Why", I ruminate, "should someone who understands the state of play give Apple credit for doing less than the minimum while rubbishing those who have consistently done more?" Contents Redux Features Over Tests Focus Areas Consequences You Do Not Have To Hand It To Them Everywhere You Turn Quality Has A Quality All Its Own Redux Like Apple's previous marketing of Safari 16.4 and Safari 26, the conjoined September release of Safari and iOS 27 documents an achingly slow release cycle. It would be one thing if the features or spec conformance were world-beating, but looking closely at the release notes, Safari 27 is set to deliver fixes for issues that, by and large, competing engines didn't suffer.1 Don't get me wrong: it's great that Apple is focusing on quality; it remains a persistent issue for Safari. But how much relief should long-suffering web developers expect? The best comparative measures come from the communal Web Platform Tests project. Comparing the current experimental builds with stable channel releases can illuminate the scale of change we can expect when the next major version of each browser launches:2 WPT Test Pass Rates (%) 90% is the minimum Apple requires across all WPT tests for competitors' engines in the EU and Japan where it has been forced to allow them (in theory). Safari barely clears the bar. Source: wpt.fyi It would appear that Safari is closing on Firefox, but this is misleading. Apple managed seven releases over the past year, or a roughly eight week cadence. Mozilla and Chromium, meanwhile, have released 12 versions to stable, or one a month. These serve as denominators (7.4 weeks vs. 4.3) when calculating rates of improvement. Safari's larger increase in passing tests between nightly and stable versions (1558 vs. 990 for Firefox) look ## May in Servo: user scripts, mp4 compat, blackboxing in DevTools, and more! DevFeed: [May in Servo: user scripts, mp4 compat, blackboxing in DevTools, and more!]() Original publisher: [Read original article]() Author: The Servo Project Developers Published: 2026-06-30T00:00:00Z Content type: release Language: en Sources: [Servo Blog]() Topics: [servo](), [Web platform](), [Document Object Model (DOM)](), [Memory Safety](), [API](), [Security](), [Forms](), [Accessibility](), [Nix](), [webgpu]() Tags: [developers](), [forms](), [html](), [memory-safety](), [release](), [rust](), [security](), [servo](), [servo-engine](), [servo-rendering-engine](), [web-browser](), [web-browser-engine](), [web-engine](), [web-platform](), [web-rendering-engine](), [webgpu](), [windows]() ### AI overview Servo 0.3.0 summarizes 391 commits made in May, adding web platform and DOM API support, improving forms and media compatibility, and fixing build issues on Windows, FreeBSD, and Nix environments. The release also includes memory safety fixes through a SpiderMonkey update, experimental Sanitizer improvements, IndexedDB changes, DevTools work, and ongoing WebGPU, accessibility, and performance development. ### Source excerpt Servo 0.3.0 contains all of the changes we landed in May, which came out to 391 commits (April: 534). For security fixes, see § Security. We've shipped several new web platform features: 'font-kerning: none' (@simonwuelker, #44634) 'font-variant-east-asian' (@simonwuelker, #44989) 'font-variant-ligatures' (@simonwuelker, #44903) 'font-variant-numeric' (@simonwuelker, #44950) 'font-variant-position' (@simonwuelker, #45142) mp4 files without fast start in