Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Binding drawer (lightning bolt button) is not opening and screen become uninteractive #15723

Open
Elestara opened this issue Mar 12, 2025 · 2 comments
Labels
avalanche OSS team bb-bindings bb-components bug Something isn't working env - production Bug found in production

Comments

@Elestara
Copy link

Checklist

  • [x ] I have searched budibase discussions and github issues to check if my issue already exists

Hosting

  • Self
    • Method: docker compose
    • Budibase Version: 3.5.0.
    • App Version: 3.5.0.

Describe the bug
Binding drawer (lightning bolt button) is not opening and screen become uninteractive after click. It happens only in one particular screen with a lot of components (and approx 10 data providers), others screens with less components are ok. Restart page/browser/container is not helping, updating docker and budibase too. I can only click to lightning and bug again.
Is this components/data provider amount limitation?

To Reproduce

  1. Make a page with a lot of components (modals, data providers, etc)
  2. One day somehow see error

Expected behavior
To work properly

Screenshots
When attempting to open drawer, browser console shows this:
index-d8ae4c4f.js:885 Uncaught (in promise) InvalidCharacterError: Failed to execute 'add' on 'DOMTokenList': The token provided ('[object Object]') contains HTML space characters, which are not valid in tokens. at buildSectionHeader (index-d8ae4c4f.js:885:142) at index-d8ae4c4f.js:885:3674 at Array.reduce (<anonymous>) at bindingsToCompletions (index-d8ae4c4f.js:885:3620) at to.$$.update (index-d8ae4c4f.js:890:26320) at init$3 (index-d8ae4c4f.js:4:11594) at new BindingPanel (index-d8ae4c4f.js:890:26805) at create_fragment$8P (index-d8ae4c4f.js:890:27080) at init$3 (index-d8ae4c4f.js:4:11650) at new ClientBindingPanel (index-d8ae4c4f.js:890:28734)

with

Incorrect use of <label for=FORM_ELEMENT>
The label's for attribute doesn't match any element id. This might prevent the browser from correctly autofilling the form and accessibility tools from working correctly.

To fix this issue, make sure the label's for attribute references the correct id of a form field

in error field, referencing to every element in component settings where lightning was clicked.
Tried in Chrome, same error.

App Export

mainworkspace_export-export-1741779560069.tar.gz

Desktop:

  • OS: Windows 10.0.19045.5487
  • Browser: Opera
  • Version: 117.0.5408.53
@Elestara Elestara added the bug Something isn't working label Mar 12, 2025
@Elestara
Copy link
Author

Elestara commented Mar 18, 2025

Found it: It was option picker in one of the modals. Delete, recreate it and problem gone. Still not sure how it made whole screen to freeze.

Found more: There are option picker that I used more like a visual clue and it has one default custom option (and then disabled). I add one more option (but still has a default) and it works. I think if you has only one option it makes a bug.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
avalanche OSS team bb-bindings bb-components bug Something isn't working env - production Bug found in production
Projects
None yet
Development

No branches or pull requests

2 participants