3 ms·
Detecting that kind of problem is not hard. When someone is posting a comment, or even while they're editing it, you could point it out to them.
by VikingCoder 13y ago
Detecting that kind of problem is not hard. When someone is posting a comment, or even while they're editing it, you could point it out to them.
- shurcooL 13y agoI don't understand the motivation of that argument. Writing assembly isn't hard either, is it. If they make a mistake, you can point it out to them.
- VikingCoder 13y agoYou're asserting users screw things up. Fine, I'm saying that showing a user they screwed up is neither a technology challenge, or a user interface challenge. If I type squirtle right now in my browser, Chrome underlines it in red. Everyone's used to this. Showing <code><code> with the second code underlined in red, to tell the user to change it to </code> is neither technically difficult, or confusing to users. My point being, you seem to be arguing that markup is hard to make mistakes in. I'm retorting that helping users correct their HTML mistakes is not hard, and is a valid response to the problem that <code><code> poses.
- shurcooL 13y agoThat is a much better articulated argument, thank you. I'm happy to say I agree that your retort's point is valid.