html_encode() bug

ID:968406
 
Sep 7 2012, 3:07 pm
Keywords: a, bug, encode, html, if, not, p, sure, though
Not a bug
BYOND Version:496
Operating System:Windows 7 Ultimate 64-bit
Web Browser:Chrome 21.0.1180.81
Applies to:Dream Seeker
Status: Not a bug
This is not a bug. It may be an incorrect use of syntax or a limitation in the software. For further discussion on the matter, please consult the BYOND forums.
When typing a message in the default input box it will actually cancel all html codings. (\n, etc..)

Undefeated Saiyans: Hello! \n


But when making a custom input in skin with the chat command or other thing, html won't cancel \n

Undefeated Saiyans: Hello!





----
Is this a bug?

You can easily test this out by
1. Make a game
2. Make a chat code or something
mob/verb/OOC(t as text)
  if(t){world<<"[src.name]: [html_encode(t)]"}

3.Make a skin file and put an input with the OOC command.
4.Type \n
And you should see that the html_encode() doesn't work with \n when using an interface/input to use the verb.
Sep 8 2012, 8:07 am
\n isn't HTML.
Sep 8 2012, 8:20 am
Okay nevermind about that then lol.
But still
html_encode() still blocks \n when using the regular input
Sep 9 2012, 11:41 pm
html_encode() doesn't, the input does. This isn't really a bug I think, so much as the design of the standard skin, versus the more open ended input controls.

You solution would be (if you wanted \n filtered), to write a few lines to find and remove \n yourself, probably using text2ascii() or such.
Sep 10 2012, 6:34 am
I'm not sure I even understand the bug report, but it's clear it's definitely not a bug with html_encode() itself.

As far as the skin is concerned, \n should be treated the same whether the OOC command was pre-entered or not. The only exception I can see is if the command did not have a quote with it.
Dec 26 2013, 6:36 am
I was so stupid back then. .-.
Dec 26 2013, 6:44 am
Stephen001 resolved issue (Not a bug)