Latest Version of Google Chrome Issues with JSS

Oh! And I thought it was just me. I haven't got around to clearing the browser cache to see if that fixes the issue, as I have too much open...

This should be more easy to find, but here is the links...

JAMFPro Known Issues

PI-007099 When using Google Chrome release 75.0.3770.80, adding scripts or packages to policies prevents you from saving or cancelling the policy. Workaround: Use a different browser.

I've also had this! I only use Chrome for work so this is really annoying.

I guess it'll also affect the current dev preview of Edge on Mac (which is excellent if anyone is wondering) as it's basically the same browser.

Also seeing this on Chrome 75.0.3770.100.

Confirming the original post, looking through the JSS log you see some really strange errors
2019-06-24 14:39:08,873 [ERROR] [Thread-5 ] [HTMLController ] - Exception processing HTMLResponse: java.lang.NullPointerException at java.lang.String$CaseInsensitiveComparator.compare(Unknown Source) at java.lang.String$CaseInsensitiveComparator.compare(Unknown Source) at java.lang.String.compareToIgnoreCase(Unknown Source) at com.jamfsoftware.jss.objects.policy.PolicyHelper$10.compare(PolicyHelper.java:1536) at com.jamfsoftware.jss.objects.policy.PolicyHelper$10.compare(PolicyHelper.java:1533) at java.util.TimSort.countRunAndMakeAscending(Unknown Source) at java.util.TimSort.sort(Unknown Source) at java.util.Arrays.sort(Unknown Source) at java.util.ArrayList.sort(Unknown Source) at java.util.Collections.sort(Unknown Source)

Is there a planned fix for this ? Has it been logged to Google Chrome devs, or is it an issue on the JSS side of things - anyone know ?

Seeing this as well. Works fine in Edge (MS Edge, not Chromium Edge) but it's really laggy in comparison.

Chrome (Version 75.0.3770.100) has the same behaviour on macOS (with JAMF Pro 10.12). Really annoying, Safari works as a workaround.
I hope it will get fixed soon.

Still a thing with Chrome version 75.0.3770.142 (Official Build) (64-bit). Issue reproduced after clearing caches and in Incognito mode. Issue reproduced on first install, not signed in to Chrome sync and with no extensions.
Safari works.

<expletive><expletive><expletive>!!!

Wish I'd seen this yesterday afternoon...at least now I know what's going on with the policy I'm trying to create.

This applies to all Chromium browsers as well (IE Brave). Still exists with all latest versions. Very frustrating.

Seeing this also. Have to switch to Firefox if I want to make policy changes.

Edge Chromium as well (but obviously it's now Chromium based so not surprising).