That’s what I believe happened. It all started when a node style prop was getting set on form load. I had updated the code to be more robust and handle the situation better, but it was like the code didn’t fully update until I checked out an older version, then went back to the master. I have encountered this situation a few times in the past. Next time, checking out a later version will be a first step in my troubleshooting.
Thanks for your quick response. Have a great weekend!
I continue to run into this issue whenever there is an app load time issue with DOM node interaction. The trick to check out an older version doesn’t seem to be resolving the issue anymore either.
@chad63e do you have an app ID and reproduction steps we can follow to take a look at what’s going on?
Hey Stu,
Here is my app ID: ENEK2H3QNBR4SJPI
The issue seems to occur when an error arises while setting a DOM node property on a component during the form_load event.
Could you provide more detailed reproduction steps.
Etc.
Unfortunately, I don’t know if I give you exact steps, but can help give my best guess as what was happening. I was working on form: SelectionInputNew2 (Now SelectionInputNew, and soon to be SelectionInput and the old one will be SelectionInputOld) (before I finally just put the in_designer condition in the input_show method). Whenever it would call a function in the designer that used the get_dom_node and then tried to set a property of that node (maybe if it is a bad reference, or incorrectly written) the app would freeze up.
I know this might not be as helpful as you might need, but unfortunately, I wasn’t doing a great job at documenting the issue.
I understand that if the code is written well, this probably wouldn’t happen, but during development, it seems inevitable to occur (at least for me).
Ok - I tried a couple of times to reproduce the issue, but couldn’t. If you get your app into that place again please let us know and we can take a look. Before going back to a previous commit, you could create a branch at the broken state, and then move the branch your working on back to the previous commit.
Thanks Stu, I will do that!