Skip to main content

We’ve discovered that a recent update to the Chrome Browser, and thus also to the latest Edge browser causes a problem with IFS Cloud Web 22R1 & 22R2, all SU levels.
This started appearing 1st week of April 2023. We don’t know the exact Chromium versions. In Edge seems to be from version 112.0.1722.46.

(The problem is same in both Chrome and Edge, since Edge today is using the same web rendering engine “Blink” from the Chromium project - so in essence Chrome and Edge always renders the same)

We have investigated and found a solution and we are working on getting it out as soon as possible.
Note that this appeared suddenly without any code changes or new deployment from IFS. So Chrome started to behave and render this element in a different way. (Then whether this is caused by IFS Cloud rendering code not adhering to some standards, the root cause analysis will have to show later).

We are very sorry for any convenience caused, and we understand the frustration for users.

A tip/workaround that seems to work for some - this depends on your screen resolution - is to temporarily change the browser visual zoom level (e.g. use Ctrl+wheel mouse to zoom to 90%).

There is a support case CS0133544 for ref

 

A solution for this problem has been developed and the correction will be in the next possible Service Updates for both affected tracks. Will solve the issue in both Chrome and Edge (given they are using the same engine). 

22.1.15 (22R1 SU15) , 22.2.8 (22R2 SU8) 

Fingers crossed Chromium doesn’t change it’s HTML/CSS styling interpretation again related to this. 

Again, we understand the frustration this causes users, and hope it’s a driver for taking the latest SUs.

A solution for this problem has been developed and the correction will be in the next possible Service Updates for both affected tracks. Will solve the issue in both Chrome and Edge (given they are using the same engine). 

22.1.15 (22R1 SU15) , 22.2.8 (22R2 SU8) 

Fingers crossed Chromium doesn’t change it’s HTML/CSS styling interpretation again related to this. 

Again, we understand the frustration this causes users, and hope it’s a driver for taking the latest SUs.

will this issue also be fixed in 23R1 GA?

(since our project decide to release update to it.)

 

A solution for this problem has been developed and the correction will be in the next possible Service Updates for both affected tracks. Will solve the issue in both Chrome and Edge (given they are using the same engine). 

22.1.15 (22R1 SU15) , 22.2.8 (22R2 SU8) 

Fingers crossed Chromium doesn’t change it’s HTML/CSS styling interpretation again related to this. 

Again, we understand the frustration this causes users, and hope it’s a driver for taking the latest SUs.

will this issue also be fixed in 23R1 GA?

(since our project decide to release update to it.)

 

Yes it will, but not mentioned above since it not released to the market yet.

Not so ideal, but a possible workaround is to change the zoom to 90% (or some value that suits the resolutions). 90% works for me.

 

Oops…. didn’t read the post fully :)… the workaround is already proposed…

Mine worked on 110% both on Edge and Chorme 

Incidently on FixFox I am not getting this issue

Regards

Pankaj

 Another workaround: make a tiny change in CSS here:

search-input-wrapper

F12 > Ctrl Shift C > uncheck “height”

Works only in the specific tab / window, only to next refresh. To keep change longer you may try to use an addon for custom CSS (ie. Stylish)

This issue has been fixed in the below versions.

22.1.15 - 22R1 SU15
22.2.8 - 22R2 SU8
23.1.0 - 23R1 GA
23.2E.0 - 23R2 EA

Reply


Terms & ConditionsCookie settings