如何消除TableView自定义Cell与内容视图间的左侧间距？

Hey there! That hacky -15 constraint might work temporarily, but you’re right—it’s not the proper solution. Let’s break down the real fixes to eliminate that annoying spacing for good.

First, Check Your Custom Cell’s Internal Layout #

A lot of the time, this spacing comes from misaligned constraints inside your cell itself. Make sure:

• All your subviews (labels, images, stacks, etc.) are constrained directly to the contentView of the cell, not the cell’s main view. The contentView is the system-managed container for your cell’s content, and ignoring it can lead to unexpected padding.
• Your subviews have leading, trailing, top, and bottom constraints set to 0 relative to the contentView (unless you intentionally want padding there). No extra margins should be added here by accident.

Adjust Cell and TableView Settings #

Here are the key code changes you need to add to your existing setup:

1. Set contentView margins in your custom cell
   Add this to your cell’s awakeFromNib() (if using XIB/Storyboard) or initializer (if using code):

   override func awakeFromNib() {
       super.awakeFromNib()
       // Reset any default margins on the contentView
       contentView.layoutMargins = .zero
   }
   

2. Disable readable width margins for the table view
   iOS defaults to making cell content follow the "readable width" (which adds side margins on larger screens). Turn this off in your view controller’s viewDidLoad():

   override func viewDidLoad() {
       super.viewDidLoad()
       // Your existing settings
       table.separatorStyle = .none
       table.separatorInset = .zero
       table.contentInset = .zero
       // Add this line
       table.cellLayoutMarginsFollowReadableWidth = false
   }
   

3. Ensure cell-level margins are zero
   If you’re using a UITableViewCell subclass, you can also explicitly set the cell’s layout margins to zero (though the contentView setting is more critical):

   override func layoutSubviews() {
       super.layoutSubviews()
       layoutMargins = .zero
   }
   

Why the -15 Constraint Is a Bad Idea #

That hack works because it offsets the entire table view against the safe area, but it’s fragile:

• It hardcodes a value that might not match safe area insets on all devices (e.g., iPads, future iPhone models).
• It breaks Auto Layout’s intended behavior, leading to unexpected layout shifts if your app’s safe area or screen size changes.
• It doesn’t fix the root cause of the spacing, which is usually misconfigured margins or constraints.

By following the steps above, you’ll address the spacing at its source and keep your layout clean and future-proof.

内容的提问来源于stack exchange，提问作者Nikita Rysin