Such scripting errors can be shown when:

  • Operator is using a separate, customized start page in Codesys,
  • as a WebBowser Scripting Error (when f.e. using a Visual "web Browser" element to show a web-server of another device)

Background information

The WebBrowser-Control for Windows Forms used within Codesys, offers only extremely few configuration possibilities.
The embedded browser behaves normally like an Internet Explorer 6 or IE 7, for "compatibility reasons", and there is no reasonable possibility for the application to influence this.

The HTML page itself, can inform the browser (with suitable Meta tag’s) that the browser should be rendering the side like in a newer IE version.

So, the Website must be changed so that it supports the Codesys browser.


Some tips from the internet:

See: https://stackoverflow.com/questions/4655662/how-to-ignore-script-errors-in-webbrowser/27705241

"...
First you need to know that the webbrowser control is using IE7 as its base (i.e. the older version of Internet Explorer) so the scripts which you are running now are compatible with the modern age browsers and thus the error. First of all, if you'll put:

<meta http-equiv="X-UA-Compatible" content="IE=edge"/>

inside your section of the page, it will render with the IE version installed on the machine instead of the default IE 7

Hope this Helps!

..."

FAQ: 



  • No labels