< /html > function to the end of posts and descriptions to automatically close everything.
TappedOut forum
Posted on Dec. 18, 2014, 11:02 p.m. by Blizzicane
Its be mention before by Epoch and others and it might have even had a thread once but all that is buried away somewhere so I decided to make a thread suggested it should be done seeing how easily it can be abused to mess up the front page and anywhere really as long as someone can write somewhere. :3
vampirelazarus says... #3
Here's an example on the site itself:
As you can see, everything is italicized, despite the < /hmtl > tag
December 19, 2014 12:34 a.m.
Blizzicane says... #4
vampirelazarus Hmmm well I don't know too much about html either as I was just quoting off what Epoch said in another thread. But I at least know there is at least way to automatically contain the code similar to what was done on profile pages back when you could leave certain tags open and color your entire profile page in a color until yeaGO set something that closes the tags preventing the profile page from being colored everywhere (I still miss that XP). :3
December 19, 2014 12:47 a.m.
vampirelazarus says... #5
The problem might be that the code for uploading comments and such is too much of a mess to implement that system without breaking something else.
Or yeaGO likes the site being fragile (I kinda do, it makes the site feel less like a "business" and more like a personal place)
December 19, 2014 12:50 a.m.
omnipotato says... #6
It's not good practice to leave working html in comments. HTML 5 is pretty powerful and you can potentially do something to harm the site if all html tags are allowed. I suspect certain html tags are enabled and some are disabled, and for good reason. The best way, though, would be to disable all of them, but that would mean the programmers would have to implement image tags (and other styling tags) apart from html.
December 19, 2014 1:33 a.m.
omnipotato says... #7
HTML is also pretty weird for a programming language. It accepts all sorts of misspellings and tags being out of order or in the wrong place. Your browser is usually smart enough to detect there's HTML content outside of the < /html > tag.
December 19, 2014 1:35 a.m.
vampirelazarus says... #8
Personally, I found that the < code > tag was disabled or at least, it no longer works. Its very handy in explaining code and stuff to others, as it allows html tags, and displays them.......
Oh well.
December 19, 2014 1:49 a.m.
vampirelazarus says... #9
As for html, Im more of a software coding kinda person.
I mean, Ill learn html when Ive got no other CS classes to take, but for now, I'll stick to software :P
December 19, 2014 1:50 a.m.
omnipotato says... #10
Hey you're a coder too? What languages?
I'm kind of an all-rounder I do db, backend as well as front end stuff. Have to do it all because the company I work for only has like 3 programmers lol
December 19, 2014 2:03 a.m.
vampirelazarus says... #11
I'm still in school, but I spent the semester doing Python and C (focused mostly on inline Assembly).
Definitely prefer Python over C :P
December 19, 2014 2:28 a.m.
Blind_Guardian says... #12
It's true that Tappedout doesn't support all kind of elements and one thing which really works horrible is when you do something like this(didn't copy all code);
SCRIPT language=JavaScriptvar NS4 = (document.layers);
var IE4 = (document.all);var win = window;
var n = 0;function findInPage(str) var txt, i, found; if (str == "") return false; if (NS4) if (!win.find(str)) while(win.find(str, false, true)) n++; else n++; if (n == 0) alert("Not found."); if (IE4) txt = win.document.body.createTextRange(); for (i = 0; i <= n && (found = txt.findText(str)) != false; i++) txt.moveStart("character", 1); txt.moveEnd("textedit"); if (found) txt.moveStart("character", -1); txt.findText(str); txt.select(); txt.scrollIntoView(); n++; else if (n > 0) n = 0; findInPage(str); else alert("Sorry, we couldn't find.Try again"); return false;/SCRIPT
Since my computer is broke I can't acess Chromes html editor but I know that when using script tags and likewise it almost never ever works.
December 19, 2014 3:19 a.m.
Blizzicane says... #13
I remember doing C++, Javascript, Java, CSS, HTML, & Objective C a few years back but I can't remember anything but HTML and a little CSS now but I am on the track of programming once again this time starting with Python (which I just finish learning) and now going back into C++ which I remember disliking. XP
December 19, 2014 3:28 a.m.
Blind_Guardian says... #14
I just ask my brother for help since he is the one studying html, css, java, c++ and the rest. Hopefully he will be able to find a solution to the script tag problem.
December 19, 2014 3:35 a.m.
vampirelazarus says... #15
Script tags are disabled, due to the fragility of the site.
It's been mentioned once or twice.
December 19, 2014 3:39 a.m.
Script tags are disabled in comments not because the site is fragile but because its a horrible idea :P
I don't really think autoclosing is a good idea, but maybe a validation error when incorrect html is entered.
December 19, 2014 9:24 a.m.
Nigeltastic says... #17
I'm not sure anyone who is serious about coding would like to keep their project fragile, that just makes no sense to me... I've never heard a client say 'while you're making that for me please keep it so it can break easily'... Enabling script tags is an awful idea lol
vampirelazarus says... #2
So, I dont think its a great idea to play with < html > or < /html >.
It also doesnt work out so well.
Granted, I dont know anything really, about html, or if that website I tested on even works correctly.
December 19, 2014 12:20 a.m.