Thread:PlasmoidThunder/@comment-957747-20160101153520/@comment-3495717-20160101223126

Right. I understand that my previous code posed a potential security issue, but I don't see why the latest revision to ChatTags.js was rejected; as stated on Shining-Armor's personal wiki, in order to add new tags, you place them below the import script and follow the structure as shown, which I did. Shining-Armor said that in order to replace existing tags, you simply use the same name as the one you want to replace, which for the yt tag, I did; I copied the yt tag from the ChatTags script on Shining-Armor's wiki and did nothing but change [yt to [youtube and alter the size of the embedded player.

To reiterate, there are four sections of code underneath the import statement that refer to three tags and a css alteration to the maximum size of images added to the chat via [img ]; the first two tags are additions, while the last one is a replacement:
 * Greentext - Changes the text colour to a specific shade of green and adds a greater-than symbol before the text. Uses the same effective coding as the [c] tag.
 * Spoiler - Changes the text colour to black and gives it a black background, requiring for users to highlight the text in order to see what was written. Uses a combination of [c] and [bg].
 * YouTube - Exactly the same as the one found in the current ChatTags script, but with the tag changed from [yt video ID] to [youtube video ID] and the player size changed from 420x315px to 210x158px.

If this is all in regards to my minor alterations to the yt tag, then the way the original tag is coded must be insecure, as I have not touched anything to do with how the tag works, but how it looks. If this is in regards to the new tags I added, then the developers section on the ChatTags page is wrong. I fail to see how a css change can pose a security issue.