You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Feb 2, 2023. It is now read-only.
Seems like there are some failing tests on Xcode 6 beta (iOS 8 beta).
testSpaceBoundingBoxForNoWordKerning and testSpaceBoundingBoxForWordKerning fail because of bounding box's width, which returns different results on Xcode 5/iOS 7.1 (value = 4.0) and Xcode 6/iOS 8 (value = 3.55200005...). I'm assuming kerning returns different widths because the system font was slightly tweaked in iOS 8. Not sure how to fix this for both versions while still testing expected behavior.
testAttributeCleansing fails because apparently the expected and actual cleansed strings don't match, but from all the visible properties they are the same strings. So it might be the way NSAttributedString uses its isEqualToAttributedString: in iOS 8.
Sorry for not being too helpful, just wanted to keep an eye on these because it might mean Apple introduces slight changes in behaviour in text rendering that actually provide different values.
Seems like there are some failing tests on Xcode 6 beta (iOS 8 beta).
testSpaceBoundingBoxForNoWordKerningandtestSpaceBoundingBoxForWordKerningfail because of bounding box's width, which returns different results on Xcode 5/iOS 7.1 (value = 4.0) and Xcode 6/iOS 8 (value = 3.55200005...). I'm assuming kerning returns different widths because the system font was slightly tweaked in iOS 8. Not sure how to fix this for both versions while still testing expected behavior.testAttributeCleansingfails because apparently the expected and actual cleansed strings don't match, but from all the visible properties they are the same strings. So it might be the wayNSAttributedStringuses itsisEqualToAttributedString:in iOS 8.Sorry for not being too helpful, just wanted to keep an eye on these because it might mean Apple introduces slight changes in behaviour in text rendering that actually provide different values.