XAMCORE_4_0 Audit List #5107
Labels
breaking-change
If an issue or a pull request represents a breaking change
enhancement
The issue or pull request is an enhancement
iOS
Issues affecting iOS
macOS
Issues affecting macOS
Milestone
In some future day we may have a chance to break API compatibility.
When that day comes we should fix up every single API mistake we can. This is a list of items we should audit.
Drop support for iOS 32-bit?We still support iOS 32-bit in .NET, and we will until our minimum OS version is 11+.NSAttributedString contains an existing ContainsAttachments property. 10,11 added a ContainsAttachmentsInRange method. Can't name the method ContainsAttachments because it conflicts with the property, but ContainsAttachmentsInRange (used for now) is an ugly name.Nothing can be done here.Double exported "worksWhenModal" selectorDon't know what this is talking about, can't find any problems with the "worksWhenModal" selector that looks like this.[XM] Add missing NSResponder APIs #929: All of the PresentError in AppKit need love.This can be done in a non-breaking way.[CoreImage] Strong-type a format parameter to CIContext.CreateCGImage in .NET. #13829already done some time ago[Sealed]
items, as some were added during work arounds for binding mistakes. ExampleLook at the types we use from System.Drawing and see if we can improve that scenario.This is done as part of .NET 6.xamarin-macios/src/ObjCRuntime/Blocks.cs
Line 239 in 5449257
CFNetwork
namespace, includingMessageHandler
, from Xamarin.Mac. [CFNetwork] Remove the MessageHandler type from .NET. #14056CFNetworkHandler
(minimum iOS 8) We can do this at a later stageonlyOn64
logic is still applicable (it's not for tvOS for instance, where the API will always be 64-bit, and it might be true for our iOS/macOS bindings too at that point). This has been done as part of the .NET migration.The text was updated successfully, but these errors were encountered: