5 html mistakes

[auriaks]

Hi,
I faced these mistakes... can't solve them alone. Here is the link: http://validator.w3.org/check?uri=ww...Inline&group=0

[traq]

try changing

<div id="meniu">
	<form method='post' action='login.php'>

		Nick <input class="input" type='text' name='nick' size='10'><div></div>
		Code <input class="input" type='password' name='password' size='10'><div></div>
		<input class="sub" type='submit' name='enter' value='Enter'>
	</form>
</div>

to

<div id="meniu">
	<form method='post' action='login.php'>
		<p>
			Nick <input class="input" type='text' name='nick' size='10'><div></div>
			Code <input class="input" type='password' name='password' size='10'><div></div>
			<input class="sub" type='submit' name='enter' value='Enter'>
		</p>
	</form>
</div>

It's just telling you to put text and <inputs> in some sort of container (putting them directly in a <form> doesn't count)

[auriaks]

yea, it was part of an answer... Thanks

[traq]

Glad I could help. I thought you were checking your page as html5 before...? Did you actually intend to use 4.01?

[auriaks]

what do you mean "intend"? I was told to use it, like it was a great option

[traq]

no, it is a great option. I thought (I may be mistaken) that you were originally checking it as html5. There's no problem.

[djr33]

Perhaps the title "5 html mistakes"... if you read that quickly...

[traq]

hmm... maybe...

[jscheuer1]

I recently had a run in of sorts with one of the folks who helps maintain the standards for HTML 5. Things ended amicably enough. In the process I learned that in HTML 5, along with many enhanced features, quite a few of which aren't yet implemented in some and/or all browsers, that at least several, if not more, of the standards from HTML 4.01 and XHTML 1.0 strict and transitional have been relaxed. Just as an example, the type attribute is no longer required for style or script blocks as long as they are the defaults (text/css and text/javascript, respectively).

[djr33]

Interesting, John. HTML 5 makes me excited in some ways, but at the same time I feel like it's going to be a mess for years until browsers adopt it. Just like with XHTML, it may not be until HTML6 that HTML5 finally "Works" at which point we'll all be trying to use HTML6 anyway, just like now waiting for HTML5.

Is there any way that they're going to try to fix this cycle?


Auriaks, sorry for interrupting your thread, but I think all of your questions are answered. If not, let us know.