VK said:
Richard Lionheart wrote:
<!DOCTYPE html PUBLIC "-//W3C//DTD HTML 4.01//EN"
"
http://www.w3.org/TR/html4/strict.dtd">
Wrong DTD link: must be <
http://www.w3.org/TR/html401/strict.dtd>
because you are reffering HTML 4.01, not HTML 4.0
<html>
<head>
<title>An "HTML 4.01 Strict" compliant document</title>
<meta http-equiv="Content-Style-Type" content="text/css" >
This meta tag is useless as it was not implemented by any browser, it
is just mention in one of W3C recommendation. It is also harmless as it
may you think that now you can skip on type declaration in the the
<style> tag itself.
<meta http-equiv="content-type"
content="text/html;charset=ISO-8859-1" >
HTTP-EQUIV metas usually presented in the same sase as they would be
sent from server: "Content-Type", not "content-type".
<style type="text/javascript">
Pardon?
#red {color:red}
.blue {color:blue}
</style>
<script type="text/javascript">
function GenLines(o, n)
{
var aL = []; // Array of lines, sans newlines, which will
populate MyTextArea
// when concatenated with newline separators
if ((o = o.form) && (o = o.elements) && (o = o['MyTextArea']))
This is completely unnecessary
Unnecessary in this case yes, but not always. In the original post by the
OP in another thread, the name of the element was passed to 'o' with a
reference to another element in the form, therefore it was needed.
But here a reference to the required element is being passed so only a test
for existence of the element referenced by 'o' is required:
if (o){
and wrong besides that: you are using
It was 'right' for the original post: testing along the way to ensure the
required components are found.
assignment operator (=) instead of comparison operator (==). So you
The assignment operator is intended. If at any stage the assignment fails,
the 'undefined' result will be type converted to 'false' and the if block
is not executed. However, in this case the OP is going from the required
element, back to the form and down to the required element again.
So while it is redundant, it isn't 'wrong'.
just consecutively assigning the most fantastic values to poor "o". The
Not 'fantastic' values at all, but the ones intended.
last value your assign is undefined (because o['MyTextArea'] property
doesn't exist). Just remove it completely.
Initially, 'o' is assigned a reference to the element named 'MyTextArea'.
When entering the if statement, it is assigned the value of 'o.form', which
is the form. It is then assigned the value of 'o.elements', which is the
elements collection of the form. It is finally assigned the value of
'o['MyTextArea']', which exists (at least in the posted code).
It is equivalent to:
o = o.form.elements['MyTextArea'];
but since o is a reference to 'MyTextArea' to start with, it's redundant.
I would suggest keeping:
if(o){
[...]
