Repeated rejection for issues... that no longer exist in the code

Back in November '21, I uploaded an extension (Three Island) to the Mozilla Add-Ons store. At the time, it used innerHTML to create nodes, and although it was initially approved, it was rejected about 8 months ago, citing the following:

========
This add-on didn’t pass review because of the following problems:

  1. This add-on is creating DOM nodes from HTML strings containing potentially unsanitized data, by assigning to innerHTML, jQuery.html, or through similar means. Aside from being inefficient, this is a major security risk. For more information, see https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Safely_inserting_external_content_into_a_page . Here are some examples that were discovered:

three-island.js - line 269

========

I updated the code accordingly (using code the EXACT way specified in the link given, as can be seen in https://github.com/PartMan7/Three-Island/blob/main/dist/firefox/unpacked/three-island.js . Despite this, every single version I attempted to release after that has ended up rejected for the same reason, with one of the reviewers, ironically enough, saying this:

========
Rejected by Add-ons Review Team

This add-on didn’t pass review because of the following problems:

  1. This add-on is creating DOM nodes from HTML strings containing potentially unsanitized data, by assigning to innerHTML, jQuery.html, or through similar means. Aside from being inefficient, this is a major security risk. For more information, see https://developer.mozilla.org/en-US/Add-ons/WebExtensions/Safely_inserting_external_content_into_a_page . Here are some examples that were discovered:

three-island.js - line 254, 255

appendChild is similar to innerhtml.
Please sanitize before appending.

========

Every time something like this would happen, I’d have to upload a new version because I have received zero responses to my Developer replies, and at this point I keep having to ask users to switch to a different browser to use the extension from the Chrome store.

I’ve checked many, many times, and the code that’s written does not use any innerHTML assignments. But despite me explicitly mentioning this in my developer comments while submitting the extension for review, me and the reviewer seem to have differing ideas on what the article means, and I would very much appreciate some assistance in this matter.

I want to make sure I understand this correctly.

Is the reviewer saying that Firefox extensions aren’t allowed to use appendChild() ?
Because it’s used in Safely inserting external content into a page

My point EXACTLY ;-;