[iOS] Fix for Editor scaling creating new lines on older iOS versions

[Tamilarasan-Paranthaman]

Root Cause of the issue

• The layout of the Editor behaves differently on iOS 17.5 and earlier versions when the scale changes at runtime. Specifically, the content height gradually increases when scaling down the Editor, suggesting improper handling of height.

Description of Change

• It seems that iOS 18.0 handles this behavior correctly. To ensure consistent behavior similar to iOS 18.0, I wrapped the Editor in a container for iOS 17.5 and earlier versions. This container ensures that the layout remains stable and visually consistent, even when the Editor is scaled or resized. Since the issue is resolved in iOS 18.0 and later, the additional container is not needed for those versions.

Issues Fixed

Fixes #25581

Tested the behaviour in the following platforms

• Android
• Windows
• iOS
• Mac

Screenshot

Before Issue Fix	After Issue Fix
Issue.mov	Fix.mov

[dotnet-policy-service]

Hey there @Tamilarasan-Paranthaman! Thank you so much for your PR! Someone from the team will get assigned to your PR shortly and we'll get it reviewed.

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jsuarezruiz]

/rebase

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[PureWeen]

Test failing on winui

[Tamilarasan-Paranthaman]

Test failing on winui

@PureWeen, I have added the snapshot for WinUI.

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[jsuarezruiz]

The device tests:

ScrollEditor
Assert.True() Failure\nExpected: True\nActual:   False

and

ScrollNextEditor
Assert.True() Failure\nExpected: True\nActual:   False

are failing after the changes.

[Tamilarasan-Paranthaman]

The device tests:

ScrollEditor
Assert.True() Failure\nExpected: True\nActual:   False

and

ScrollNextEditor
Assert.True() Failure\nExpected: True\nActual:   False

are failing after the changes.

@jsuarezruiz, I have fixed this by restricting the Mac platform in the fix, as the issue occurred on the iOS platform. The cases have passed locally. Could you please check and let me know if you have any concerns?

[jsuarezruiz]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[tj-devel709]

@Tamilarasan-Paranthaman did you see this issue in iOS 17? I have only noticed it in 15.5 and 16.4 but maybe there is a scenario it happens in 17 also?

[Tamilarasan-Paranthaman]

@Tamilarasan-Paranthaman did you see this issue in iOS 17? I have only noticed it in 15.5 and 16.4 but maybe there is a scenario it happens in 17 also?

@tj-devel709, I encountered this issue in iOS 17+ as well. Interestingly, I am currently unable to reproduce it in iOS 17+ (specifically tested on version 17.5). This is quite unusual, as the issue report also confirms it was verified in version 17.5. Could you please share your thoughts on this and suggest how we should proceed?

[PureWeen]

@Tamilarasan-Paranthaman let's just go with what you're seeing

Can you just set the operating system version check to whatever version you find that we need this for?

[Tamilarasan-Paranthaman]

@Tamilarasan-Paranthaman let's just go with what you're seeing

Can you just set the operating system version check to whatever version you find that we need this for?

@PureWeen, I have updated the version, and it will now apply only to versions below 17. Could you please check it now and let me know if you have any further concerns?

[PureWeen]

/azp run

[azure-pipelines]

Azure Pipelines successfully started running 3 pipeline(s).

[tj-devel709]

Confirmed with these new changes that it works with the following I versions!

18.1
18.0
17.5
17.2
17.01
16.4
15.5

issues addressed