Frontend Dogma

“interoperability” Archive

Supertopics: · subtopics:  (non-exhaustive) · glossary look-up: “interoperability”

Entry (Sources) and Other Related TopicsDate#
5 Questions for Jeremy Keith (ada+/fro)75
, , ,
Launching Interop 2025 (moz)74
, ,
Interop 2025 (pat)73
, ,
Interop 2025: Another Year of Web Platform Improvements (rac/dev)72
, ,
Interop 2024 Brings More Features to Baseline (rac/dev)71
, ,
The Success of Interop 2024 (jen/web)70
, ,
Interop and Hard Problems (bka)69
, ,
In the Future Using Top-Level “await” Might Be Cause a Backwards Compatibility Break in Node (eve)68
, , ,
Submit Your Proposals for Interop 2025 (rac/dev)67
, ,
Get Ready for Interop 2025: Your Chance to Shape the Web (stu/web)66
, ,
Interop 2024: Chrome at 100% for the Accessibility Focus Area (dev)65
, , ,
Interop 2024 Mid-Year Update (rac/dev)64
, ,
Safari 18—What Web Features Are Usable Across Browsers? (ste)63
, , , , ,
Web Platform Status (dev)62
, , ,
Native Support for CJS/ESM Interoperability Begins in Node.js 22 (hi)61
, , ,
Building an npm Package Compatible With ESM and CJS in 2024 (lir/sny)60
, , ,
History of JS Interop in Dart (dar)59
, ,
Runtime Compatibility (asc+/unj)58
, , , , , ,
The Web Just Gets Better With Interop 2024 (jen/web)57
, ,
Interop 2024 (rac/dev)56
, ,
Celebrate a More Interoperable Web With Interop 2023 (rac/dev)55
, ,
The Popular Vote of Interop 2024 (chr/fro)54
BCD Watch (mey+/iga)53
, , ,
Border Images in CSS: A Key Focus Area for Interop 2023 (dip/mdn)52
, , , ,
CSS Wrapped: 2023 (una+/dev)51
, , ,
Interop 2023 October Update (rac/dev)50
, ,
The Global “innerWidth” and “innerHeight” Properties Return the Width and Height of the Layout Viewport (sim/web)49
, ,
Get Ready for Interop 2024 (jen/web)48
Submit Your Proposals for Interop 2024 (rob+/dev)47
, ,
Interoperability With Specific Assistive Technologies or: “Does the Website Work on JAWS?” (kar)46
, , ,
Interop 2023 CMS Checkin (chr)45
, , , ,
Pushing Interop Forward in 2023 (jon+/web)44
Microsoft Edge and Interop 2023 (mse)43
, , ,
Interop 2023 (boc)42
Interop 2023: Continuing to Improve the Web for Developers (rob+/dev)41
Igalia and Interop 2023 (iga)40
,
Announcing Interop 2023 (moz)39
Interop 2022: End of Year Update (rac/dev)38
, , ,
Do We Need an Interop for Assistive Technologies? (hdv)37
, , ,
When New CSS Features Collide: Possibility and Complexity at the Intersections (rac)36
, ,
Interoperability (bka/htt)35
, , ,
Building Interoperable Web Components That Even Work With React (ada/css)34
,
Interop 2022: Browsers Working Together to Improve the Web for Developers (rac+/dev)33
,
Adversarial Interoperability (plu/sit)32
, ,
Testing Standards (ann)31
, ,
Dyslexia, [Typos,] and Web Compatibility (kar)30
, ,
Standards and Browser Compatibility (rod/mob)29
, , , , , ,
Web 2024—a Response to Robin Berjon’s Post (mar)28
, , , , , ,
Web Developers Less Concerned About Browser-Compatibility, More Concerned With HTML527
, ,
Where Is Interoperability for Social Media? (dhi/zdn)26
,
Old Browsers, Does It Matter? (kar)25
, ,
7 Solutions to the CSS3 Vendor Prefix Crisis (cra/sit)24
, , ,
The Impending CSS Vendor Prefix Catastrophe (cra/sit)23
, ,
Unfixed (mey)22
, ,
On the Vendor Prefixes Problem (bru)21
, ,
Call for Action: The Open Web Needs You Now (gla)20
, , ,
IE9 Tops Chrome, Firefox in HTML5 Compatibility (jbr/net)19
, , , ,
The W3C and the “HTML5 Isn’t Ready” Backlash (cra/sit)18
, , ,
The “spacer” Element Is Gone (hsi)17
Internet Explorer 8 Could Break Web Pages, Microsoft Warns16
, ,
Microsoft Debuts IE 8, Aims for CSS Interoperability15
, , ,
Versioning, Compatibility, and Standards (oth/web)14
, , ,
Beyond DOCTYPE: Web Standards, Forward Compatibility, and IE8 (aar/ali)13
, , , , , ,
The Need for Diversity (kar/w3c)12
, ,
Why HTML 5 Specification Matters? (kar/w3c)11
Marathon 2.0 (bur)10
, ,
HTML5 and XHTML 1.1+ Must Stop for Now (mho)9
, , , , , ,
Tag Soup: “innerHTML” Interoperability (or Lack Thereof) (hix)8
,
Cross Browser Compatibility (web)7
, , , , , ,
Extensibility and Interoperability (mno)6
, ,
Why XML Doesn’t Suck (tim)5
, ,
Language Barriers May Stifle Web Future (zdn)4
, ,
Waiting for the DOM3
, , , ,
W3C Hashes Out New Interoperability Standard (cli)2
Fear of Style Sheets (zel/ali)1
, , ,