| The Success of Interop 2024 (by/via) | | 55 |
| web-platform, browsers, support |
| Interop and Hard Problems (by) | | 54 |
| web-platform, browsers, support |
| Get Ready for Interop 2025: Your Chance to Shape the Web (by/via) | | 53 |
| web-platform, browsers, support |
| Submit Your Proposals for Interop 2025 (by/via) | | 52 |
| web-platform, browsers, support |
| Interop 2024: Chrome at 100% for the Accessibility Focus Area (via) | | 51 |
| browsers, google, chrome, accessibility |
| Interop 2024 Mid-Year Update (by/via) | | 50 |
| web-platform, browsers, support |
| Safari 18—What Web Features Are Usable Across Browsers? (by) | | 49 |
| browsers, apple, safari, support, css, javascript |
| Web Platform Status (via) | | 48 |
| websites, web-platform, browsers, support |
| Native Support for CJS/ESM Interoperability Begins in Node.js 22 (by) | | 47 |
| commonjs, esm, support, nodejs |
| History of JS Interop in Dart (via) | | 46 |
| javascript, dart, history |
| The Web Just Gets Better With Interop 2024 (by/via) | | 45 |
| web-platform, browsers, support |
| Interop 2024 (by/via) | | 44 |
| web-platform, browsers, support |
| Celebrate a More Interoperable Web With Interop 2023 (by/via) | | 43 |
| web-platform, browsers, support |
| The Popular Vote of Interop 2024 (by/via) | | 42 |
| web-platform |
| BCD Watch (by+/via) | | 41 |
| websites, browsers, support, web-platform |
| Border Images in CSS: A Key Focus Area for Interop 2023 (by/via) | | 40 |
| images, borders, css, browsers, web-platform |
| CSS Wrapped: 2023 (by+/via) | | 39 |
| css, browsers, support, retrospectives |
| Interop 2023 October Update (by/via) | | 38 |
| web-platform, browsers, support |
| The Global “innerWidth” and “innerHeight” Properties Return the Width and Height of the Layout Viewport (by/via) | | 37 |
| viewport, javascript, webkit |
| Get Ready for Interop 2024 (by/via) | | 36 |
| web-platform |
| Submit Your Proposals for Interop 2024 (by+/via) | | 35 |
| web-platform, browsers, support |
| Interoperability With Specific Assistive Technologies or: “Does the Website Work on JAWS?” (by) | | 34 |
| accessibility, screen-readers, assistive-tech, jaws |
| Interop 2023 CMS Checkin (by) | | 33 |
| html, syndication, rss, atom, semantics |
| Interop 2023 (via) | | 32 |
| web-platform |
| Microsoft Edge and Interop 2023 (via) | | 31 |
| web-platform, browsers, microsoft, edge |
| Pushing Interop Forward in 2023 (by+/via) | | 30 |
| web-platform |
| Interop 2023: Continuing to Improve the Web for Developers (by+/via) | | 29 |
| web-platform |
| Igalia and Interop 2023 (via) | | 28 |
| web-platform, igalia |
| Announcing Interop 2023 (via) | | 27 |
| web-platform |
| Interop 2022: End of Year Update (by/via) | | 26 |
| browsers, html, css |
| Do We Need an Interop for Assistive Technologies? (by) | | 25 |
| accessibility, browsers, screen-readers, assistive-tech |
| When New CSS Features Collide: Possibility and Complexity at the Intersections (by) | | 24 |
| slides, css, complexity |
| Interoperability (by/via) | | 23 |
| web-almanac, studies, research, metrics |
| Building Interoperable Web Components That Even Work With React (by/via) | | 22 |
| web-components, react |
| Interop 2022: Browsers Working Together to Improve the Web for Developers (by+/via) | | 21 |
| browsers, support |
| Adversarial Interoperability (by/via) | | 20 |
| terminology, concepts, link-lists |
| Testing Standards (by) | | 19 |
| standards, testing, web-platform |
| Web 2024—a Response to Robin Berjon’s Post (by) | | 18 |
| web, visions, javascript, web-components, w3c, web-workers, servo |
| 7 Solutions to the CSS3 Vendor Prefix Crisis (by/via) | | 17 |
| css, vendor-extensions, browsers, w3c |
| The Impending CSS Vendor Prefix Catastrophe (by/via) | | 16 |
| css, vendor-extensions, browsers |
| Call for Action: The Open Web Needs You Now (by) | | 15 |
| vendor-extensions, css, browsers |
| On the Vendor Prefixes Problem (by) | | 14 |
| vendor-extensions, css, browsers |
| Unfixed (by) | | 13 |
| css, vendor-extensions, browsers |
| The W3C and the “HTML5 Isn’t Ready” Backlash (by/via) | | 12 |
| html, w3c, browsers, support |
| The “spacer” Element Is Gone (by) | | 11 |
| html |
| Internet Explorer 8 Could Break Web Pages, Microsoft Warns | | 10 |
| internet-explorer, microsoft, browsers |
| Microsoft Debuts IE 8, Aims for CSS Interoperability | | 9 |
| internet-explorer, microsoft, browsers, css |
| Versioning, Compatibility, and Standards (by/via) | | 8 |
| browsers, standards, versioning, compatibility, webkit |
| Tag Soup: “innerHTML” Interoperability (or Lack Thereof) (by) | | 7 |
| html, browsers |
| Cross Browser Compatibility (via) | | 6 |
| browsers, compatibility, internet-explorer, microsoft, netscape, firefox, mozilla, opera |
| Extensibility and Interoperability (by) | | 5 |
| standards, extensibility, profiling |
| Why XML Doesn’t Suck (by) | | 4 |
| xml, internationalization, software-design |
| Waiting for the DOM | | 3 |
| javascript, dom, css, browsers, support |
| W3C Hashes Out New Interoperability Standard (by) | | 2 |
| w3c |
| Fear of Style Sheets (by/via) | | 1 |
| css, browsers, support, progressive-enhancement |
