Abhinav Jha

@ankurrsinghal I've added a different mechanism to enable this. Please see #17686 . Closing this PR.

The rationale behind having min and max here, is that the values beyond the bounds would break the application or have the widget work incorrectly. This is why the fallback...

@Nikhil-Nandagopal - We can extend height to a limit, after which the developer needs to decide whether the content is clipped (today's default), or content is scrolled. This is why...

> I think my point is scroll will only come if there is a max height set otherwise it won't Agreed! > This makes it easier to configure than guessing...

@Nikhil-Nandagopal Sounds good. I can relate to the inaccuracy in anticipating how a feature effects things at runtime. 😅 @momcilo-appsmith Any suggestions on a good UX here?

# Update - Why are we not using dynamic width? - Appsmith doesn't have a concept of infinitely wide canvas. There is always a fixed maximum number of columns a...

@Nikhil-Nandagopal Absolutely. I'll make sure to add this to the task list for the project.

@dilippitchika This is a great point! I believe, if we can confirm that the dynamic height will come into play only if the word-wrap is enabled, then we can make...

# Dynamic height investigation results ## Approach - We assumed using [`ref`](https://reactjs.org/docs/refs-and-the-dom.html) to be the most straightforward approach to enable dynamic height in widgets. - This works by attaching refs...

## Update - Conclusion: Disable vertical resize of the widget when dynamic height is enabled - Parallel design exploration: Signifiers of max-height and min-height. @vinay-appsmith @momcilo-appsmith - Conclusion: Persist heights...