how to turn off meta-refresh ?

[dan baker]

I have a page that gets loaded with a meta-refresh hardcoded so that a
few things on the page get updated. its kind of a fake chat board.
anyway, what I need to do is turn off the meta-refresh once someone
clicks in a <textarea> to enter their input; otherwise the refresh
catches them in the middle and messes up the focus.

I need a way to turn off the meta-refresh, or to force the
cursor/focus to stay in the message input box once they click in it
and start typing.

I've tried:
<p class=small>Ent er your new message:
<br><textarea NAME=NewMsg rows=2 cols=60 wrap=virtual
onClick="window .location.reloa d(false);"></textarea>
<br><input TYPE=submit value="Post Your Message" >

but this actually forces a refresh onClick ?!

dan

[Richard Cornford]

"Thomas 'PointedEars' Lahn" <Po*********@we b.de> wrote in message
news:3F******** ******@PointedE ars.de...
<snip>

Grepping through the RFCs I have found no standard that
supports that, but that is not important at all. <snip>

It is important if you want to persuade other people to adopt a course
of action that they otherwise perceive to be completely arbitrary.

and your argument to date seems to hinge on stressing
the word "line" in "attributio n line".

No, re-read my answer(s). It hinges on the easy readability
of a posting/ thread which is a Good Thing. Header information
included in the attribution line that may be *someday* of use
for *someone* doesn't compensate for a more difficult following
of a discussion, mentally ignoring superfluous information when
reading *now*.

Personally I don't find that the number of carriage return/line feed
pairs in an attribution line has any impact on my ability to easily
comprehend news postings.

<snip.But can you name a user agent where the global object is _not_
`window' _and_ provides $globalObject.s etTimeout/clearTimeout?

I don't see the relevance of this. I have been questioning the worth of
referring to properties of the global object relative to a - window -
reference because that is unnecessary and must be fractionally slower. I
do not doubt that a property accessor syntax relative to a - window -
reference will be effective on JavaScript capable HTML web browses (at
least where setTimeout/Interval are concerned) but why do that when it
is unnecessary?

ACK, but `typeof' was implemented in JavaScript 1.1.

And fortunately JavaScript 1.0 environments are no longer in use.

How do you know for sure?

Nothing is known for sure, but if there were JavaScript 1.0 environments
in use this group is where I would expect to here about them. What I do
know with almost certainty is that anyone still using a JavaScript 1.0
web browser is not finding doing so a productive activity these days.

Richard.

[Thomas 'PointedEars' Lahn]

Jim Ley <ji*@jibbering. com> wrote with Forte Free Agent 1.11/32.235 in
comp.lang.javas cript on October 19, 2003 07:33 Central European Summer
Time about "Re: how to turn off meta-refresh ?" with the message-id
<3f************ ***@news.cis.df n.de> a followup to the posting with the
message-id <3F************ **@PointedEars. de> while the temperature outside
here was about 21.7°C, quite warm for the season and daytime (or was it the
infrared radiation from the heating?) the following 32 lines:

On Sun, 19 Oct 2003 14:36:45 +0200, Thomas 'PointedEars' Lahn
<Po*********@w eb.de> wrote:

Depends. As stated before, `window' and its properties are
part of the core JavaScript language up to version 1.3.
So that would be relevant to precisely one user agent?
(Netscape 4).

No, how do you get that idea?
Generally we try and talk about all ECMAScript implementations now
commonly known as javascript here, otherwise life would be really very
dull.

I really don't see the point.

JavaScript 1.3 is according to Netscapes Core JavaScript Reference
a fully compatible implementation of ECMAScript Ed. 1 and includes
host objects like `window' anyway.

I am using window.setTimeo ut(...) to set the timeout. Do the other
user agents you know where the global object is not `window' provide
$globalObject .setTimeout(... ) and $globalObject.c learTimeout(... )
with the same functionality? If not, this is merely of academical
interest.

Yep! They certainly do.

ACK
PointedEars

[Jim Ley]

On Sun, 19 Oct 2003 22:22:57 +0200, Thomas 'PointedEars' Lahn
<Po*********@we b.de> wrote:

Jim Ley <ji*@jibbering. com> wrote with Forte Free Agent 1.11/32.235 in

Depends. As stated before, `window' and its properties are
part of the core JavaScript language up to version 1.3.
So that would be relevant to precisely one user agent?
(Netscape 4).

No, how do you get that idea?

Because Netscape 4, is the only user agent that ever implemented
JavaScript 1.3 - Mozilla has JavaScript 1.5, IE has had various
JScript implementations , Konqueror and Safari have KJS
implementations , iCab and Opera have their own ECMAScript
implementations - sure we know they're all pretty similar to
JavaScript, but they are not JavaScript 1.3 (there's no watch for
example)
JavaScript 1.3 is according to Netscapes Core JavaScript Reference
a fully compatible implementation of ECMAScript Ed. 1 and includes
host objects like `window' anyway.

You're freely allowed to add objects to ECMAScript (it would be a
useless language if you didn't, but that doesn't make your extensions
part of the language.

Jim.
--
comp.lang.javas cript FAQ - http://jibbering.com/faq/

[Thomas 'PointedEars' Lahn]

Jim Ley wrote:

[...] Thomas 'PointedEars' Lahn [...] wrote:

Jim Ley <ji*@jibbering. com> wrote with Forte Free Agent 1.11/32.235 in

Depends. As stated before, `window' and its properties are
part of the core JavaScript language up to version 1.3.

So that would be relevant to precisely one user agent?
(Netscape 4).
No, how do you get that idea?

Because Netscape 4, is the only user agent that ever implemented
JavaScript 1.3 [...]

Read the Client-Side JavaScript (1.3) Reference[1] and you see that the
window object and most of its methods were implemented in JavaScript 1.0.
I wrote `*up to* version 1.3' for a reason. And that includes at least
Netscape Navigator 2.0 to 4.8.[2]

[1] http://devedge.netscape.com/library/...1.3/reference/
[2]
http://devedge.netscape.com/library/...e.html#1003267

JavaScript 1.3 is according to Netscapes Core JavaScript Reference
a fully compatible implementation of ECMAScript Ed. 1 and includes
host objects like `window' anyway.

You're freely allowed to add objects to ECMAScript

I know.
[...], but that doesn't make your extensions part of the language.

Not part of ECMAScript, but part of JavaScript which Netscape has done.
See the difference?
PointedEars

[Jim Ley]

On Sun, 19 Oct 2003 23:29:11 +0200, Thomas 'PointedEars' Lahn
<Po*********@we b.de> wrote:

Jim Ley wrote:

[...] Thomas 'PointedEars' Lahn [...] wrote:

Jim Ley <ji*@jibbering. com> wrote with Forte Free Agent 1.11/32.235 in
>Depends. As stated before, `window' and its properties are
>part of the core JavaScript language up to version 1.3.

So that would be relevant to precisely one user agent?
(Netscape 4).

No, how do you get that idea?

Because Netscape 4, is the only user agent that ever implemented
JavaScript 1.3 [...]

Read the Client-Side JavaScript (1.3) Reference[1] and you see that the
window object and most of its methods were implemented in JavaScript 1.0.
I wrote `*up to* version 1.3' for a reason. And that includes at least
Netscape Navigator 2.0 to 4.8.[2]

Oh right, okay, NN 2-4.8, still completely irrelevant to 99% of the
questions on this groups and certainly not relevant to the start of
this thread where you were mentioning IE and "recent UA's" - you
didn't mention << NN4 then - I also don't agree that the
documentation your citing actually supports your case, the
documentation being for "javascript language and its objects", but
even if it does (and it's debateable) it's not particularly relevant.

Jim.
--
comp.lang.javas cript FAQ - http://jibbering.com/faq/

[Dr John Stockton]

JRS: In article <3F************ **@PointedEars. de>, seen in
news:comp.lang. javascript, Thomas 'PointedEars' Lahn
<Po*********@we b.de> posted at Sun, 19 Oct 2003 18:45:39 :-

Jim Ley wrote:

On Sun, 19 Oct 2003 14:36:45 +0200, Thomas 'PointedEars' Lahn
<Po*********@we b.de> wrote:

Please shorten this to one line, thanks.

The size of an attribution is at the discretion of the poster; AIUI, you
can cite no authority that states otherwise.

Desist.

--
© John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v4.00 MIME ©
Web <URL:http://www.uwasa.fi/~ts/http/tsfaq.html> -> Timo Salmi: Usenet Q&A.
Web <URL:http://www.merlyn.demo n.co.uk/news-use.htm> : about usage of News.
No Encoding. Quotes before replies. Snip well. Write clearly. Don't Mail News.

[Dr John Stockton]

JRS: In article <3F************ **@PointedEars. de>, seen in
news:comp.lang. javascript, Thomas 'PointedEars' Lahn
<Po*********@we b.de> posted at Sun, 19 Oct 2003 08:02:48 :-

Dr John Stockton wrote:

[...]
Evidently you do not understand the full variety of circumstances under
which someone who has a copy of an article can make use of an
informative attribution. Be aware, for example, that someone who has
saved a copy of an article which *quotes* an attribution line has not
saved the header of the attributing article.
Evidently you do not understand what headers are and what their function
is. Most news clients are saving headers with articles (see the .eml format
for example) and one can include the information *when* *required*.

The information in an attribution is not contained in the header of the
article containing the attribution; it is extracted from the header of
the article being replied to. The attribution adds to the information
content of the article containing it. When an article is saved for
longer than one's news client normally saves articles, it is probable
that, when later reading the saved article, its predecessor will not be
locally available.

Evidently you do not know of news archives like Google Groups,
where one can (in most cases) re-read whole discussions when a
single message ID or even a keyword has been provided.
News is a medium suited to off-line use; the Web, and GG in particular,
is not. I would not, of course, support re-posting in News of large
quantities of material that can be recovered from the Web; but the
modest amount that many of us include can be useful to those reading the
article in News, or reading a stored copy.

And evidently you do not even think about paying respect to core Internet
and Usenet standards, namely not using a valid e-mail address (as stated
by RFCs 1036 and 2822), not having installed the `postmaster' account for
your(?) sub-level domain (as stated by RFC 1173), and not obeying the core
rules of Netiquette (RFC 1855), so I do not see the point of discussing
the justification of (my) statements by those standards with you.

You continue with your false assumptions. You do not understand what
has occurred in this case.

--
© John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v4.00 MIME ©
Web <URL:http://www.uwasa.fi/~ts/http/tsfaq.html> -> Timo Salmi: Usenet Q&A.
Web <URL:http://www.merlyn.demo n.co.uk/news-use.htm> : about usage of News.
No Encoding. Quotes before replies. Snip well. Write clearly. Don't Mail News.

[Thomas 'PointedEars' Lahn]

Dr John Stockton wrote:

[...] Thomas 'PointedEars' Lahn [wrote:]

Evidently you do not understand what headers are and what their function
is. Most news clients are saving headers with articles (see the .eml format
for example) and one can include the information *when* *required*.
The information in an attribution is not contained in the header of the
article containing the attribution; it is extracted from the header of
the article being replied to.

I get the idea that you really think that this information was new to me.
The attribution adds to the information content of the article containing
it. When an article is saved for longer than one's news client normally
saves articles, it is probable that, when later reading the saved article,
its predecessor will not be locally available.
You may want to explain why it is then necessary to know when
the unavailable article was posted and in which newsgroup ...

Evidently you do not know of news archives like Google Groups,
where one can (in most cases) re-read whole discussions when a
single message ID or even a keyword has been provided.

News is a medium suited to off-line use; the Web, and GG in particular,
is not.

.... if you do not accept even the Web/Google Groups as an
appropriate medium of investigation.
I would not, of course, support re-posting in News of large
quantities of material that can be recovered from the Web;
Non sequitur. I don't recommend people to act as a Human gateway either.
but the modest amount
Since replies can contain down to only one line of new information,
IMHO three lines of meta information is not a modest amount.
that many of us include can be useful
to those reading the article in News, or reading a stored copy.

You oppose yourself. If one maintains a local news archive, they would
use most certainly a software that can follow references. And if the
article expires, its posting date is barely of interest any longer.

If one doesn't maintain such an archive, they would have access to the
Internet/Usenet and can access the thread for the stored posting somehow,
in the unlikely case that this is required. If they don't have immediate
access, they would have saved the whole thread in the first place.

And evidently you do not even think about paying respect to core Internet
and Usenet standards, namely not using a valid e-mail address (as stated
by RFCs 1036 and 2822), not having installed the `postmaster' account for
your(?) sub-level domain (as stated by RFC 1173), and not obeying the core
rules of Netiquette (RFC 1855), so I do not see the point of discussing
the justification of (my) statements by those standards with you.

You continue with your false assumptions. You do not understand what
has occurred in this case.

Then why don't you enlighten me and explain what has occured in this case?
So far I only got a bounce when sending you e-mail using the substring you
used in the `From:' header as e-mail address, and I must therefore conclude
that it is no e-mail address. So far I got a bounce when addressing the
`postmaster' account for the domain part of that substring and I must
therefore conclude that either the host is misconfigured or that this domain
cannot receive e-mail at all.
PointedEars

[Dr John Stockton]

JRS: In article <3F************ **@PointedEars. de>, seen in
news:comp.lang. javascript, Thomas 'PointedEars' Lahn
<Po*********@we b.de> posted at Sat, 25 Oct 2003 20:43:21 :-

You continue with your false assumptions. You do not understand what
has occurred in this case.
Then why don't you enlighten me and explain what has occured in this case?
So far I only got a bounce when sending you e-mail using the substring you
used in the `From:' header as e-mail address, and I must therefore conclude
that it is no e-mail address. So far I got a bounce when addressing the
`postmaster' account for the domain part of that substring

That is, so far, in accordance with my expectations.
and I must
therefore conclude that either the host is misconfigured or that this domain
cannot receive e-mail at all.

That is, however, a false deduction.

--
© John Stockton, Surrey, UK. ?@merlyn.demon. co.uk Turnpike v4.00 MIME ©
Web <URL:http://www.uwasa.fi/~ts/http/tsfaq.html> -> Timo Salmi: Usenet Q&A.
Web <URL:http://www.merlyn.demo n.co.uk/news-use.htm> : about usage of News.
No Encoding. Quotes before replies. Snip well. Write clearly. Don't Mail News.

[Lasse Reichstein Nielsen]

Dr John Stockton <sp**@merlyn.de mon.co.uk> writes:

[postmaster account bounced]

and I must
therefore conclude that either the host is misconfigured or that this domain
cannot receive e-mail at all.

That is, however, a false deduction.

An SMTP server with no postmaster account is misconfigured. Even if it is
deliberate. :)

/L
--
Lasse Reichstein Nielsen - lr*@hotpop.com
DHTML Death Colors: <URL:http://www.infimum.dk/HTML/rasterTriangleD OM.html>
'Faith without judgement merely degrades the spirit divine.'