Thread:Btd456Creeper/@comment-15575766-20150313000733/@comment-28857013-20150318124550

All those characters up there (including the space character!) can be used to break out of an unquoted HTML attribute value. If you escape every last one of them, then you’re probably pretty close to being safe. But you’re still not so safe that you can just start throwing around user input willy nilly.
 * 1) Done here
 * 2) Yeah to the end my module is a trash, so go delete it.
 * 3) Well it does serve, but it doesn't mean we had to redo everything from scratch and trash the old one.
 * 4) My point still stands; it's still quite a bash for me.
 * 5) They were white and had colored strips on the left? Never knew.
 * 6) I don't think I need to further explain since you argued for a wrong thing.
 * 7) My point still stands: You're just officially better in reputation than me.
 * 8) Appeal to hypocrisy. Also I'm not sure if I did, but that wasn't a bragging in my sense. I did write the shortened policies, and what's wrong with that? Are you trying to pick up random things just to prove I'm wrong?
 * 9) Here's an amount of quotes showing why using quotes are better.
 * 10) Even with these simplified definitions, it’s still a pain to remember all the rules for unquoted attribute values, especially as they differ between HTML and CSS. When in doubt, it’s probably best to just use quotes. If you’re confused, it’s likely to confuse your colleagues too. If you’re using user input in an attribute value, always quote (and escape) it to prevent XSS security vulnerabilities. Note that I don’t mean to recommend the use of unquoted attribute values with this article — this is just me reading the spec so you don’t have to.
 * 11) In order for user input to be safe in an unquoted attribute value, a much larger set of characters needs to be escaped than for a quoted attribute value. The vast majority of HTML escaping implementations in web frameworks and JavaScript libraries do not produce output that's safe to use in unquoted attribute values. This means that if you’re using user input in unquoted attribute values and expecting it to be safe because you’re using your favorite framework’s HTML escaper, you may have opened up a big fat XSS vector without even realizing it.  In my opinion, the benefit of not having to type (or serve) a couple of quote characters per attribute isn't worth the XSS risk that unquoted attributes introduce. While I certainly recommend understanding how unquoted attributes work, I strongly recommend against using unquoted attributes.
 * 12) ...You could try to remember all these rules — go for it! But sometimes it just pays to be strict.
 * 13) The traditional answer to people who ask "should I put an attribute value into quotes" has been "when in doubt, quote".  The discussion in this document strongly suggests appending the following to the answer: even when not in doubt, quote anyway.
 * 14) https://css-tricks.com/problems-with-unquoted-attributes/
 * 15) Escaping &, <, >, ", ', `,, !, @, $, %, , =, +, {, }, [, and ] is almost enough

Okay, up to this point, sure I could have avoided it, but as someoe doing coding, I could not leave this alone. Reasons provided all the way along, unless you decide to misunderstand again.

Also, you've proven, in every way that I'm always wrong in situations, and you're still the very best, you've always received reputations, you're always right. I know you're not leaving, so here's the deal: I'll be the one leaving.

Actually it's not now that I've decided leaving, in the 77777th thread I've actually implied that the apparently higher-ranked will stay, but I'm obviously misunderstood.

It's hard for me to live in this community now, so there you have it, you have successfully forced me away. You've been doing this since you joined this community, gets rights and have Meta stripping his own rights just because you're asked to, and now, you're having my rights stripped.

I've actually left this wiki, avoiding contact for at least one day, but since you replied, still bashing me and saying that I'm all wrong, and you're so superior, I guess I've to clear things out a little bit. Sure more replies will come, but meh.