Getting a heap of these on certain pages, notably one page with a repeat filled with API data. There are some formatters in the repeat, but not many and nothing complex:
What is most concerning, is that if I leave the page open and fully loaded - these violations keep going up, constantly. I’ve looked through the various posts on the forum relating to this, and I note that the violation is pointing towards: dmxAppConnect.js:7
Other than this, I am not sure how to debug/fix - if it’s pointing to a core Wappler file? I’d appreciate any suggestions to help me look into this further.
UPDATE:
I moved this to bugs, as this is happening on a page that was working great, I had not made any amendments to it over the last week - so can only assume something has changed with Wappler 3.6.0.
I’ve just spent the last couple of hours removing formatting/conditions (that previously worked well) just to try to find the source of the issue, but no luck.
Whatever is causing this flooding is rendering this page unusable, as many features (primarily that rely on adding/removing from arrays) just won’t work…
Hi @mgaussie,
Not shure it will help you but i get exactly this kind of message recently.
Indeed it is the first time I have seen this kind of message.
But when i noticed it i was playing with some javascript functions inside my page code.
This disappeared when I was done with my javascript bugs.
Update : after a few tests, i had been able to reproduce the issue.
This error is launched when i click on a particular button.this button is firing a static event (with a javascript function) and a submit action.
My javascript function aimed to format a string with servral field inputs and return the result in a hidden field, and the submit action sends the hiiden field content to the database.
The first question I asked myself before doing this was, which of the static event or the dynamic event was launched first. However the solution works, however there is the famous [violation] message…
Another update :
My error message is thown by polyfills.js
Well as your page becomes more complex, with a lot of expressions, it will get slower.
So it is very important that you use conditional regions - to hide whole inactive areas that doesn’t need to be evaluated all the time.
Note I mean really conditional regions - now just show/hide - those are done with css and still get evaluated.
