Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

Hello,

Since the release of chrome version 86.0.4240.75 multiple functionality's are broken in SuperOffice 8.5 R15, logging the following errors in the console:

Trying to create a new appointment:

Trying to open a drop down:

Note: Errors do not happen in SuperOffice 9

RE: Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

Hi,

I have the same issue mainly when creating appointments.

Allready posted in:

https://community.superoffice.com/en/technical/Forum/rooms/topic/superoffice-product-group/crm-web-application/cookie-problems-with-version-82x-and-85x-versions/

 

Af: Norbert van Korlaar 7. okt 2020

RE: Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

Thank you for your report.

R&D will start to digg into this ASAP

Af: Erik Eide 7. okt 2020

RE: Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

Hi Erik,

Thanks for your response that R&D is looking into it.

I have run the chrome-bisect tool to find out what broken it, eventually got this revision range where something was changed that broke it:

https://chromium.googlesource.com/chromium/src/+log/bd2832b620af18975b54a96cca19ea1231a779bf..e752cc67acaa3f25f0ced9e002d808e7aaacd734

Hopefully it helps.

Af: David Hollegien 7. okt 2020

RE: Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

This update seems to break SuperOffice versions between 8.0 - 8.4 R02. 

Minipanel and bottom sections doesn't load data, buttons on top right corner isn't clickable.

Trying to change filter settings gives this error message:

Newer versions looks fine.
Edit: Newer versions does not look fine.
The issues are different on versions between 8.4 R03 - 8.5 R14 (wasn't able to test R15)
It is not possible to get lists to work, when you for example create a new appointment. After choosing a type, the lists stops loading and gives errors in the console as mentioned here.

Af: Serkan Gonca 7. okt 2020

RE: Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

Hi , 

Also wanted to note that also 8.2 version is effected and is neerly unusable with this Chrome version.

Please consider a patch for this version also, an upgrade to a higer version is not always possible in a short time .

Kind Regards

Af: Mehmet Canavar 7. okt 2020

RE: Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

I also have a customer experiencing this issue on version 8.5 R13

 

They are going over to edge for the time being, but is looking forward to a fix asap.

Af: Dennis Aagaard Mortensgaard 8. okt 2020

RE: Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

We have multiple customers experiencing this issue, for now we recommend temporarily switching to another browser but that isn't always possible.

Any ETA on a fix?

Af: David Hollegien 8. okt 2020

RE: Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

I'm getting reports that the beta version of edge (which will include the same version of the chromium engine that is causing the issue) is also experiencing this behavior. That means it will soon not even be an option to circumvent the problem by using edge.

Af: Dennis Aagaard Mortensgaard 8. okt 2020

RE: Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

Hi,

Also experiencing this on Version 8.5 R15

Creating for ex. a Task , cannot select Compay from list and trying the search function eventually gives:

Dialog callback execution went horribly wrong: undefined_obj is not defined

Hope for a fix asap.

 

Af: Remco Koot 8. okt 2020

RE: Javascript errors with SuperOffice 8.5 R15 starting with chrome release 86.0.4240.75

Hey :)
We are working on it! And have found a bug, fixed and testing it now on 8.5 R15, but...

We are not sure about fixing all the older versions, since this fix is in a bundle of java joy... but we'll keep digging for possibilities for older versions.

As you all have started to do, is to move to other browsers, but we do understand that it's not a permanent soloution.

We'll keep you posted!

Af: Kirsti Aakerholt 8. okt 2020