/
Navigation
Chronicles
Browse all articles
Explore
Semantic exploration
Research
Entity momentum
Nexus
Correlations & relationships
Story Arc
Topic evolution
Drift Map
Semantic trajectory animation
Posts
Analysis & commentary
Pulse API
Tech news intelligence API
Browse
Entities
Companies, people, products, technologies
Domains
Browse by publication source
Handles
Browse by social media handle
Detection
Concept Search
Semantic similarity search
High Impact Stories
Top coverage by position
Sentiment Analysis
Positive/negative coverage
Anomaly Detection
Unusual coverage patterns
Analysis
Rivalry Report
Compare two entities head-to-head
Semantic Pivots
Narrative discontinuities
Crisis Response
Event recovery patterns
Connected
Search: /
Command: ⌘K
Embeddings: large
TEXXR

Chronicles

The story behind the story

days · browse · Enter similar · o open

Microsoft, Google, and others partner to improve browser compatibility, focusing on five areas, including CSS Flexbox, CSS Grid, and CSS sticky positioning

Google and Microsoft have announced that they're joining forces with other companies such as Igalia, as well as the “broader web community” …

Neowin João Carrasqueira

Context & Ripple Effects

Microsoft, Google and Igalia are targeting layout features that routinely require consistent implementation across browser engines. The effort follows earlier cross-vendor work on unified MDN Web Docs and WebAssembly, where Google, Microsoft and Mozilla also collaborated on shared web foundations.

The partnership is an early operational step toward the later Interop 2022 benchmark, which gave developers’ compatibility complaints a defined set of test areas. It matters because it moves browser competition away from divergent behavior in core CSS features.

First-order effects

  • Microsoft, Google, Igalia and participating web developers align work on Flexbox, CSS Grid and sticky positioning, concentrating compatibility effort on the same high-use layout behaviors.
  • Web developers gain a clearer cross-browser target for those CSS features rather than treating each engine’s behavior as a separate implementation constraint.

Second-order effects

  • Browser teams outside the initial group face stronger pressure to match the shared behavior, especially as Apple, Google, Microsoft and Mozilla later adopted a common compatibility benchmark.
  • Documentation and testing become more valuable shared infrastructure: the earlier MDN Web Docs consolidation and the later Interop benchmark both reduce the cost of identifying which browser behavior should prevail.

Third-order effects

  • If repeated across standards work, browser differentiation shifts further from proprietary rendering quirks toward performance, tooling and product integration.
  • Cross-vendor benchmarks can make developer-reported compatibility gaps a more durable mechanism for setting browser-engine priorities.

The trend: Browser makers are increasingly treating interoperability as shared infrastructure while competing on layers above the web platform.

Discussion

  • @chromiumdev @chromiumdev on x
    You told us what you needed, and we listened! In 2021, we aim to eliminate the five top compatibility pain points on the web: Google blog post: https://web.dev/... Microsoft: https://blogs.windows.com/... https://twitter.com/...
  • @tomayac Thomas Steiner on x
    Super happy about the #compat2021 initiative: https://web.dev/.... Eliminating 5 top compatibility pain points on the Web.
  • @mahemoff @mahemoff on x
    Just noticed Google deprecated its own https://goo.gl/ shortener and recommends bitly etc (though really why are shorteners even needed on Twitter anymore?) https://twitter.com/...
  • @iansherr Ian Sherr on x
    I feel like I read this type of story ever few years and nothing comes of it? https://twitter.com/...
  • @msedgedev @msedgedev on x
    We're excited to join @chromiumdev and the broader web community in kicking off #Compat2021, a cross-browser effort aiming to fix frustrating compatibility issues across browsers in a number of key areas. Read more on the Edge blog: https://blogs.windows.com/...