Lee said:
Thomas 'PointedEars' Lahn said:
Lee said:
DU said:
Lee wrote:
[...] <a href="
http://www.google.com" target="extern"
onclick="window.open(this.href,'extern').focus();return
false">an
I don't agree with DU's other statements, however:
Calling a method for an object, whose reference is returned by
another method, without checking if the reference is valid and
without checking if the object returned has the former method, is
error-prone.
Only if it's possible for the method to fail to return a valid
object.
No. From JavaScript version 1.5 on, "window" is removed from the core
language and becomes a host object. As client-side host objects are
part of the UA's DOM and those DOMs are different (although there are
some mutualities called "DOM Level 0"), their methods are different.
I don't believe that can happen in this case.
What you believe is irrelevant. What specs and references say is
relevant. window.open() returns a reference to a Window object if
successful, `null' or at least not a Window object otherwise:
<
http://devedge.netscape.com/library/manuals/2000/javascript/1.3/reference/window.html#1202731>
Besides, both of you violate Internet standards (namely RFCs 1036
and 2822) by using non-existing "From:" addresses [...]
There's nothing wrong with my From address, [...]
IBTD!
| The "From" line contains the electronic mailing address of the
| person who sent the message, in the Internet syntax. [...]
(RFC 1036 "Standard for interchange of USENET messages", section 2.1.1)
| A mailbox receives mail. [...]
(RFC 2822 "Internet Message Format", section 3.4.)
| - Forging of news articles is generally censured. [...]
(RFC 1855 "Netiquette Guidelines", section 3.1.3)
| The standards upon which Usenet is built, that is, the specification
| for the system's operation, requires that the poster use a legitimate
| email address. Making exceptions to standards simply for short-term
| convenience is unwise at best. At worst, it jeopardizes the Internet's
| long-term viability to continue the same level of utility that it has
| enjoyed.
|
| Allowing standards to be broken is contradictory to the philosophy
| behind the Internet [...]
(<
http://www.interhack.net/pubs/munging-harmful/>)
| From: Lee <
[email protected]>
(<
[email protected]>)
$ host -t mx cox.net
cox.net MX 100 mx.east.cox.net
cox.net MX 100 mx.west.cox.net
$ telnet mx.east.cox.net smtp
Trying 68.1.17.3...
Connected to mx.east.cox.net.
Escape character is '^]'.
220 lakermmtai17.cox.net ESMTP server (InterMail vM.6.01.03.02
201-2131-111-104-20040324) ready Tue, 15 Jun 2004 14:54:42 -0400
mail from:<
[email protected]>
250 Sender <
[email protected]> Ok
rcpt to:<
[email protected]>
550 Invalid recipient: <
[email protected]>
quit
221 lakermmtai17.cox.net ESMTP server closing connection
Connection closed by foreign host.
$ telnet mx.west.cox.net smtp
Trying 68.6.19.3...
Connected to mx.west.cox.net.
Escape character is '^]'.
220 fed1rmmtai19.cox.net ESMTP server (InterMail vM.6.01.03.02
201-2131-111-104-20040324) ready Tue, 15 Jun 2004 14:55:38 -0400
mail from:<
[email protected]>
250 Sender <
[email protected]> Ok
rcpt to:<
[email protected]>
550 Invalid recipient: <
[email protected]>
quit
221 fed1rmmtai19.cox.net ESMTP server closing connection
Connection closed by foreign host.
| *Acceptable Use Policy*
| Updated 2/4/04
|
| 14. *Newsgroups.* [...]
| *Forging, altering or removing header information is prohibited.*
| [...]
| *Cox reserves the right to discontinue access to any Usenet newsgroup
| at any time for any reason.*
| [...]
| *How to Contact Cox.* For any questions regarding this AUP, complaints
| of violations, or cancellation notices, please contact Cox at one of
| the following:
|
| E-mail: (e-mail address removed)
| [...]
(<
http://www.cox.com/policy/#aup_14>)
There is *anything* wrong with your From "address".
PointedEars
Xref: uni-berlin.de comp.lang.javascript:446174
Thomas 'PointedEars' Lahn said:
Lee said:
DU said:
Lee wrote:
[...] <a href="
http://www.google.com" target="extern"
onclick="window.open(this.href,'extern').focus();return
false">an
I don't agree with DU's other statements, however:
Calling a method for an object, whose reference is returned by
another method, without checking if the reference is valid and
without checking if the object returned has the former method, is
error-prone.
Only if it's possible for the method to fail to return a valid
object.
No. From JavaScript version 1.5 on, "window" is removed from the core
language and becomes a host object. As client-side host objects are
part of the UA's DOM and those DOMs are different (although there are
some mutualities called "DOM Level 0"), their methods are different.
Since JScript never contained
I don't believe that can happen in this case.
What you believe is irrelevant. What specs and references say is
relevant. window.open() returns a reference to a Window object if
successful, `null' or at least not a Window object otherwise:
<
http://devedge.netscape.com/library/manuals/2000/javascript/1.3/reference/window.html#1202731>
Besides, both of you violate Internet standards (namely RFCs 1036
and 2822) by using non-existing "From:" addresses [...]
There's nothing wrong with my From address, [...]
IBTD!
| The "From" line contains the electronic mailing address of the
| person who sent the message, in the Internet syntax. [...]
(RFC 1036 "Standard for interchange of USENET messages", section 2.1.1)
| A mailbox receives mail. [...]
(RFC 2822 "Internet Message Format", section 3.4.)
| - Forging of news articles is generally censured. [...]
(RFC 1855 "Netiquette Guidelines", section 3.1.3)
| The standards upon which Usenet is built, that is, the specification
| for the system's operation, requires that the poster use a legitimate
| email address. Making exceptions to standards simply for short-term
| convenience is unwise at best. At worst, it jeopardizes the Internet's
| long-term viability to continue the same level of utility that it has
| enjoyed.
|
| Allowing standards to be broken is contradictory to the philosophy
| behind the Internet [...]
(<
http://www.interhack.net/pubs/munging-harmful/>)
| From: Lee <
[email protected]>
(<
[email protected]>)
$ host -t mx cox.net
cox.net MX 100 mx.east.cox.net
cox.net MX 100 mx.west.cox.net
$ telnet mx.east.cox.net smtp
Trying 68.1.17.3...
Connected to mx.east.cox.net.
Escape character is '^]'.
220 lakermmtai17.cox.net ESMTP server (InterMail vM.6.01.03.02
201-2131-111-104-20040324) ready Tue, 15 Jun 2004 14:54:42 -0400
mail from:<
[email protected]>
250 Sender <
[email protected]> Ok
rcpt to:<
[email protected]>
550 Invalid recipient: <
[email protected]>
quit
221 lakermmtai17.cox.net ESMTP server closing connection
Connection closed by foreign host.
$ telnet mx.west.cox.net smtp
Trying 68.6.19.3...
Connected to mx.west.cox.net.
Escape character is '^]'.
220 fed1rmmtai19.cox.net ESMTP server (InterMail vM.6.01.03.02
201-2131-111-104-20040324) ready Tue, 15 Jun 2004 14:55:38 -0400
mail from:<
[email protected]>
250 Sender <
[email protected]> Ok
rcpt to:<
[email protected]>
550 Invalid recipient: <
[email protected]>
quit
221 fed1rmmtai19.cox.net ESMTP server closing connection
Connection closed by foreign host.
| *Acceptable Use Policy*
| Updated 2/4/04
|
| 14. *Newsgroups.* [...]
| *Forging, altering or removing header information is prohibited.*
| [...]
| *Cox reserves the right to discontinue access to any Usenet newsgroup
| at any time for any reason.*
| [...]
| *How to Contact Cox.* For any questions regarding this AUP, complaints
| of violations, or cancellation notices, please contact Cox at one of
| the following:
|
| E-mail: (e-mail address removed)
| [...]
(<
http://www.cox.com/policy/#aup_14>)
There is *anything* wrong with your From "address".
PointedEars