Description of Problem

https://github.com/argoproj/argo-cd/issues/20392

When typing in the "Application Name" field (or the Namespace field in the DESTINATION section, and we suspect this can happen in other fields too) during the creation of a new application, the input text starts blinking and oscillates between different words (e.g., "ce" and "chrome" when trying to enter the word "chrome"). This behavior can be triggered sometimes by hitting the backspace key, retyping the text, clicking elsewhere, and returning to the text box. However, once triggered, the text continues to "blink" indefinitely.

Additional Info

• Git issue does contain video of blinking filed 
  https://github.com/argoproj/argo-cd/issues/20392

Problem Reproduction

• While creating ArgoCD Application

Reproducibility

• Intermittent

Prerequisites/Environment

• ArgoCD 

Steps to Reproduce

• Open ArgoCD Dashboard and Click on New App 
• Starting entering details of Application
• Try adding name and backspace repeatedly couple of times

Expected Results

• Input field contain entered text

Actual Results

• Input field text starts blinking the text 

Problem Analysis

• In browser seen 504 Gateway timeout errors 

Root Cause

Workaround (If Possible)

• Use Edit Yaml option and use yaml to create application 

Fix Approaches

• <If we decide to fix this bug, how will we do it?>

Acceptance Criteria

• ...

Definition of Done

• Code Complete:
  • All code has been written, reviewed, and approved.
• Tested:
  • Unit tests have been written and passed.
  • Ensure code coverage is not reduced with the changes.
  • Integration tests have been automated.
  • System tests have been conducted, and all critical bugs have been fixed.
  • Tested and merged on OpenShift either upstream or downstream on a local build.
• Documentation:
  • User documentation or release notes have been written (if applicable).
• Build:
  • Code has been successfully built and integrated into the main repository / project.
  • Midstream changes (if applicable) are done, reviewed, approved and merged.
• Review:
  • Code has been peer-reviewed and meets coding standards.
  • All acceptance criteria defined in the user story have been met.
  • Tested by reviewer on OpenShift.
• Deployment:
  • The feature has been deployed on OpenShift cluster for testing.