Entry tab "stretching" bug. #15783
Labels
area-layout
StackLayout, GridLayout, ContentView, AbsoluteLayout, FlexLayout, ContentPresenter
layout-grid
partner/syncfusion
Issues / PR's with Syncfusion collaboration
platform/android
platform/windows
s/triaged
Issue has been reviewed
s/try-latest-version
Please try to reproduce the potential issue on the latest public version
t/bug
Something isn't working
Uh oh!
There was an error while loading. Please reload this page.
Description
I described the issue in full detail in the following .NET q/a page with images and everything;
https://learn.microsoft.com/en-us/answers/questions/1315087/problem-with-the-entry-bar-after-adding-a-(collect?page=1#answer-1274789
After adding the <CollectionView.ItemTemplate> into the code, the entry tab and button sizes change unexpetedly.
The Entry tab "stretches out" when writing a long string inside. Shrinking the button next to it, even smaller than the preset size.
Steps to Reproduce
6)The Entry tab & button sizes above the "< CollectionView >", on the first row will be modified.
7)When writing a long string on the Entry tab, this one "stretches" to a certain point. Getting bigger, while the button gets smaller.
Link to public reproduction project repository
https://github.com/Rickter-Darkaster/MAUI-CollectionView.ItemTemplate-ColumnSpan-bug
Version with bug
7.0.86
Last version that worked well
6.0
Affected platforms
Android, Windows, I was not able test on other platforms
Affected platform versions
Windows Machine 10.0.190410 and Android 13.0
Did you find any workaround?
-When you remove the grid properties "Padding" or "Margin" and all the elements inside the grid of the <CollectionView.ItemTemplate>. The bug goes away (Not very useful though, cause you won't see anything being displayed).
-When you remove the Grid.ColumnSpan="2" from the whole "< CollectionView >", the bug disappears entirely. But the grid given will only span the first column..... So there's a downside but it is a temporary fix.
Relevant log output
No response
The text was updated successfully, but these errors were encountered: