WeWeb Editor & Form Behavior: Seeking Solutions & Best Practices

I’m running into a few issues while working with WeWeb and wanted to get some insights from the community. If anyone has solutions or best practices for these, I’d really appreciate the help!

1. Ctrl + Z Overwrites Everything

Using Ctrl + Z seemed to revert the editor to its initial state, undoing dozens of changes at once instead of just the last action. Has anyone found a way to make undo behave normally?

2. Form isValid Only Updates on Submit

The isValid property only updates when submitting the form. Is there a way to trigger validation on change, so we can do things like prevent submission until validation conditions are met?

  • Example: Ensuring a password meets complexity rules in real-time instead of just at submission.
  • I’m aware of workarounds using global variables, but that feels hacky and unsustainable if this is needed for multiple cases.

3. Accessing Current Object’s Properties in Formulas

Is there a simple way to access the current object’s property values in formulas?

  • I tried thisInstance, but many UI-editable properties aren’t available there.
  • Would love a way to do something like this.decoration or this.disabled, etc… inside formulas.

4. Accessing Other Elements’ States in Formulas

Is there a way to access another element’s state inside a formula?

  • Example: Having one element react to state changes in a different element without using global variables to track everything.

5. Font Size Definitions for Breakpoints

Right now, I have to create multiple Typography styles (H1 Desktop, H1 Tablet, H1 Mobile) to handle font sizes at different breakpoints.

  • I could really use a way to define font sizes for all breakpoints inside a single Typography style, rather than making separate styles for each…

6. Form Values: formdata vs fields.value – Performance Impact?

Form input values are accessible via both formdata and fields.value.

  • Is there a recommended WeWeb approach for accessing values?
  • Does performance differ based on which method is used?
  • I noticed that some of my debug log statements in an onChange workflow were one character behind the actual input – could this be related to which method is being used?

Any insights would be hugely helpful! Thanks in advance for your help. :blush: