Tracking issue: Run tests to help decide about search technology (JCEF vs native)

Created by: vdavid

Things to test, in rough order of decreasing priority:

Google Doc Notes

• Can we add a JCEF component anywhere on the UI?
• Can we put a JCEF component to a modal?
• How long does it take to load the modal with content (does the JCEF component flicker?)
• Can we customize the colors of the web view to match the JetBrains layout?
  • How does the bridge between native and browser look like? Look for custom UI settings and see how we can forward them to the browser environment.
• Can we avoid page refreshes and loading indicators to a large extent?
• How can we measure and compare the startup speed of the web view in comparison to a native widget?
• Debugging Tools: Can we connect chrome debugger (for UI tests)?
• Keyboard handling: Does tabbing inside and outside the JCEF component work as intended?
• Keyboard handling: There are default shortcuts for interacting with a search box. Do these work?
• Keyboard handling: Do custom keyboard shortcuts work as well?
• Can we register events in Analytics? (are we sandboxed?)
• What browser APIs are supported
  • And what about older JetBrains versions?
• Can we support VIM Mode? (Does VIM mode apply to modals at all, or is that editor-only?
• How can we bundle the JavaScript?