Pardon me, but I think you might be misunderstanding my problem @Peter_Schorn. The issue is not about what happens when the text escapes the visible bounds, but how UITextField interprets its "text" property. For example, if a user types in three consecutive periods "...", the value that is read from UITextField::text is a Unicode elipsis rather than three period characters. I would prefer instead that the periods remain.

Seems to have done the trick (with the elipsis at least) :). Thanks!

I will note that it does not seem like the documentation for smartDashesType is complete. It does not reference conversion between periods and elipsis, and makes me wonder if there is other hidden behavior.

Understood. Filed with Feedback Assistant :)

I have just noticed that the directional layout margins are being reset from my custom specified to (top: 0.0, leading: 20.0, bottom: 0.0, trailing: 20.0) sometime after my view controller is loaded. Do you happen to know what could be causing this behavior? This seems to occur sometime inbetween calls to viewWillAppear(:animated) and viewDidAppear(:aniamted)

The "Internal" views (Internal1 and Internal2) are IB-based (not created in code) and owned by the External view.

Yes. I observed the same behavior.

Scratch that. The issue is that my procedure to retrieve the dynamic title is a bit more complex than I let on and relies on an combine publisher that is recieved on DispatchQueue.main. I made an incorrect assumption that an event would fire off immediately once a subscription was made, which is where I got the idea that I had tried viewDidLoad(:). Thankfully this is an easy fix :)

"Constrain to what? Are you saying that you want to set the height of the inner table view so that it doesn't need to scroll its contents, so that scrolling gestures always scroll the outer scroll view? Is the number of rows in the inner table view fixed, or does it change over time?" This is exactly what I mean. The contents of the inner table view do change, but at discrete moments of time (e.g. at the press of a button), so I'm not sure if this is much of a concern?

"No, it doesn't get an accurate height in advance" Thanks for clearing up this misunderstanding and explaining the implementation a bit more in depth. I will go ahead and mark this as a solution and look at other potential implementations :)