Starting macOS 15/iOS 18 TextKit 2 extra line frame is more broken (height always been broken) than previously. The same code return different values when run on macOS 14/iOS 17 and macOS 15/iOS 18.
The problem is that extra line fragment (NSTextLineFragment) origin and size is incorrect. I sketch the problem with the code snippet below:
// Storage
let textContentManager = NSTextContentStorage()
// Layout
| [alias] | |
| # need llm CLI: https://llm.datasette.io/en/stable/ | |
| # based on https://gist.github.com/karpathy/1dd0294ef9567971c1e4348a90d69285?permalink_comment_id=5167582#gistcomment-5167582 | |
| commit-ai = "!f() { if [ -n \"$(git diff --cached)\" ]; then git commit -m \"$(git diff --cached | llm -m '4o-mini' 'Below is a diff of all staged changes, coming from the command:\\n```\\ngit diff --cached\\n```\\nPlease generate a concise, two-sentence, maximum 100 characteres commit message for these changes. Do not mention project name.')\"; else echo 'No changes to commit'; fi }; f" |
https://mastodon.social/@krzyzanowskim/113007925115490633
UITextView convenience initializer does not call designated initializer since iOS 16.
The UITextView.init(usingTextLayoutManager:) that is a "convenience" initializer for the UITextView, does not call UITextView.init(frame:textContainer:) that is a designated initializer.
This behavior, when the class interface traslated to Swift interface, breaks the Swift rules of object initialization. I believe that is also incorrect in Objective-C, although the compiler doesn't check that.
code snippet to reproduce:
final class CustomTextView: UITextView {
the sample code published by Apple https://developer.apple.com/documentation/uikit/textkit/enriching_your_text_in_text_views show how List indicators does not render at all on macOS. This is regression as it used to work on macOS 13.
see attached video pf the EnrichingYourTextInTextViews Sample Code
| extension StringProtocol { | |
| /// str[NSRange(location:0, length: 9)] | |
| subscript(_ range: NSRange) -> SubSequence { | |
| guard let stringRange = Range<String.Index>(range, in: self) else { | |
| fatalError("String index is out of range") | |
| } | |
| return self[stringRange] | |
| } | |
expected:
| import Cocoa | |
| let loremIpsum = """ | |
| Lorem ipsum dolor sit amet, consectetur adipiscing elit. Pellentesque erat risus, laoreet et eros id, lobortis elementum sem. Nullam nec magna massa. Donec gravida felis at odio tincidunt pretium et in orci. Curabitur suscipit porta purus non faucibus. Cras dapibus felis eu enim rutrum, vel aliquet lacus volutpat. Quisque fermentum vulputate dictum. Morbi mattis orci quis dui posuere, id vulputate turpis tempus. Sed vulputate augue at ullamcorper feugiat. Phasellus nec lacus eget sapien congue lacinia vel et nulla. Phasellus sollicitudin gravida dapibus. Donec molestie ullamcorper lacus eu rutrum. Praesent lacinia dignissim dui eu ultricies. Integer in lacus lobortis, porttitor sem eu, tincidunt dolor. Cras dignissim nisl in maximus ullamcorper. | |
| Proin nec vulputate magna. In interdum leo sit amet arcu consequat facilisis. Fusce ut malesuada ante, nec malesuada nisl. Mauris porta velit quis tortor mollis, in suscipit augue efficitur. Praesent eleifend mollis neque, non sempe |
| extension StringProtocol { | |
| subscript(_ offset: Int) -> String.Element { | |
| if offset >= 0 { | |
| self[index(startIndex, offsetBy: offset)] | |
| } else { | |
| self[index(endIndex, offsetBy: offset)] | |
| } | |
| } | |
| import Cocoa | |
| /// "given this many pixels and a string with these attributes, tell me the optimal places to do a line break" | |
| class LineBreakPropose: NSObject, NSTextLayoutManagerDelegate { | |
| var lineBreaks: [NSTextLocation] = [] | |
| init(_ attributedString: NSAttributedString, in size: CGSize, by lineBreakMode: NSLineBreakMode = .byWordWrapping) { | |
| super.init() | |
I noticed that NSTextLayoutManager.usageBoundsForTextContainer is no longer KVO observable, despite being documented as KVO-compliant.. I believe it worked around macOS 13.
var usageBoundsForTextContainerObserver: NSKeyValueObservation?
usageBoundsForTextContainerObserver = textLayoutManager.observe(\.usageBoundsForTextContainer, options: [.new]) { textLayoutManager, change in
print("never called")
}