In this conversation, Adam Argyle, a CSS expert from the Google Chrome team, shares insights on the intricate process of adding features to CSS. He explains the journey from public proposals on GitHub to formal drafts, emphasizing the collaborative nature of development. Adam discusses the importance of community feedback and regular meetings in shaping standards. He also touches on exciting advancements like the CSS Houdini API and the role of developer relations. Packed with humor and personal anecdotes, their dialogue is a captivating blend of tech and creativity.
01:03:40
forum Ask episode
web_stories AI Snips
view_agenda Chapters
auto_awesome Transcript
info_circle Episode notes
volunteer_activism ADVICE
Proposing CSS Changes
Share use cases and problems succinctly on a GitHub issue in the CSS Working Group Drafts repo.
Include a strawman solution and a JavaScript demo to showcase your idea.
insights INSIGHT
Gauging Proposal Interest
The number of comments and the type of attention a proposal receives indicate community interest and potential success.
Consider how thought-provoking your proposal is and how much it offers to web development.
question_answer ANECDOTE
Logical Properties Bike-Shedding
Logical properties in CSS, while useful, lack a shorthand for all sides, causing frustration for developers like Adam.
The ongoing "bike-shedding" about syntax hinders progress despite the clear need for this feature.
Get the Snipd Podcast app to discover more snips from this episode
In this episode of Syntax, Scott and Wes talk with Adam Argyle about how stuff gets added to CSS.
LogRocket - Sponsor
LogRocket lets you replay what users do on your site, helping you reproduce bugs and fix issues faster. It’s an exception tracker, a session re-player and a performance monitor. Get 14 days free at logrocket.com/syntax.
Freshbooks - Sponsor
Get a 30 day free trial of Freshbooks at freshbooks.com/syntax and put SYNTAX in the “How did you hear about us?” section.
WPTs and standards are being nudged into a final state
44:20 - Roles
Spec author
Community Member
Print
Color
Internationalization
Box Model
AOM
JS APIs
Renderers
etc
Implementor
It’s like pub/sub, where spec authors pub and implementors sub, and the community tries to help shape the message that’s published while supporting the subscribers who need to implement and make it real