Tom Smykowski beta

Blog

๐Ÿ The Reason Why CSS Inset Property Was Not Called Position

๐Ÿ The Reason Why CSS Inset Property Was Not Called Position

Hi, my name is Tom Smykowski, I'm a staff full-stack engineer. I build and scale SaaS platforms to millions of users, working end-to-end from system architecture to frontend to mobile. On this blog I share what I learn about software engineering, career growth, and navigating the ever-evolving landscape of web technologies.

What This Article Covers

Explore the fascinating decision-making process behind the naming of CSS properties, focusing specifically on why the inset property wasn't simply called position. This article delves into the intricacies of CSS property naming conventions and provides insights into how these decisions impact developers' understanding and memory of CSS functionalities.

Questions This Article Answers

  • What is the CSS inset property, and why is it significant?
  • Why didn't the W3C name the inset property as position?
  • How do different CSS positioning properties like relative and absolute work together with inset?
  • What challenges do developers face in remembering various CSS properties?
  • How does naming impact the usability and adoption of CSS properties?

Length and Time

A thoughtful exploration of CSS property naming with practical insights for developers. Approximately 7 minutes to read.

Want to unlock the full story? Log in

โ† All posts