Slowness/Lagging with dropdown Fields in Chromium 89 based browsers (e.g., Edge 89, Chrome 89)


Description

Slowness/Lagging with dropdown Fields (Choice Fields, condition builder operators) in Chromium 89 based browsers (e.g., Edge 89, Chrome 89). Only users on Windows using Chromium 89.x based browsers such as Microsoft Edge 89 and Google Chrome 89 may experience these symptoms. 

As a result, here are some UI issues that users may report:

- Filter Navigators like search and list filters are slow or sometimes get hanged. 

- Slowness or Timeout while the initial rendering of the Dropdown Fields 

- Choosing an option from Dropdown is slow

- Slow performance or freezing of drop-downs while using the scroll bar

Steps to Reproduce

1. Login to the instance 
2. Navigate to incident.list
3. Open any incident
4. Try to modify random dropdown fields ( Category / State)

Actual behavior:
Notice that the form is lagging from time to time and it takes sometimes between 2 and 9 seconds to update the field.

Expected behavior: 
Dropdown gets displayed quickly and the choices can be selected quickly.

Workaround

NOTE: We believe only users on Windows using Chromium 89.x based browsers such as Microsoft Edge 89 and Google Chrome 89 are affected.

RECOMMENDATION - USE A BROWSER WITHOUT THE BUG:

  1. Use an unaffected browser such as Internet Explorer or Firefox
  2. Wait for Google Chrome version 90 to become publicly available on April 13, 2021, and upgrade

WORKAROUNDS IF RECOMMENDATIONS CANNOT BE FOLLOWED:

PLEASE PERFORM STEP 1 AND ONE OF THE OPTIONS FROM STEP 2:

  1. Import UI Macro attached to this PRB
  2. One of the following:
    1. If possible, disable accessibility options in the browser upon each launch (chrome://accessibility or edge://accessibility), or
    2. Launch the browser with the "--disable-render-accessibility" options in the Command Prompt, or
    3. Alter the browser shortcut and include the "--disable-render-accessibility" option

NOTE: Disabling accessibility options will likely affect any software that needs those options enabled.  If the end-user needs assistive technology or whatever app is enabling these options, then the #2 workaround is not possible.

At this time, there are no additional workarounds available.  If the customer cannot implement the workarounds listed above, their only option is to use an unaffected browser (IE or Firefox) or upgrade to Chrome 90 once available.


Related Problem: PRB1483389