Using UINavigationBar standalone causes weird top attaching layout

Question

Created Feb ’22

Replies 2

Boosts 0

Participants 2

Against using UINavigationController + UINavigationBar. This question is about what if we use UINavigationBar as standalone in a ViewController.

To lay UINavigationBar out as well as it is the case of UINavigationController management, I'm doing like this,

Add UINavigationBar to the view of ViewController
Add constraints to lay it out on top of the safe area.

navigationBar.bottom == safeAreaLayoutGuide.top navigationBar.left == view.left navigationBar.right == view.right

Set the delegate of UINavigationBar, then return topAttached for the bar position.
Set additionalSafeAreaInsets to propagate the insets to the subviews.

It looks works well but got weird laying out inside UINavigationBar from seeing view debugger.

The extending view to cover to the top of the screen by setting `topAttached is too much growing.

What am I missing? I'd like to know how to use UINavigationBar in the correct way that includes safe-area management.

CleanShot 2022-02-26 at 20.24.16@2x.png

Boost

Answer 1

anils OP

Feb ’22

Screen Shot 2022-02-27 at 9.35.38 AM.png

class ViewController: UIViewController {
    @IBOutlet weak var navigationBar: UINavigationBar!
    override func viewDidLoad() {
        super.viewDidLoad()
        // Do any additional setup after loading the view.
        navigationBar.delegate = self
    }
}

extension ViewController: UINavigationBarDelegate {
    func position(for bar: UIBarPositioning) -> UIBarPosition {
        return .topAttached
    }
}

Screen Shot 2022-02-27 at 9.38.03 AM.png

0

Answer 2

muukii0803 OP

Feb ’22

Additional notes for my question, I'm working on this like

- ViewController
  - View
    - UINavigationBar
    - UICollectionView (laying out to fullscreen, content-inset managed by safe-area)

0