Sounds Similar to some of the issues we have experienced as well.
In version 15.57 we were able to make a call using contentDocument.Eval() and it worked fine. Versions after that it do not work. After many months and asking for feedback on this issue, TestComplete Support finally, said that the eval function was deprecated by Chrome/Javascript. It is my understanding this was related to Chrome moving to Manifest version 2. So, the newer versions of TestComplete work with Manifest version 2. Older versions of TestComplete worked with manifest version 1 which allowed the call to the eval function. We are currently exploring an option of attempting to call the functions directly (and bypassing the eval function) by using contentDocument.Script.functionname(), but that is not working in version 15.64 of TestComplete.
My code is not using eval(), at least visibly.
You were lucky to get a hint from the support...
Started copying the Sales person on the requests for updates to the open ticket. Would go back every couple of weeks with another email requesting an update and complaining about lack of support. Sales did eventually get someone else involved, and a few months later finally got the response there is nothing they can do, and that was when they mentioned the Manifest version. I did have some other open issues as well, that were not getting addressed in a timely manner, so those were included in my complaints as well.
