editor-injector: uncaught type error when previewing markdown
MR: Pending <!-- The first line of the MR must be one of the following: 1. `MR: Pending` 2. `MR: <MR link with trailing +>`, and the first description line of the MR should be `Issue: <Issue link with trailing +>` 3. `MR: No MR` For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/index.html#1-to-1-relationship-of-issues-to-mrs --> <!-- The following sections should be filled out as part of the refinement process before the issue is prioritized. For more context, see: https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#2-pre-iteration-planning-meeting --> ## Description 1. Create a workspace. 2. Open browser developer console. 3. Open markdown file in the editor. 4. Preview the markdown file. 5. Notice the following error in the developer console ``` Uncaught (in promise) TypeError: Failed to execute 'createNodeIterator' on 'Document': parameter 1 is not of type 'Node'. at n (VM20 injected.js:17:294319) at VM20 injected.js:17:294716 at Vo (VM20 injected.js:17:294736) at ka.ensureFillableField (VM20 injected.js:17:309840) at VM20 injected.js:17:312452 at o (VM20 injected.js:17:309548) at Object.p [as dispatch] (VM20 injected.js:17:306886) at VM20 injected.js:17:348913 n @ VM20 injected.js:17 (anonymous) @ VM20 injected.js:17 Vo @ VM20 injected.js:17 ensureFillableField @ VM20 injected.js:17 (anonymous) @ VM20 injected.js:17 o @ VM20 injected.js:17 p @ VM20 injected.js:17 (anonymous) @ VM20 injected.js:17 Promise.then (async) getFrameManagerConfiguration @ VM20 injected.js:17 Bs @ VM20 injected.js:17 yy @ VM20 injected.js:17 (anonymous) @ VM20 injected.js:17 (anonymous) @ VM20 injected.js:19 Show 13 more frames Show less ``` ![image](/uploads/f0e52e5cd8b71107e8982e31b2117437/image.png) ## Acceptance Criteria TODO: Fill out (required) - [ ] [Describe what must be achieved to complete this issue.] - [ ] [Describe another requirement needed to complete this issue.] - [ ] [Add additional acceptance criteria as needed.] ## Technical Requirements TODO: Fill out or delete [If applicable, please list out any technical requirements for this feature/enhancement.] ## Design Requirements TODO: Fill out or delete [If applicable, please provide a link to the design specifications for this feature/enhancement.] ## Impact Assessment TODO: Fill out or delete [Please describe the impact this feature/enhancement will have on the user experience and/or the product as a whole.] ## User Story TODO: Fill out or delete [Provide a user story to illustrate the use case for this feature/enhancement. Include examples to help communicate the intended functionality.] <!-- Replace with other type, e.g. bug or maintenance, if appropriate --> <!-- Replace with other subtype if appropriate --> <!-- By default, all issues start in the unprioritized status. See https://about.gitlab.com/handbook/engineering/development/dev/create/ide/#-remote-development-planning-process --> <!-- For simplicity and to avoid triage bot warnings about missing workflow labels, we will default to issues starting at the refinement phase -->
issue