I am using Xamarin.Forms with 18.104.22.168 and have an SfTextInputLayout containing an Editor. These controls are within a Grid row that is set to "auto" height. I have the Editor set to AutoSize when the text changes.
When someone types a long message, the text will wrap to the next line and the Editor's height increasing. When they erase text, the height changes as well. This all works well.
The problem comes with other code sets the Editor's text value to a long string. Lets say I said: txtMsg.Text = "Hello this is a long message that will wrap to another line and make the editor height grow."
Then I tap the Editor and try to erase some of the text area. It is as if the Editor itself shrinks in height, but the SfTextInputLayout does not. This results in the SfTextinputLayout's borders and whatnot cascading off the screen and the "Hint" becomes displaced. I have attached a couple screenshots of this.
RARachel A Syncfusion Team November 21, 2019 07:55 AM
We were able to reproduce the issue at our end. We have confirmed this as an issue and logged bug report. We will include the fix in our Volume 4 release which will be available by the mid-December 2019. You can track the bug status from the below link.
We are not able to provide workaround for this issue. We will provide patch for this issue on or before November 29th, 2019. We appreciate your patience until then.
Hey, sorry for being impatient, but I noticed there was a weekly release today (11/26) and the bug was not patched in this release.
You mentioned a fix would be implemented on or before 11/29, does this mean a second release is going to happen this week?
LRLakshmi Radha Krishnan Syncfusion Team November 27, 2019 08:13 AM
We have mentioned to provide patch for this issue and we have not included the fix in our last weekly release (22.214.171.124). As promised earlier, we will provide patch for this issue on November 29, 2019.
LRLakshmi Radha Krishnan Syncfusion Team November 29, 2019 10:04 AM
Please note that we have created this patch for
version 126.96.36.199 specifically to
resolve the issue in this incident. If you have received other patches for the same version for other products, please apply all patches
in the order received.
Could you please crosscheck at your end by clearing the
NuGet cache as mentioned in this link? and refer the provided NuGet and
confirm us whether you can resolve this issue. We will include this fix in our
Volume 4 beta release which is scheduled to be rolled out in the first week of