InvalidateMeasure in child triggers parent measure

[karthikraja-arumugam]

Description

In our custom control, we have a nested layout, in which if we call InvalidateMeasure for child element it triggers parent measure. This causes a loop in our implementation.

Sometimes InvalidateMeasure doesn't trigger the calling layout's measure itself.

Steps to Reproduce

TestSample.zip

1. Run the attached sample. It has the below implementation
   Custom Control => Layout => Grid => ScrollView => DrawableView

2. Press the InvalidateSize button, it will invalidate the layout measure and it triggers custom control (parent layout) measure.

Version with bug

Preview 11

Last version that worked well

Unknown/Other

Affected platforms

iOS, Android, Windows, macOS

Affected platform versions

Android 9.0, Windows SDK 10.0.19041

Did you find any workaround?

No

Relevant log output

No response

[wenwen60]

Reproduce on VS2022 17.2.0 Preview 2.0 [32215.517.main] using Android 11, attach repro sample
TestSample.zip.

[hartez]

if we call InvalidateMeasure for child element it triggers parent measure

It is true that calling InvalidateMeasure() on a control may trigger the Measure of the parent control. That is expected behavior.

This causes a loop in our implementation.

I am not seeing a loop in the repro project you provided. Clicking the button calls the child's InvalidateMeasure(); the parent and child controls' Measure() methods are called, the controls are arranged, and the cycle ends.

Could you tell us why you are trying to call InvalidateMeasure() on a child control?

[ghost]

Hi @karthikraja-arumugam. We have added the "s/needs-info" label to this issue, which indicates that we have an open question for you before we can take further action. This issue will be closed automatically in 7 days if we do not hear back from you by then - please feel free to re-open it if you come back to this issue after that time.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.

[ghost]

This issue has been automatically marked as stale because it has been marked as requiring author feedback but has not had any activity for 4 days. It will be closed if no further activity occurs within 3 days of this comment. If it is closed, feel free to comment when you are able to provide the additional information and we will re-investigate.