February has marked another significant month for the evolution of the web platform, with key advancements in security, developer ergonomics, and cross-browser compatibility. The latest Baseline digest highlights features that have achieved critical adoption milestones, empowering developers to build more robust, secure, and interoperable web experiences. This month’s updates underscore a continued commitment from major browser engines to foster a cohesive and capable web ecosystem.
Interop 2026 Kicks Off, Setting the Stage for Web Standardization
The year 2026 has commenced with the official launch of Interop 2026, a collaborative initiative focused on enhancing the interoperability of web features across different browser engines. This crucial effort brings together leading browser vendors, including Google (Chrome), Apple (Safari), Mozilla (Firefox), and Microsoft (Edge), who are the primary contributors to the development of browser rendering engines. The goal of Interop is to prioritize emerging web standards and ensure that high-priority features are consistently implemented across all major browsers, thereby reducing fragmentation and developer friction.
The Interop dashboard, accessible at wpt.fyi/interop-2026, provides a transparent view of test pass rates for identified key features. This initiative has been instrumental in driving the adoption of new web technologies, as it directly influences development roadmaps and resource allocation for browser vendors. The focus on interoperability ensures that developers can build with confidence, knowing that their applications will function reliably for a broader audience, regardless of their chosen browser. Historical data from previous Interop cycles indicates a strong correlation between participation in the program and the accelerated standardization and adoption of web APIs.
New Features Reach Baseline Status in February 2026
The Baseline initiative signifies features that have achieved widespread support across all major browser engines, making them reliable for general use. This month, several key technologies have reached this important milestone, offering developers new tools to enhance their web applications.
CSS shape() Function: Enhancing Declarative Shape Definitions
A significant addition to the CSS landscape is the introduction of the shape() function, now part of the <basic-shape> data type. This function offers a more intuitive and CSS-native approach to defining complex paths for properties like clip-path and offset-path. Unlike the existing path() function, which relies on a single string of SVG-like commands, shape() embraces standard CSS syntax. This paradigm shift allows developers to leverage familiar CSS units, such as rem, em, and percentages, alongside powerful functions like calc(), and even CSS variables.
This evolution significantly simplifies the creation of responsive and dynamic shapes. Developers who are more accustomed to CSS than the intricacies of SVG path strings will find shape() to be a more accessible and powerful tool. For instance, creating a star shape that adjusts its size based on the viewport width can now be achieved with greater ease and clarity. The ability to incorporate CSS variables also opens up new avenues for theming and dynamic styling of shapes, further enhancing the creative possibilities for web designers and developers.
Further details on the CSS shape() function can be found on MDN: developer.mozilla.org/docs/Web/CSS/Reference/Values/basic-shape/shape.
Trusted Types API: A New Frontier in DOM-Based XSS Prevention
In a critical move for web security, the Trusted Types API has now become Baseline, providing a robust defense against DOM-based cross-site scripting (XSS) attacks. This API mandates a more secure data handling process by requiring developers to channel data through predefined "policies" before it can be passed to sensitive "sinks"—APIs that are capable of executing code or rendering HTML, such as Element.innerHTML or eval().
The Trusted Types API works in conjunction with Content Security Policy (CSP). By enforcing these policies, web applications can guarantee that only sanitized or explicitly "trusted" data is utilized in ways that could lead to injection vulnerabilities. This fundamentally shifts security enforcement from a post-development manual review process to a platform-guaranteed mechanism. The implications for securing user data and preventing malicious code execution are profound, offering a proactive approach to mitigating one of the most persistent threats on the web. The adoption of Trusted Types is expected to significantly reduce the attack surface for many web applications, particularly those handling user-generated content.
Developers can delve deeper into the Trusted Types API documentation on MDN: developer.mozilla.org/docs/Web/API/Trusted_Types_API.
JavaScript Map Enhancements: getOrInsert() and getOrInsertComputed()
The JavaScript Map object has received a significant usability upgrade with the inclusion of getOrInsert() and getOrInsertComputed() methods. These additions streamline a common development pattern: checking for the existence of a key in a map, and if it’s absent, inserting a default value before returning it.
The getOrInsert() method is ideal for scenarios where a simple, predefined default value is sufficient. For more complex or computationally expensive default values, getOrInsertComputed() proves invaluable. This method accepts a callback function, which is only executed if the key is not found in the map. This lazy evaluation prevents unnecessary computation, optimizing performance for applications that rely heavily on data structures with potentially costly default initializations. These methods contribute to more concise and efficient JavaScript code, reducing boilerplate and improving developer productivity.
More information on Map.getOrInsert() is available on MDN: developer.mozilla.org/docs/Web/JavaScript/Reference/Global_Objects/Map/getOrInsert.
Zstandard Compression: A Modern Approach to Data Transfer
Zstandard (zstd), a modern compression algorithm known for its exceptional balance of high compression ratios and remarkably fast decompression speeds, has now become a Baseline option for HTTP Content-Encoding. This inclusion provides web developers with a powerful alternative to established algorithms like Gzip and Brotli.
Zstandard’s efficiency across a wide spectrum of data types makes it particularly effective for reducing the amount of data transferred over the network. This directly translates to faster page load times and a more responsive user experience, without imposing a significant CPU burden on the user’s device during decompression. As web applications continue to grow in complexity and data volume, Zstandard offers a crucial tool for optimizing performance and bandwidth utilization. The widespread adoption of zstd support is a testament to the ongoing efforts to improve web performance at a fundamental level.
Further details on HTTP Content-Encoding and Zstandard can be explored on MDN: developer.mozilla.org/docs/Web/HTTP/Reference/Headers/Content-Encoding.
dirname HTML Attribute Achieves Widely Available Status
The dirname HTML attribute has now reached Baseline Widely Available status, an important step for applications supporting multilingual users and complex text input. This attribute can be applied to <input> and <textarea> elements to automatically capture the text directionality (either ltr for left-to-right or rtl for right-to-left) as entered by the user.
When a form containing an element with the dirname attribute is submitted, the browser sends an additional field. This field is named according to the value provided in the dirname attribute and contains the detected text directionality. This feature is indispensable for applications that need to accurately process and display text in multiple languages, ensuring that the server receives the necessary context to render or store the information correctly. The widespread availability of dirname simplifies the implementation of bidirectional text support, enhancing the usability and accuracy of globalized web applications.
More comprehensive information on the dirname HTML attribute is available on MDN: developer.mozilla.org/docs/Web/HTML/Reference/Elements/input#dirname.
Looking Ahead: Continuous Improvement for the Web Platform
The monthly Baseline digests serve as a vital communication channel, highlighting the continuous progress in web standards and their adoption by major browser engines. The inclusion of features like the CSS shape() function, the Trusted Types API, and Zstandard compression demonstrates a clear trajectory towards a more secure, performant, and developer-friendly web. The ongoing commitment to interoperability through initiatives like Interop 2026 is crucial for maintaining a unified and robust web ecosystem.
Developers are encouraged to provide feedback and report any missed Baseline-related features through the issue tracker for the web-features project on GitHub. This collaborative approach ensures that the Baseline definition remains accurate and that the web platform continues to evolve in a direction that benefits both developers and users. The February 2026 updates represent significant strides, equipping developers with powerful new tools to build the next generation of web applications.
