{"id":16902,"date":"2019-09-09T08:02:31","date_gmt":"2019-09-09T06:02:31","guid":{"rendered":"https:\/\/www.inovex.de\/blog\/?p=16902"},"modified":"2025-08-21T07:09:07","modified_gmt":"2025-08-21T05:09:07","slug":"houdini-future-of-css","status":"publish","type":"post","link":"https:\/\/www.inovex.de\/de\/blog\/houdini-future-of-css\/","title":{"rendered":"Houdini and the Future of CSS [State of the Web]"},"content":{"rendered":"

CSS is the styling language used to define the appearance of web contents. As web developers we rely on the existing implementation of CSS features across major browsers. Sometimes we face constraints that come with it, when a feature cannot be used in production because not every browser supports it. But with CSS Houdini this is about to change. Houdini’s goal is to enable web developers to extend the capabilities of CSS<\/strong> by providing APIs that make it possible to create custom CSS features<\/strong> and modify the browser rendering pipeline<\/strong>.<\/p>\n

Houdini is a task force which consists of engineers from Google, Mozilla, Apple, Microsoft and others who work together on creating specification drafts that will be standardised by the W3C. These specifications define several APIs which contribute to the goal of making CSS more extensible. These APIs are usually referred to when spoken of Houdini.<\/p>\n

This article will give you a brief overview of the Houdini specifications and their goal together with the current state of development.<\/p>\n

\n

<\/p>\n<\/div>