Issue with picker when selecting data bindings

Hyperbytes · October 8, 2025, 1:57pm

Wappler Version : 7.3.6
Operating System : Win 11
Server Model: node
Database Type: mysql
Hosting Type: local

Expected behavior

This can happen in a number of places but this in this example it happens when picking a data binding for a Bootstrap table.

When selecting binding, on many occasions it can not be selected

What actually happens?

Should be selected on click
See video

Log (errors visible in this log)
wappler.zip (5.7 KB)

franse · October 8, 2025, 3:27pm

Maybe same as this?:

Hyperbytes · October 8, 2025, 4:23pm

Yes, thats the same issue.
Pain in the A**

Priya_Sharma · October 8, 2025, 4:28pm

Pain in the eyes

sitestreet · October 8, 2025, 4:41pm

Happens to me, too. I thought I was imagining it at first. Good to see it’s not just me. Thanks for putting the video together so it can hopefully be fixed.

Hyperbytes · October 8, 2025, 4:48pm

bug report shows exactly what is happening, multiple occurrences of this:

2025-10-08 14:48:02.118] IndexSizeError: Failed to execute 'getRangeAt' on 'Selection': 0 is not a valid index.
    at file:///C:/Users/brian/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/jQuery/tagify.js:34:57089
    at Array.forEach (<anonymous>)
    at Y.setRangeAtStartEnd (file:///C:/Users/brian/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/jQuery/tagify.js:34:57059)
    at Y.injectAtCaret (file:///C:/Users/brian/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/jQuery/tagify.js:34:60677)
    at Y.appendMixTags (file:///C:/Users/brian/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/jQuery/tagify.js:34:70548)
    at Y.addMixTags (file:///C:/Users/brian/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/jQuery/tagify.js:34:70457)
    at HTMLDivElement.<anonymous> (file:///C:/Users/brian/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/dmxAppConnect/pickup.htm?theme=dark&app=true&noinit=true:886:30)
    at file:///C:/Users/brian/AppData/Local/Wappler/resources/app/Shared/DMXzone/dmxAppCreator/UI/jQuery/js_lib.js:658:12
    at sentryWrapped (C:\Users\brian\AppData\Local\Wappler\resources\app\node_modules\@sentry\browser\build\npm\cjs\helpers.js:95:17)

ben · October 8, 2025, 10:23pm

I decided to ask Copilot for assistance, and this was the response:

Ben, if this is the beginning of a cosmic glitch in the multiverse or just a looping denial from a Wappler bug report, I’m here for it. Want me to help you script a surreal skit about it? Maybe a quantum tribunal where every version of you insists, “It wasn’t me,” while the logs say otherwise?

So much for AD (artificial dumbness).

patrick · October 9, 2025, 11:22am

It is a bug is in tagify, we trying to find a solution for it. If we or the author finds a fix we will update it immediately within Wappler.

github.com/yairEO/tagify

Adding tags in mix mode causes infinite loop

opened 08:56AM - 07 Aug 25 UTC

dmx-patrick

## Prerequisites - [x] I am running the latest version - [x] I checked the docu…mentation and found no answer - [x] I checked to make sure that this issue has not already been filed ### 💥 Demo Page https://jsbin.com/libuxiyomo/2/edit?html,js,console,output ### Explanation There are several problems with the use of document fragment in addMixTags method. I already did most of the debugging and know what exactly goes wrong but don't have a solution for it yet. The demo page does not show the infinite loop but only the first problem which finally causes the infinite loop. #### Cause of the problem After the fragment is inserted into the DOM the fragment becomes empty. The code still uses the fragment after it was inserted which causes several problems. #### First problem: selection not correctly set and warning in console With existing selection it calls the method `injectAtCaret` which insert the fragment in the DOM and after that it calls `setRangeAtStartEnd` with the document fragment as `node` argument. The fragment is at this moment empty causing an error which is inside a try/catch and shows the error `IndexSizeError: Failed to execute 'getRangeAt' on 'Selection': 0 is not a valid index.` in the console. The error is with the `setEnd`, the `setStart` didn't throw an error but due to the empty fragment being passed as parameter it caused the selection being unset causing the error in the second loop with `setEnd`. #### Second problem: invinite loop Due to the above error you now have an unset selection with no range, while the instance `state.selection` still holds a valid selection. I'm not sure when it happens but in our case the `state.selection` was updated with an invalid selection, the object became: ```js { anchorOffset: 0, anchorNode: null, range: 0 } ``` With this corrupted state we do get an infinite loop where the methods `injectAtCaret` and `appendMixTags` repeatedly calling each other causing a `Maximum call stack size exceeded` error. #### Screenshots of the errors <img width="591" height="103" alt="Image" src="https://github.com/user-attachments/assets/849c633d-9b43-4a72-9caf-d3decc72cf8b" /> <img width="448" height="447" alt="Image" src="https://github.com/user-attachments/assets/bb699a55-1d76-4ad9-a828-7238155f5112" />

Teodor · November 13, 2025, 5:05pm

Fixed in Wappler 7.4.2