The Syncfusion native Blazor components library offers 70+ UI and Data Viz web controls that are responsive and lightweight for building modern web apps.
.NET PDF framework is a high-performance and comprehensive library used to create, read, merge, split, secure, edit, view, and review PDF files in C#/VB.NET.
When setting height to wrap_content and run this Application on a Device like a Samsung Galaxy S7 the height of the sfautocomplete ist about 3x the height it should be.
MKMuneesh Kumar G Syncfusion Team April 9, 2019 08:11 AM
Hi Alex,
Greetings from Syncfusion, we have checked the reported issue "wrap_content height not working as expected" from our side and we have modified the provided sample and give the height of the AutoComplete control as 15db to solve this problem as per the below code snippet.
Please check and let us know if you have any concern on this.
Thanks,
Muneesh Kumar G.
ALAlexApril 9, 2019 08:17 AM
This is only a workaround. Not a solution. Because if i set 15dp to the EditText Controls they are much to small but i want them to be the same Size with same dp values.
MKMuneesh Kumar G Syncfusion Team April 11, 2019 07:40 AM
Hi Alex,
We have logged issue report with "SfAutoComplete and Editext height are different when we set control height as WrapContent in AXML". Please find the feedback link for this issue from below.
The fix for the reported issue will be available on April 16, 2019.
If you have any more specification/precise replication procedure or a scenario to be tested, you can add it as a comment in the portal.
Regards,
Muneesh Kumar G.
MKMuneesh Kumar G Syncfusion Team April 16, 2019 04:35 AM
Hi Alex,
Thanks for your patience,
We have fixed the reported issue "SfAutoComplete and EditText heights are different when we set the same DP value for both controls in AXML" and attached the patch file for your reference. Please find it from the below link.
Advanced approach – use only if you have specific needs and can directly replace existing assemblies for your build environment
Disclaimer: Please note that we have created this patch for version 17.1.0.38 specifically to resolve the following issue reported in this incident. If you have received other patches for the same version for other products, please apply all patches in the order received.
This fix will be included in our upcoming Volume 1 SP1 release which will be available in the mid of May 2019.