Answers.Body: <p>You don't mention CMS but if this is Drupal then I would recommend you upgrade to 7.71 due to</p>
  
  <ul>
  <li><a href="https://www.drupal.org/node/3143016" rel="nofollow noreferrer">Fix for jQuery Form bug in Chromium-based browsers</a> </li>
  </ul>
  
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-17T23:34:45.080Z
Answers.Text: I was using Drupal 7.71; now after security release today, I'm on 7.72. Jquery update version is  7.x-2.7 and uses 1.10 Jquery version. I have now install the alpha version and upgraded the jquery_update to 3.1. No joy on either front.
Answers.UserDisplayName: TimETown
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-18T01:04:04.893Z
Answers.Text: sorry to hear that. i can't recall hitting this issue - just a few clients have said 'problems uploading' (not certain if they were all drupal or some were civi forms) and have then confirmed it works in FF and not in Chrome, and so we updated Drupal and didn't hear back. Have now just done the security upgrade for all of them too.
Answers.UserDisplayName: petednz - fuzion
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-19T11:41:54.150Z
Answers.Text: I have Chrome Version 80.0.3987.137 (Official Build) (64-bit) on my Chromebook and it works like a charm. It's certainly something with Chrome 83. I'm not entirely convinced it's the same jquery-Ajax bug discussed in the thread you mentioned--or more to the point, it looks like the kcfinder script includes it's own version of jquery code which would make a Drupal core patch not help? Knowing this is Chrome's bug and should eventually be fixed once Chrome gets to version 85 may make working on it not worthwhile.
Answers.UserDisplayName: TimETown
Answers.ContentLicense: CC BY-SA 4.0
Answers.CreationDate: 2020-06-16T21:36:26.347Z
Answers.LastActivityDate: 2020-06-16T21:36:26.347Z
Answers.UserDisplayName: petednz - fuzion
Body: <p>There did not use to be a problem with the media browser in CiviMail when using Chrome, but it's broken now.</p>
  
  <p><a href="https://BASEURL/sites/all/modules/civicrm/packages/kcfinder/js/index.php" rel="nofollow noreferrer">https://BASEURL/sites/all/modules/civicrm/packages/kcfinder/js/index.php</a> 3.12</p>
  
  <p>WORKS in Firefox: shows KCFinder: /image33 files (4 MB) </p>
  
  <p>Does not work/Hangs showing "CIVICRM File Manager" as heading
  Chrome Version 83.0.4103.97</p>
  
  <p>Other reports of hanging while trying to upload or select images.</p>
  
Tags: <civimail><images>
Title: problems with kcfinder image browser in Chrome
ThreadText: # problems with kcfinder image browser in Chrome
  
  (Asked by: username_0 on 2020-06-16)
  
  There did not use to be a problem with the media browser in CiviMail when using Chrome, but it's broken now.
  
  <https://BASEURL/sites/all/modules/civicrm/packages/kcfinder/js/index.php> 3.12
  
  WORKS in Firefox: shows KCFinder: /image33 files (4 MB)
  
  Does not work/Hangs showing "CIVICRM File Manager" as heading
  Chrome Version 83.0.4103.97
  
  Other reports of hanging while trying to upload or select images.
  
  **Tags:** civimail, images
  
  
  ---
  
  ## 1 answers
  
  ### Answer by username_1 on 2020-06-16. Score: 1
  
  You don't mention CMS but if this is Drupal then I would recommend you upgrade to 7.71 due to
  
  * [Fix for jQuery Form bug in Chromium-based browsers](https://www.drupal.org/node/3143016)
  
  > **Comments:**
  > **username_0**: I was using Drupal 7.71; now after security release today, I'm on 7.72. Jquery update version is  7.x-2.7 and uses 1.10 Jquery version. I have now install the alpha version and upgraded the jquery_update to 3.1. No joy on either front.  
  > **username_1**: sorry to hear that. i can't recall hitting this issue - just a few clients have said 'problems uploading' (not certain if they were all drupal or some were civi forms) and have then confirmed it works in FF and not in Chrome, and so we updated Drupal and didn't hear back. Have now just done the security upgrade for all of them too.  
  > **username_0**: I have Chrome Version 80.0.3987.137 (Official Build) (64-bit) on my Chromebook and it works like a charm. It's certainly something with Chrome 83. I'm not entirely convinced it's the same jquery-Ajax bug discussed in the thread you mentioned--or more to the point, it looks like the kcfinder script includes it's own version of jquery code which would make a Drupal core patch not help? Knowing this is Chrome's bug and should eventually be fixed once Chrome gets to version 85 may make working on it not worthwhile.  
  
  ---
  
  