惯性聚合 高效追踪和阅读你感兴趣的博客、新闻、科技资讯
阅读原文 在惯性聚合中打开

推荐订阅源

L
Lohrmann on Cybersecurity
Martin Fowler
Martin Fowler
Engineering at Meta
Engineering at Meta
腾讯CDC
钛媒体:引领未来商业与生活新知
钛媒体:引领未来商业与生活新知
Microsoft Azure Blog
Microsoft Azure Blog
G
Google Developers Blog
TaoSecurity Blog
TaoSecurity Blog
博客园_首页
Vercel News
Vercel News
Hugging Face - Blog
Hugging Face - Blog
D
Darknet – Hacking Tools, Hacker News & Cyber Security
Last Week in AI
Last Week in AI
cs.CL updates on arXiv.org
cs.CL updates on arXiv.org
T
The Exploit Database - CXSecurity.com
量子位
Project Zero
Project Zero
A
Arctic Wolf
小众软件
小众软件
NISL@THU
NISL@THU
C
CERT Recently Published Vulnerability Notes
有赞技术团队
有赞技术团队
MongoDB | Blog
MongoDB | Blog
博客园 - 聂微东
OSCHINA 社区最新新闻
OSCHINA 社区最新新闻
N
News and Events Feed by Topic
宝玉的分享
宝玉的分享
freeCodeCamp Programming Tutorials: Python, JavaScript, Git & More
T
Troy Hunt's Blog
P
Privacy & Cybersecurity Law Blog
Security Latest
Security Latest
B
Blog
酷 壳 – CoolShell
酷 壳 – CoolShell
D
DataBreaches.Net
Schneier on Security
Schneier on Security
The Hacker News
The Hacker News
K
Kaspersky official blog
C
Check Point Blog
Hacker News: Ask HN
Hacker News: Ask HN
cs.AI updates on arXiv.org
cs.AI updates on arXiv.org
Webroot Blog
Webroot Blog
www.infosecurity-magazine.com
www.infosecurity-magazine.com
人人都是产品经理
人人都是产品经理
AI
AI
Cisco Talos Blog
Cisco Talos Blog
MyScale Blog
MyScale Blog
Cloudbric
Cloudbric
B
Blog RSS Feed
S
Schneier on Security
P
Palo Alto Networks Blog

Chip Cullen

The need for importance, and AI: Chip Cullen An updated Colorosetta: Chip Cullen The Return of the Font Combinator!: Chip Cullen Changing the number of an item in an ordered list: Chip Cullen My pizza dough recipe as of May 2025: Chip Cullen Gonna try to be a bit more personal: Chip Cullen How I built dynamic social media images in Eleventy using Cloudinary: Chip Cullen My current approach to AI : Chip Cullen Lessons Learned Surviving a Major Product Launch: Chip Cullen How to Build a Drop Down Menu with Modern CSS: Chip Cullen How to stop page scrolling when you have an open dialog element: Chip Cullen Distraction Driven Development: Chip Cullen How I learned to code: the art of letting go: Chip Cullen In praise of the switch statement: Chip Cullen Project stuck? Think about how you’re breaking it down & question everything: Chip Cullen So how did the onboarding experiment go?: Chip Cullen Ideas for an Onboarding Checklist: Chip Cullen I really like Post Mortems: Chip Cullen Raise Red Flags Early: Chip Cullen How to mock fetch requests in React Testing Librarty tests: Chip Cullen Running a Structured Meeting: Chip Cullen Adding the View Transitions API to my personal site: Chip Cullen A Lightweight Way to Read GraphQL Data: Chip Cullen How to make a color changing favicon: Chip Cullen Using a Pros/Cons list to help navigate technical discussions: Chip Cullen How to use variable fonts from Google Fonts: Chip Cullen A new website: now on Eleventy!: Chip Cullen How to Truncate Type at More Than One Line with Just CSS: Chip Cullen Colorosetta: the VS Code Extension!: Chip Cullen Browser Dev Tools: Element Inspector Popover: Chip Cullen The Link with rel=preload is a Seperate Thing: Chip Cullen How to have Dark & Light Mode Images that also works with User Choice: Chip Cullen Don’t use Viewport Units for Font Size on their own: Chip Cullen A little known Media Query: Aspect Ratio: Chip Cullen Meta thinking: Managing Decisions: Chip Cullen Give Your To-Do's Context: Chip Cullen Say What the Impact is when Reporting Issues: Chip Cullen Firefighting 101: How to Manage Breakages: Chip Cullen How to Deal With Large Pieces of Technical Debt: Chip Cullen Make Your Request Clear: Chip Cullen Analytics events, HTML classes, and protecting against refactoring: Chip Cullen How We Removed jQuery from a large app: Chip Cullen New tool: ColoRosetta: Chip Cullen What width and height attributes should you use with responsive images?: Chip Cullen Django 3.1 gotcha: Referrer Policy has a new default, and it might break iframes and links: Chip Cullen A Javascript Component Pattern: Chip Cullen CSS min(), max() and clamp() Functions: Chip Cullen Pointer Events and Inline Elements in Chrome: Chip Cullen Resolving a github repo and a new Create React App: Chip Cullen How to POST *Data* with the Fetch API: Chip Cullen The Contrast Triangle: Chip Cullen Advice on interviewing for Junior Developers: Chip Cullen Life Lessons Learned From Running a Marathon: How to do something really hard: Chip Cullen A (Brief) intro to Search Engine Structured Data: Chip Cullen Javascript Fallback Values on Variables and Booleans - a hard lesson: Chip Cullen Alfred Tip: Quickly Access Common URLs: Chip Cullen Responsive Images in Hugo - by Laura Kalbag: Chip Cullen Making a Gatsby Site with Multiple Content Types: Chip Cullen How to Create and Use Fixtures in Cypress Tests: Chip Cullen Fixing the 'Bad Interpreter' Error from AWS and Python 3.7: Chip Cullen Creating a Canonical Tag in a Django Template: Chip Cullen Responsive spacing with viewport and ch units: Chip Cullen Welcome to my New Design - 2019: Chip Cullen Django Templates: Block and If statements don’t work like you might expect: Chip Cullen Books I Read in 2018: Chip Cullen Lifehack: 4 ways to help tame common email noise: Chip Cullen How to make better Pull Requests: Adding Steps to Test: Chip Cullen The unsung develpment tool: Spreadsheets: Chip Cullen Troubleshooting Adding and Removing EventListeners: with Arguments, Debounced, and in a React Class: Chip Cullen How to Fake the Window Object in Jest and Enzyme: Chip Cullen Migrating From Wordpress to Hugo: Chip Cullen Background Repeat and its Possibilities: Chip Cullen Getting Started With Front End Tests: a Mindset: Chip Cullen Migrating a Blog - An Opportunity for a Content Inventory: Chip Cullen Moving to Hugo: Chip Cullen JavaScript events: .target vs .currentTarget: Chip Cullen Things I wish I knew when starting with Python: Chip Cullen Leading Ampersands for modifiers in Sass: An anti-pattern: Chip Cullen How to get rid of the "You have mail" message in your terminal: Chip Cullen Why three typefaces rule the web, and what you can do about it: Chip Cullen You shouldn't worry about Section 508 - it's Section 504: Chip Cullen Looping Video Backgrounds: pointers and pitfalls: Chip Cullen How to “preview” a click event tag in the Google Tag Manager console: Chip Cullen Moving on from a technology, or: life after Drupal: Chip Cullen Don’t be a dumb developer: Chip Cullen Two level breadcrumbs with CSS :only-child: Chip Cullen Simplicity comes with experience: Chip Cullen Do the least amount possible: Chip Cullen SVGs vs. Icon Fonts: Two points in favor of Icon Fonts: Chip Cullen Accessible links without underlines: Chip Cullen The Strategic Job Hunt: Chip Cullen Surviving Getting Laid Off: Chip Cullen How to structure your typography in Sass: Chip Cullen Layer Cake: A Responsive Design Layout Pattern: Chip Cullen Creativity is yet to come in Web Design: Chip Cullen Front End Testing with Wraith: A Step by Step Recipe: Chip Cullen Where to begin? How I start a visual design for the web: Chip Cullen If you could only have five Google Fonts: Chip Cullen Why SVG is so cool (or: what happens when you're late to the party on something): Chip Cullen How to apply classes to elements with CKEditor 4, in Drupal 7: Chip Cullen
Using CSS Custom Properties and Logical Properties Together: Chip Cullen
2022-05-22 · via Chip Cullen

Let's say you have a large website, with lots of views, with lots of components. And the designs for these components have spacing that shifts across breakpoints. It would be very easy for components over time to 'drift' and not line up with their neighbors. How can you wrangle that?

CSS Custom Properties + CSS Logical Properties

These will allow you to have less code, that is more consistent, at scale.

What are CSS Custom Properties?

That's the proper name for CSS Variables:

:root {
  --brand-color: blue;
}

body {
  color: var(--brand-color);
}

What are CSS Logical Properties?

CSS Logical properties are sort-of-newish properties that control layout in a logical way rather than in a physical way. The idea is that these values are writing-direction agnostic.

/* phyiscal property */
margin-left: 10px;
/* logical property */
margin-inline-start: 10px;

There are a bunch of properties that have been added that follow this idea.

If you are most used a left-to-right, top-to-bottom language (e.g. English, Latin-based languages), it's easiest to think of it like this:

  • top and bottom are together the block direction
    • top is block-start
    • bottom is block-end
  • left and right are together the inline direction
    • left is inline-start
    • right is inline-end

It gets more nuanced than that, but that is enough for this article.

Why are Logical Properties better?

The shorthand is cleaner. That's really it. When I'm talking about spacing in a component, and keeping it consistent across components, I'm generally talking about the padding or margin that is just inside the boundary of the component. And generally, I'm most concerned with the left and right as one set of values being the same.

padding-right: 10px;
padding-left: 10px;
/* vs */
padding-inline: 10px;

Same for the block direction:

padding-top: 10px;
padding-bottom: 10px;
/* vs */
padding-block: 10px;

Sure, that's one less line of code - but it's one less invitation for inconsistency to creep in.

Overrides are also much cleaner:

.card {
  padding: 10px;
}

@media (min-width: 800px) {
  .card {
    padding-left: 20px;
    padding-right: 20px;
  }
}

/* becomes */

@media (min-width: 800px) {
  .card {
    padding-inline: 20px;
  }
}

Creating your Custom Properties

Across large projects components tend to have one set of values for their left and right visual margins. It is very important to keep these values consistent so that components feel unified as the user scrolls down the UI. Vertical margins, on the other hand, can be much more varied. They can intentionally have wildly different margins as a way to form visual emphasis.

Here is what I have found works really well - creating spacing custom properties. And, having one for the inline direction, and one for the block direction.

:root {
  --spacing-inline: 2rem;
  --spacing-block: 4rem;
}

These can then be used for either margin, padding, or inset values as needed.

.card {
  padding-inline: var(--spacing-inline);
  margin-block: var(--spacing-block);
}

Why is this better?

It's much, much easier to wrangle this in a responsive design. You can augment your custom properties like so:

:root {
  --spacing-inline: 2rem;
  --spacing-block: 4rem;
}

@media (min-width: 800px) {
  :root {
    --spacing-inline: 4rem;
    --spacing-block: 8rem;
  }
}

You don't need to maintain breakpoints in your component. And your spacing across components will be much easier to keep consistent.

I can say from personal experience that this change alone has allowed me to remove a lot of code from a lot of components, and given me the confidence that my components will be consistent moving forward.

Bringing it all together

To demonstrate how this all can work together:

:root {
  --spacing-inline: 2rem;
  --spacing-block: 4rem;
}

@media (min-width: 800px) {
  :root {
    --spacing-inline: 4rem;
    --spacing-block: 6rem;
  }
}

@media (min-width: 1200px) {
  :root {
    --spacing-inline: 5rem;
  }
}

.card {
  padding-inline: var(--spacing-inline);
  padding-block: var(--spacing-block);
}

.card--spaced {
  padding-inline: var(--spacing-inline);
  padding-block: var(--spacing-blocked);
  margin-block: var(--spacing-blocked);
}

.card--big {
  padding-inline: calc(var(--spacing-inline) * 2);
  padding-block: calc(var(--spacing-block) * 2);
}

I hope this gives you some ideas on how you can use CSS Custom Properties as well as Logical Properties to make your components more consistent.