## Description In the previous glorious epic https://gitlab.com/groups/gitlab-org/-/epics/895, we moved all but a few karma specs over to Jest. Let's finish the job. ## What specs are remaining? Check out the issues attached to this epic. They are located in `spec/javascript` and end in `_browser_spec.js`. ## How should we remove these karma specs? If we could move them to Jest that'd be great, but these were determined to be particularly challenging because there's some special coupling to a real browser environment. This gives us two options: 1. Move it to Jest. This potentially requires extending our `jsdom` mocked browser environment. 2. Move it to RSpec. This will probably require us changing our perspective to a use-case oriented one. We just want to make sure we have the same value coverage.