Conditional max height on Text causes `evaluate_property outside of an autorun or watcher`

Bugs
1

I’ve had these bugs for a while and the klankers finally found the root cause. I would submit a bug report, but god only knows how to submit a bug report these days.

So we created a demo page: https://nocode-to-knowcode.bubbleapps.io/version-test/conditional-text-height

To reproduce:

  1. Open the demo and your browser console.
  2. Turn off Preserve log, clear the console, and reload.
  3. Four errors appear—one for each affected Text element:
Calling evaluate_property outside of an autorun or watcher
    at evaluate_property (.../run.js)
    at max_height_css (.../run.js)
    at compute_clamp_lines (.../run.js)

The failing configuration uses a Text element that:

  • Fits its height to its content.
  • Has a maximum height of 42px.
  • Has a condition that removes the maximum height when an Expanded custom state is yes.

The error occurs on page load, before the expansion button is clicked. It occurs with both short and truncated text.

The working example displays the same content using two mutually exclusive Text elements:

  • A collapsed Text with a constant 42px maximum height.
  • An expanded Text with no maximum height.

Only their visibility changes. Neither Text has a conditional maximum height.

On repeated tests, the comparison page produced four errors, while the working-only URL produced zero fresh errors. No custom JavaScript generates or suppresses the errors.

This appears to be a Bubble runtime bug because it is reproducible with native elements and the entire stack is inside Bubble’s delivered run.js. My interpretation is that compute_clamp_lines reads the conditional max_height_css property outside the expected reactive context, but that has not been confirmed by Bubble.

2

your UI has been looking extra good recently Rico!

3

haha.. when you come from 0, anything is fantastic.

I appreciate that, thanks!

4

And thanks for the knowcode shoutout :rofl: