If this is a Chromium bug, what are you fixing with the CPS Release then?
Chromium closed their bug only last Thu. Until then we were not sure about when they'll have a fix. The fix we added was basically one of their recommendations.
We'd also like to avoid shipping a patch.
We are running in circles in our companies out here, re-evaluating our upgrade plans, browser policies, etc, to figure out how to make this go away.
If PTC has any respect for them selves, at least test this internally and let us know what to expect. In the compatibility Matrix it says that Chrome versions newer than version 57 is supported. I hope you will live up to that promise by being proactive in testing future versions.
We do understand your concerns and this is exactly why we’re trying all possible options to solve the problem at the earliest.
I have installed Version 86.0.4187.0 and verify that the issues are not there anymore!
However, I cannot understand when this Chrome version will be out as production release.
Has anybody an idea?
Just tested a few of our usecases in respectively Chrome (Dev) 85.0.4181.8 and Chrome (Canary) 86.0.4187.0
I can confirm that the issue still persist in 85.0.4181.8, but not in 86.0.4187.0
So, it looks like something happened 🙂
Not sure if Edge (Chromium) is supposed to have this fix in versions newer than 85.0.4182.0 as well as Chrome? Do you have a link to the Chromium changelog about this fix?
I also tested with Edge versions 85.0.552.1 (DEV) and 85.0.562.0 (Canary), where the issue still persists.
I will test again when any of these Edge channels have caught up to 85.0.4182.0
Happy to learn that this can be fixed without applying a CPS 🙂
Now, we can't wait for the stable versions of Chrome/Edge version 85 to be released.
Chrome: 25 August
Edge: Hopefully close to August 25 as well.
I have downloaded and installed Google Chrome Canary from here https://www.chromestatus.com/features/schedule
Version 86.0.4187.0 (Offizieller Build) canary (64-Bit)
The problem is NOT reproducible there!
Ah. I see.
I will wait until it's at the stable status. I don't think my company would appreciate me downloading a development version. Especially since we can use IE for now.
No one have mentioned that PTC published workaround to solve the issue.
if google fix the problem in the browser then the workaround should be reversed.
PTC Case CS326191 describes the workaround. I tested it and it works.
I also tested and it works. We will put into production this weekend.
note: Every user has to force refresh (control F5).
i'm holding out for the chrome fix and/or the installation of CPS14 to cure this. the work-around needs to be implemented now and then removed when chrome gets to the fix version in production. i only wan to fix this once.