Process Editor not rendering symbols in process elements correctly

mariano_froh

Dear Axon Ivy Team and Community,

since today, we have been experiencing an issue in Axon Ivy Designer 12 (versions 0.7, 0.8, 0.9) where the process editor is no longer displaying the symbols correctly. They are outside the process elements (see picture below):

In addition, the context menu that used to open after right-clicking in the process editor no longer opens.

We assume, this may be related to Windows or MS Edge updates.
I have already reinstalled Edge and Webview2 according to the instructions here: https://community.axonivy.com/d/1006-troubleshooting-with-webview2
but this did not resolve the issue.

We would be very grateful for any help.

Best regards,
Mariano

Lukas Lieb

Hi mariano_froh

Thanks for the report!
Yes, it seems to be related to a change on chrome-based browsers in the latest versions: https://developer.chrome.com/release-notes/141?hl=en#support_width_and_height_as_presentation_attributes_on_nested_svg_elements

I will have a look at it.

Reguël Wermelinger

We can confirm that a Chrome change caused this effect. Therefore, Windows (Edge) users are widely affected by this through a Windows Update.
We're currently fixing this issue for the upcoming releases (10.0.32, 12.0.10, 13.2).
Meanwhile you may work-around the issue by right-clicking into the process -> Open in External Browser -> Then copy the URI of the opened browser into a non Chrome based browser, like Firefox.

Lukas Lieb

The problem is that we can only fix this for newer Ivy versions (10.0.32, 12.0.10, 13.2).
So currently there are to following solutions to fix this problem:

Use a nightly version: https://developer.axonivy.com/download/archive/unstable
Use an older chrome-based browser (pre v141)
Patch Ivy

Patch Ivy

To patch your Pro Designer (Eclipse), you have to add the following snippet to the following file.

.sprotty-graph svg {
  height: attr(height px);
  width: attr(width px);
}

Pro Designer (Eclipse)

v10.0.x: AxonIvyDesigner/plugins/ch.ivyteam.glsp.eclipse.editor.client_*/diagram/assets/diagram-*.css
v12.0.x / v13.x: AxonIvyDesigner/plugins/ch.ivyteam.glsp.eclipse.editor.client_*/diagram/assets/index-*.css

Replace x with the corresponding version or hash.
For MacOS the plugins folder is in AxonIvyDesigner.app/Contents/Eclipse

Process Viewer (Pro Designer / Engine)
v10.0.x:

Unpack AxonIvyEngineOrDesigner/webapps/ivy/WEB-INF/lib/editor-client-standalone-*.jar
Add snippet to the style tag of META-INF/resources/process-editor/index.html
Pack (compress) META-INF as editor-client-standalone-*.jar
Clear browser cache and reload

v12.0.x / v13.x:

Unpack AxonIvyEngineOrDesigner/webapps/ivy/WEB-INF/lib/process-viewer-client-*.jar
Add snippet to META-INF/resources/process-viewer/assets/index-*.css
Pack (compress) META-INF as process-viewer-client-*.jar
Clear browser cache and reload

Neo Designer

Unpack AxonIvyEngine/webapps/neo-designer/neo-designer-*.jar
Add snippet to META-INF/resources/process-editor/assets/index-*.css
Pack (compress) META-INF as neo-designer-*jar
Clear browser cache and reload

Replace x with the corresponding version or hash.

Ernesto

After adding patch the problem has gone in my current version 13.1.1

Lukas Lieb

Just for your information:

There are plans to revert this change in chromium (https://issues.chromium.org/issues/449170647), so maybe after the next update it will behave like before also on older Ivy versions.
However, our change for the next versions should still behave correctly, so we will not revert it. This in favor of whether this change will come back later or in a different state.

mariano_froh

Lukas Lieb thank you very much for your quick help!

Lukas Lieb

The chromium team did revert this change. So the process editor should behave as before even without to the latest ivy releases or patching.
For it please make sure you have updated your chromium based browser (chrome, edge) to the latest version.
For the WebView2 (edge runtime in the Eclipse Pro Designer), I'm not sure how the update cycle of microsoft is. Maybe you have to wait here to the next Windows Update?