cancel
Showing results for 
Search instead for 
Did you mean: 
Reply
Highlighted
Frequent Visitor

Auto Height of canvas changed behaviour

I have a scrollable window on a canvas app.

I`ve created a set of cards that expands or collapses like a tree control.

Old Behaviour: I could set a card height small enough just to view those objects with visible=true at the top of the card.  Other objects with visible=false were not considered into container's height validation.

New Behaviour: every object on the container, visible or not, is accountable for container height validation. To collapse the container card I must:

  • Set every invisible object height to 0
  • Set every invisible object y to 0

... and remember their original locations

 

Is this going to be the new standard behaviour? or it depends on any new configuration?

Thanks in advance

2 REPLIES 2
Highlighted
Community Support
Community Support

Hi @Bubbler ,

Could you please share a bit more about your scenario?

Do you mean that these invisible objects within the Container would be considered container's height validation?

 

Based on the issue that you mentioned, I have made a test on my side, and don't have the issue that you mentioned. These invisible objects within the Canvas Container would not be considered into Container's height.

4.JPG

 

Please consider take a try to re-create a new canvas app, then add a Scollable screen within it ("Insert" -> "New Screen"-> "Scrollable screen"), then check if the issue is solved.

 

If I do not understand your issue correctly, please share a screenshot about your issue, then we could reproduce it on my side, and provide a proper workaround for you.

 

Best regards,

Community Support Team _ Kris Dai
If this post helps, then please consider Accept it as the solution to help the other members find it more quickly.
Highlighted

Hi @v-xida-msft 

 

You got it perfectly.

I've rebuilt it from scratch as you suggested and.... It worked!!

 

So I compared each implementation to try to understand the differences.

Finally I discovered the issue/bug.  It only happens when the invisible objects are grouped together.

 

Try to group a pair of objects that change their visibility dinamically, It happens even if all the grouped objects are invisible at the same time.

 

Could you reproduce it?

It is a new behaviour

Helpful resources

Announcements
Community Conference

Power Platform Community Conference

Check out the on demand sessions that are available now!

News & Announcements

Community Blog

Stay up tp date on the latest blogs and activities in the community News & Announcements.

secondImage

Power Platform 2020 release wave 2 plan

Features releasing from October 2020 through March 2021

Community Highlights

Community Highlights

Check out the Power Platform Community Highlights

Top Solution Authors
Top Kudoed Authors
Users online (13,518)