- My Interop 2027 Rankings

Another year, another Interop. Interop is a collaborative effort by organisations that implement web technology in browsers to identify what should be prioritised. Firefox has created ‘2027 Web Platform Feature Ranking’ for ranking the 2027 Interop proposals.

As is my civic duty, I’ve submitted my rankings. I’ve reproduced them here with comment. Truth be told, I’m interested in almost all of these proposals, but I’ve only ranked the ones I’m most interested in. If everything is highlighted, nothing is highlighted.

  1. Targeted SVG improvements. My love for SVG filters is unhealthy, unhinged, and bordering on perverse. I want the bugs fixed and support for various capabilities improved.
  2. CSS reading-flow and reading-order properties. These properties have great potential to fix a lot of accessibility problems.
  3. CSS @supports at-rule(). Certainly valuable to lots of cases, but something that is particularly valuable to me when creating demos of new features for articles. Progressive enhancement is great in many cases, but I need to show what I’m trying to show, and a fallback will confuse. I need to be able to detect support and act on it.
  4. CSS flex-wrap: balance. There is so much utility in being able to balance a flexbox’s items when wrapped. I’m already using it as a progressive enhancement.
  5. CSS line-clamp property. line-clamp has been so desired by so many people for so long. I’m already using the vendor prefixed -webkit-line-clamp in many places.
  6. Customisable/stylable <select>. Select has been reimplemented in so many hacky ways that are often especially terrible for accessibility. Native support on the web platform would be so wonderful.
  7. Progressive rendering of JPEG XL and AVIF images. I love AVIF and especially JPEG XL, and would love preview versions of images while the rest downloads. It would be such a great usability thing for users with no added effort required.
  8. CSS corner-shape property. I want fancy corners on my elements. They offer so many fun opportunities and are otherwise tricky to implant.
  9. JavaScript Temporal. I don’t need Temporal to live; I just need Date to die.
  10. CSS scroll-triggered animations. Scroll-driven animations have more utility in my opinion, and they’ll be seeing wider browser support soon, but scroll-triggered animation support would complement them nicely.
  11. CSS gap decorations. A commonly needed/wanted but tricky to achieve effect that often needs funky border, padding, or pseudo hacks. Browser support would be great.
  12. Responsive iframes. I’ve previously written about making iframes responsive, and it is a pain to do. I’m not actually sure the design of the system is perfect, but hopefully that can be fixed, I’d like to see this capability in browsers.
  13. Device Posture API. I’m not yet sure that foldable devices are ‘the future’, but I think they’re positioned to become a lot more popular in the near future. The Device Posture API will allow us to do so much with them on the web and bring parity with that which can be done in native applications.

For my wider thoughts on what I’d like to see added to the web platform, read my Web Platform Wishlist. For more perspectives, you can read the rankings of Ana Rodrigues, Tyler Sticka, and Paweł Grzybek.