Forum Discussion

toto's avatar
toto
Occasional Contributor
2 months ago
Solved

i would like to know if JointJS requests are supported ?

actually we are using WebView2 and GoJS request with TestComplete and we should switch to JointJS instead of GoJS.
i would like to know if JointJS requests are supported ? 

  • rraghvani's avatar
    rraghvani
    2 months ago

    WebView2 apps can still inject scripts programmatically because they are host applications, not extensions inside a browser. Unlike, Manifest V3, which disables certain kinds of dynamic script injection for browser extensions.

    Now to answer your original question - JointJS and GoJS are not supported technologies of TestComplete. However, they may work in WebView2 host applications.

    Something to think about - there could be a possible chance of WebView following Chromium, to disable script injection in the future.

9 Replies

  • Hassan_Ballan's avatar
    Hassan_Ballan
    Icon for Champion Level 3 rankChampion Level 3
    2 months ago

    To clarify based on current TestComplete documentation and release notes:

    • ✅ WebView2 is officially listed as supported as of TestComplete version 15.69.
      However, community discussions report limitations — especially with element recognition and stability. So while support exists, it may not be as reliable as with standard browsers like Chrome or Edge.
    • ❌ JointJS and GoJS are not officially supported. They don’t appear in the list of Supported Web Controls and Libraries or the Supported Browsers and Web Technologies.
    • 🔧 That said, it is still possible to interact with JointJS via JavaScript injection, just as you are doing with GoJS. If the diagram model (e.g. graph, paper, or specific cells) is accessible from the global window object, you can retrieve or manipulate data through script evaluation — although this remains an unsupported workaround.

    Summary: ⚙️ Script injection (like you used with GoJS) may still work for JointJS, depending on how your app exposes its internals.

    🤖 AI-assisted response
    👍 Found it helpful? Click Like
    ✅ Issue resolved? Click Mark as Solution

  • toto's avatar
    toto
    Occasional Contributor
    2 months ago

    thanks for the link but it is not up to date because i don't found Microsoft Webview2 nor GoJS in the list but currently it is supported 

    • rraghvani's avatar
      rraghvani
      Icon for Champion Level 3 rankChampion Level 3
      2 months ago

      Supported Technologies and Applications shows what TestComplete actually supports. It does not mention GoJS or JointJS, therefore, it is not supported.

      Where have you read, it is supported?

      • toto's avatar
        toto
        Occasional Contributor
        2 months ago

        you don't catch my point.
        i never read it in TestComplete documentation.
        But i know it is supported because i currently using it in Testcomplete since one year.
        example of my testcomplete code using WebView2 and GoJS query:

        let query = `${diagram}.findNodeForKey(${selectedDeviceKey}).data.${FieldNames}`;
        var deviceInfoVal = oParent.contentDocument.Script.eval(query);

        So my question is shall i do the similar query with JointJS instead of GoJS



  • toto's avatar
    toto
    Occasional Contributor
    2 months ago



    i saw in doc that eval is not supported in JavaScript 

    but eval method is working well with embbeded web via WebWiew2 in last testcomplete version

     

     

    • rraghvani's avatar
      rraghvani
      Icon for Champion Level 3 rankChampion Level 3
      2 months ago

      WebView2 apps can still inject scripts programmatically because they are host applications, not extensions inside a browser. Unlike, Manifest V3, which disables certain kinds of dynamic script injection for browser extensions.

      Now to answer your original question - JointJS and GoJS are not supported technologies of TestComplete. However, they may work in WebView2 host applications.

      Something to think about - there could be a possible chance of WebView following Chromium, to disable script injection in the future.

    • Hassan_Ballan's avatar
      Hassan_Ballan
      Icon for Champion Level 3 rankChampion Level 3
      2 months ago

      It’s expected that your page.contentDocument.Script.eval() call still works — the behavior depends on which browser engine your test uses.

      In Chrome or Edge, the eval() method is no longer supported because Chrome Manifest V3 disables dynamic code execution for security reasons. This is confirmed in SmartBear’s documentation Run JavaScript on Web Pages

      The use of eval() in JavaScript is no longer supported with the migration to Chrome Manifest V3.


      However, if you run the same code in Firefox, Internet Explorer, or within TestComplete’s internal JavaScript engine, it will still work — those environments don’t enforce Manifest V3 restrictions.

      You can also confirm that in other scripting languages (like Python, VBScript, or DelphiScript) the equivalent eval() or Evaluate() functions remain supported, since they execute in TestComplete’s own engine rather than the browser.

      🤖 AI-assisted response
      👍 Found it helpful? Click Like
      ✅ Issue resolved? Click Mark as Solution