How does new CSS get into browsers?
If you have been doing web development for a few years, you may be under the impression that new features take a very long time to get into our browsers and therefore there is no point looking at features with little browser support. Things have changed and the time that it takes for a new feature to be designed and implemented can be very short indeed. We saw with CSS Grid Layout how all the browser vendors shipped their implementation within a single year; making the web platform interoperable is something that everyone working on CSS cares about.
When it comes to adding new CSS features to browsers, we sometimes wonder why one browser hasn’t added a feature that others already have. Ultimately, it comes down to the fact that each browser is a business with limited people working on browser implementations and decisions must be made about which features to implement next. You can help encourage vendors to implement new features by actively demonstrating a need for them. There are several ways to do this and the first is simply to use the feature. Browser vendors search the web to see how much usage a feature has when deciding what to prioritise. Another way is to write about features, even on a personal blog. This shows interest from web developers. You can also go to places such as the Edge Developer Feedback site ( wpdev.uservoice.com/ forums/257854-microsoft-edge-developer) or find the bug on Bugzilla for Firefox and Chrome and star it.
Above The CSS Exclusions feature noted to have ‘no signals’ from developers, therefore indicating little interest from the web development community.