469,602 Members | 1,912 Online
Bytes | Developer Community
New Post

Home Posts Topics Members FAQ

Post your question to a community of 469,602 developers. It's quick & easy.

Form not terminating on FireFox

Hi,

I have some code I just cannot seem to get to work properly on FireFox. It
is probably something simple.

On FireFox the following code does not seem to terminate in the browser, but
it works fine on IE :-

http://angray.members.beeb.net/Test/Test5.html

Thanks in advance,

Aaron
Nov 23 '05 #1
35 1828
Aaron Gray wrote:
http://angray.members.beeb.net/Test/Test5.htm


<http://validator.w3.org/check?uri=http%3A%2F%2Fangray.members.beeb.net%2FT est%2FTest5.html&ss=1;verbose=1>
HTH

PointedEars
Nov 23 '05 #2
> I have some code I just cannot seem to get to work properly on FireFox. It
is probably something simple.

On FireFox the following code does not seem to terminate in the browser,
but it works fine on IE :-

http://angray.members.beeb.net/Test/Test5.html


Sorry the JavaScripts stopped working on IE. Works on FireFox but FireFox is
not terminating still.

Aaron
Nov 23 '05 #3
VK

Aaron Gray wrote:
Sorry the JavaScripts stopped working on IE. Works on FireFox but FireFox is
not terminating still.


Your code contains a conglomerate of HTML and JavaScript error :-(
As usual IE is the most durt tolerant browser on the market :-)

Here is the more proper version. A cannot comment on each change mage,
try to guess yourselve, ask only if no way.

<html>
<head>
<title>Frame test</title>
<script type="text/javascript">
function go()
{
var doc = self.frames['output'].document;
doc.open("text/html");
doc.writeln("<font face='Arial'>");
doc.writeln("Test");
document.forms['result'].elements['txt01'].value = 10;
doc.writeln("</font>");
doc.close();
}
</script>
</head>

<body onload="go()">

<h2>Frame test</h2><br>
<br>

<iframe name="output" width="100%" height="50%"></iframe>

<br>

<FORM name="result">
<label for="txt01">Result:</label>
<input type="text" name="txt01" value="">
</FORM>

</body>
</html>

Nov 23 '05 #4
>> http://angray.members.beeb.net/Test/Test5.htm

<http://validator.w3.org/check?uri=http%3A%2F%2Fangray.members.beeb.net%2FT est%2FTest5.html&ss=1;verbose=1>


Food for trolls :-)

http://validator.w3.org/check?uri=ht...ss=1&verbose=1

Eat that !

Aaron
Nov 23 '05 #5
Aaron Gray wrote:

Food for trolls :-)
http://validator.w3.org/check?uri=ht...ss=1&verbose=1
Eat that !


Google aren't asking for free help in solving problems with their code. If
they want to ignore useful, but trivial to implement, QA then that is there
choice and we can roll our eyes at them. On the other hand, if you want a
bunch of complete strangers to help you, then you can show a little respect
by fixing problems that well known and free software can detect for you
before asking your questions.

--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is
Nov 23 '05 #6
> Your code contains a conglomerate of HTML and JavaScript error :-(

Ah <script> sections in <head>
var doc = self.frames['output'].document;
doc.open("text/html"); ... doc.close();


doc.open and doc.close seem to be the real solution !

Thanks,

Aaron
Nov 23 '05 #7
Aaron Gray said the following on 11/13/2005 11:56 AM:
Hi,

I have some code I just cannot seem to get to work properly on FireFox. It
is probably something simple.

On FireFox the following code does not seem to terminate in the browser, but
it works fine on IE :-

http://angray.members.beeb.net/Test/Test5.html


Check the JS Console. It gives this error message in Firefox:

Warning: Element referenced by ID/NAME in the global scope. Use W3C
standard document.getElementById() instead.
Source File: http://angray.members.beeb.net/Test/Test5.html
Line: 30

Your code:

<FORM name=input onsubmit="return false;" action="">

You may want to rename your form to something less likely to cause a
problem. input is not a reserved word but less likely to cause confusion
if you name it something like myInputForm or myForm.

Your code:

<FORM name=result onsubmit="return false;" action="">
<INPUT type="Text" size=75 name="result">
</FORM>

Your form and your input have the same name. What does result refer to?
The form or the input? Name them differently.
Your code:

<script type="text/javascript">

function go()
{
output.document.body.innerHTML="";
output.document.writeln( "<font face='Arial'>");
output.document.writeln( "Test");
result.result.value = "10";
output.document.writeln( "</font>");
Here, you reference output as a global variable but it is not defined
anywhere. That is the cause of the Firefox error but in this case
Firefox's error message is actually incorrect. Do not use gEBI to access
form elements, use the form collection. Use the frames collection to
access IFrames.

Give this version a try:

<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN"
"http://www.w3.org/TR/html4/strict.dtd">
<html>
<head>
<meta http-equiv="content-type" content="text/html; charset=UTF-8">
<title>Frame test</title>
<script type="text/javascript">
function go()
{
window.frames['output'].document.open();
window.frames['output'].document.writeln( "<font face='Arial'>");
window.frames['output'].document.writeln( "Test");
document.forms['myResult'].elements['myResult2'].value = "10";
window.frames['output'].document.writeln( "<\/font>");
window.frames['output'].document.close();
}

</script>
</head>
<body>
<h2>Frame test</h2>
<p>
<FORM name="myResult" onsubmit="return false;" action="">
<div>
<INPUT onclick="go()" type="button" value="Go">
<INPUT type="Text" size=75 name="myResult2">
</div>
</FORM>
<iframe name="output" style="width:100%;height:25%"></iframe>
</body>
</html>
Compare the two versions and see if you can tell the difference.
I left your font tags in, even though I don't care for the font tag and
it is irrelevant to your question.

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Nov 23 '05 #8
>> Food for trolls :-)

http://validator.w3.org/check?uri=ht...ss=1&verbose=1

Eat that !


Google aren't asking for free help in solving problems with their code. If
they want to ignore useful, but trivial to implement, QA then that is
there
choice and we can roll our eyes at them. On the other hand, if you want a
bunch of complete strangers to help you, then you can show a little
respect
by fixing problems that well known and free software can detect for you
before asking your questions.


I normally use HTML validation as the last part of the process. But like
Google I ignore it most of the time as it does not really seem to be very
helpful most of the time, just a pain in the backside :(

Aaron
Nov 23 '05 #9
Aaron Gray said the following on 11/13/2005 1:05 PM:
Your code contains a conglomerate of HTML and JavaScript error :-(

Ah <script> sections in <head>
var doc = self.frames['output'].document;
doc.open("text/html");


...
doc.close();

doc.open and doc.close seem to be the real solution !


open() and close() were not the only problems though.

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Nov 23 '05 #10
VK wrote:
<html>
The DOCTYPE declaration is missing.
<head>
The character set declaration via `meta' element is missing.
<title>Frame test</title>
<script type="text/javascript">
It should be noted that due to review of the now Informational RFC
"Scripting Media Types" in the IETF, the text/javascript MIME type
has been registered in the standards tree to be obsoleted by the
also registered MIME type application/javascript.

<http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg01349.html>
<http://www.iana.org/assignments/media-types/>
function go()
{
var doc = self.frames['output'].document;
doc.open("text/html");
The argument of document.open() is bogus, it will not be interpreted in
a UA standards compliant in this regard, including all Gecko-based UAs.
Instead, the Content-Type of the resulting document will be always
text/html.
doc.writeln("<font face='Arial'>");
doc.writeln("Test");
document.forms['result'].elements['txt01'].value = 10;
doc.writeln("</font>");
Deprecated usage of the `font' element aside, this is not Valid HTML as
ETAGO delimiters are not properly escaped. The above line should read

doc.writeln("<\/font>");

More important is that the resulting document is not a Valid HTML
document as the context in which the `font' element is allowed
is not generated as well.
[...]
<body onload="go()">

<h2>Frame test</h2><br>
This should be an `h1' element. As all `hX' elements are block elements,
the adjacend `br' element is neither necessary nor prudent.
<br>
Use CSS to format margins, not `br' elements.
<iframe name="output" width="100%" height="50%"></iframe>
This element is missing alternative content to be displayed if the
`iframe' element is not supported or "output" cannot be displayed.
<br>
See above.
<FORM name="result">
<label for="txt01">Result:</label>
<input type="text" name="txt01" value="">


The `label' element is not supposed to work as perhaps expected by
the poster. The value of the `for' attribute has to be an ID.
PointedEars
Nov 23 '05 #11
Aaron Gray wrote:

vvvvvvvvvvvvvvvvvv <http://jibbering.com/faq/faq_notes/pots1.html>
http://angray.members.beeb.net/Test/Test5.htm

<http://validator.w3.org/check?uri=http%3A%2F%2Fangray.members.beeb.net%2FT est%2FTest5.html&ss=1;verbose=1>
Food for trolls :-)


You admit that you are trolling?

<http://diveintomark.org/archives/2003/05/05/why_we_wont_help_you>
PointedEars, Score adjusted
Nov 23 '05 #12
Thomas 'PointedEars' Lahn said the following on 11/13/2005 1:23 PM:
VK wrote:
<html> The DOCTYPE declaration is missing.


Off-topic and irrelevant to this thread.
<head> The character set declaration via `meta' element is missing.


Off-topic and irrelevant to this thread.

But, the character set is not required so it is missing if of no
consequence. What matters is if the server sends it correctly in a
web-based environment which is the default assumption in this group.
<title>Frame test</title>
<script type="text/javascript">


It should be noted that due to review of the now Informational RFC
"Scripting Media Types" in the IETF, the text/javascript MIME type
has been registered in the standards tree to be obsoleted by the
also registered MIME type application/javascript.
<http://www1.ietf.org/mail-archive/web/ietf-announce/current/msg01349.html>
<http://www.iana.org/assignments/media-types/>


Irrelevant to this thread.
function go()
{
var doc = self.frames['output'].document;
doc.open("text/html");


The argument of document.open() is bogus, it will not be interpreted in
a UA standards compliant in this regard, including all Gecko-based UAs.
Instead, the Content-Type of the resulting document will be always
text/html.


Still irrelevant to the problem.
doc.writeln("<font face='Arial'>");
doc.writeln("Test");
document.forms['result'].elements['txt01'].value = 10;
doc.writeln("</font>");
Deprecated usage of the `font' element aside, this is not Valid HTML as
ETAGO delimiters are not properly escaped. The above line should read

doc.writeln("<\/font>");


Off-topic and irrelevant to this thread.
More important is that the resulting document is not a Valid HTML
document as the context in which the `font' element is allowed
is not generated as well.
Off-topic and irrelevant to this thread.
[...]
<body onload="go()">

<h2>Frame test</h2><br> This should be an `h1' element. As all `hX' elements are block elements,
the adjacend `br' element is neither necessary nor prudent.


Off-topic and irrelevant to this thread.
<br>

Use CSS to format margins, not `br' elements.


Off-topic and irrelevant to this thread.
<iframe name="output" width="100%" height="50%"></iframe>

This element is missing alternative content to be displayed if the
`iframe' element is not supported or "output" cannot be displayed.


Off-topic and irrelevant to this thread.
<br>

See above.


Off-topic and irrelevant to this thread.
<FORM name="result">
<label for="txt01">Result:</label>
<input type="text" name="txt01" value="">

The `label' element is not supposed to work as perhaps expected by
the poster. The value of the `for' attribute has to be an ID.


Off-topic and irrelevant to this thread.
If there is nothing you can add that is even remotely relevant to the
thread and the problem then please STFU and SIYC.

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Nov 23 '05 #13
Thomas 'PointedEars' Lahn said the following on 11/13/2005 1:26 PM:
Aaron Gray wrote:

vvvvvvvvvvvvvvvvvv <http://jibbering.com/faq/faq_notes/pots1.html>
http://angray.members.beeb.net/Test/Test5.htm
<http://validator.w3.org/check?uri=http%3A%2F%2Fangray.members.beeb.net%2FT est%2FTest5.html&ss=1;verbose=1>
Food for trolls :-)

You admit that you are trolling?


He said nothing of the sort. You purported that the reason his script
wasn't working was invalid HTML which is a stupid idea. Had you tested
and found the solution, you would know that.
<http://diveintomark.org/archives/2003/05/05/why_we_wont_help_you>


STFU and SIYC Thomas. Stick to things you know, this isn't one of them.

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Nov 23 '05 #14
VK

Aaron Gray wrote:
open and doc.close seem to be the real solution !


Not really. As I said it was a complex agglomeration of wrong technics,
and open() / close() may just happened to be the last drop.
Usially you can skip on open() / close() methods: inputStream get open
and closed automatically. It is not formally correct but tolerated by
majority browsers (including Firefox).

Nov 23 '05 #15
VK said the following on 11/13/2005 2:01 PM:
Aaron Gray wrote:
open and doc.close seem to be the real solution !

Not really. As I said it was a complex agglomeration of wrong technics,
and open() / close() may just happened to be the last drop.
Usially you can skip on open() / close() methods: inputStream get open
and closed automatically. It is not formally correct but tolerated by
majority browsers (including Firefox).


No, they do not get closed automatically. Comment out the close() line
in Firefox and test it. Firefox does not automatically close it and
displays the behavior the OP was complaining about. IE auto closes it.

And that behavior (auto closing) shouldn't be surprising in a "Do what
you think I want, not what I tell you to do" browser.
--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Nov 23 '05 #16
VK
> No, they do not get closed automatically. Comment out the close() line
in Firefox and test it. Firefox does not automatically close it and
displays the behavior the OP was complaining about. IE auto closes it.


Oh... Things changed then. I personally did not use document.write()
since NN 4.x (for layer updates) and it did not require close() though
I always used it.

That's indeed a bit of hypercorrectness syndrom (one of youthhood
problems ? :-)

Nov 23 '05 #17
VK wrote:
No, they do not get closed automatically. Comment out the
close() line in Firefox and test it. Firefox does not
automatically close it and displays the behavior the OP was
complaining about. IE auto closes it.


Oh... Things changed then. I personally did not use document.write()
since NN 4.x (for layer updates) and it did not require close() though
I always used it.

<snip>

So once again you don't let know knowing what you are talking about
stand in the way of your pontificating on the subject? It is actually
well known that many browsers do not automatically close documents
following a write operation, it is even clearly expressed in the W3C
HTML DOM standard that automatic document closing should not be expected
(while opening on a write operations is required).

Richard.
Nov 23 '05 #18
Aaron Gray wrote:
Your code contains a conglomerate of HTML and JavaScript error :-(


Ah <script> sections in <head>
var doc = self.frames['output'].document;
doc.open("text/html");


the open() method does not take any arguments:

open
Note. This method and the ones following allow a user to add to or
replace the structure model of a document using strings of unparsed
HTML. At the time of writing alternate methods for providing similar
functionality for both HTML and XML documents were being considered.
The following methods may be deprecated at some point in the future
in favor of a more general-purpose mechanism.

Open a document stream for writing. If a document exists in the
target, this method clears it.
No Parameters
No Return Value
No Exceptions

<URL:http://www.w3.org/TR/2000/WD-DOM-Level-2-HTML-20001113/html.html#ID-72161170>
A useful guide to the use of document.write(), open() and close is here:

<URL:http://developer.mozilla.org/en/docs/DOM:document>

A call to either write or writeln methods after the document has loaded
will automatically call the open method and clear the document.

[...]

--
Rob
Nov 23 '05 #19
RobG wrote:
Aaron Gray wrote:
Your code contains a conglomerate of HTML and JavaScript error :-(


Ah <script> sections in <head>
var doc = self.frames['output'].document;
doc.open("text/html");


the open() method does not take any arguments:
[...]

<URL:http://www.w3.org/TR/2000/WD-DOM-Level-2-HTML-20001113/html.html#ID-72161170>

The statement is correct, however the reference is outdated. You are
inappropriately and needlessly referring to a Working Draft (WD) where
a Recommendation (REC), and, as such, a Specification and Web Standard
has been published long ago.

<http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-72161170>

(See also <news:18****************@PointedEars.de> where I already
explained this.)
PointedEars
Nov 23 '05 #20
Thomas 'PointedEars' Lahn said the following on 11/14/2005 5:14 AM:
RobG wrote:

Aaron Gray wrote:
Your code contains a conglomerate of HTML and JavaScript error :-(

Ah <script> sections in <head>

var doc = self.frames['output'].document;
doc.open("text/html");
the open() method does not take any arguments:
[...]


<URL:http://www.w3.org/TR/2000/WD-DOM-Level-2-HTML-20001113/html.html#ID-72161170>

The statement is correct, however the reference is outdated. You are
inappropriately and needlessly referring to a Working Draft (WD) where
a Recommendation (REC), and, as such, a Specification and Web Standard
has been published long ago.


Irrelevant to this thread.
<http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-72161170>

(See also <news:18****************@PointedEars.de> where I already
explained this.)


Please give references that anybody has access to.

--
Randy
comp.lang.javascript FAQ - http://jibbering.com/faq & newsgroup weekly
Javascript Best Practices - http://www.JavascriptToolbox.com/bestpractices/
Nov 23 '05 #21
Thomas 'PointedEars' Lahn wrote:
RobG wrote:

<URL:http://www.w3.org/TR/2000/WD-DOM-Level-2-HTML-20001113/html.html#ID-72161170>

... You are
inappropriately and needlessly referring to a Working Draft (WD) where
a Recommendation (REC), and, as such, a Specification and Web Standard
has been published long ago.

<http://www.w3.org/TR/DOM-Level-2-HTML/html.html#ID-72161170>

(See also <news:18****************@PointedEars.de> where I already
explained this.)


Nothing happens when clicking on this link (using Thunderbird).
I followed the W3 links and automatically was directed to
http://www.w3.org/TR/2003/REC-DOM-Le...HTML-20030109/
which is
http://www.w3.org/TR/DOM-Level-2-HTML/
So I was curious what can be explained about it.
Nov 23 '05 #22
VK
Do not take <Thomas 'PointedEars' Lahn> too close to your heart. He's
one of numerous people in this group who managed to learn the basics of
the Books of the Cannon, and really believed what an appropriate
quotation from the book may solve anyone's problem. It is not true, but
the full reveal of this truth may hurt endlessly - so we just skip on
it.

Nov 23 '05 #23
Randy Webb wrote:
The statement is correct, however the reference is outdated.
Irrelevant to this thread.


This is Usenet. Discussions evolve, and drifting to tangential topics is
perfectly normal.
(See also <news:18****************@PointedEars.de>

Please give references that anybody has access to.


Everybody does have access to that resource. If it happens to have expired
on your newserver (or if your news client isn't good enough to look up a
post by its message id), then you can pop it into Google Groups and
retrieve it that way.

--
David Dorward <http://blog.dorward.me.uk/> <http://dorward.me.uk/>
Home is where the ~/.bashrc is
Nov 23 '05 #24
VK wrote:
Do not take <Thomas 'PointedEars' Lahn> too close to your heart. He's
one of numerous people in this group who managed to learn the basics of
the Books of the Cannon, and really believed what an appropriate
quotation from the book may solve anyone's problem. It is not true, but
the full reveal of this truth may hurt endlessly - so we just skip on
it.


What are you babbling about? The very text of the reference used by
_Rob_ states that it is inappropriate to cite it as reference material:

| This is a W3C Working Draft for review by W3C members and other interested
| parties. It is a draft document and may be updated, replaced or obsoleted
| by other documents at any time. It is inappropriate to use W3C Working
| Drafts as reference material or to cite them as other than "work in
| progress".

This does not invalidate _Rob's_ argument (which you obviously not
noticed), however, since as I stated there is a Specification for it
that says exactly the same.

If would would just have read what was posted and not what you imaged
you understood of it, you would be much less successful in posing as a
complete idiot here. I am sure there was already someone who told you
this.
PointedEars
Nov 23 '05 #25
David Dorward wrote:
Randy Webb wrote:
The statement is correct, however the reference is outdated.


Irrelevant to this thread.


This is Usenet. Discussions evolve, and drifting to tangential topics is
perfectly normal.


And there was not even a drift in topic but a correction of the reference
provided and a confirmation of the argument based on it.
PointedEars
Nov 23 '05 #26
Thomas 'PointedEars' Lahn wrote:
VK wrote:

Do not take <Thomas 'PointedEars' Lahn> too close to your heart. He's
one of numerous people in this group who managed to learn the basics of
the Books of the Cannon, and really believed what an appropriate
quotation from the book may solve anyone's problem. It is not true, but
the full reveal of this truth may hurt endlessly - so we just skip on
it.

If would would just have read what was posted and not what you imaged
you understood of it,


This sentence hurts my eyes.
you would be much less successful in posing as a
complete idiot here. I am sure there was already someone who told you
this.


Hello!!!
Can we please be a little more friendly towards eachother? And I don't
mean just Thomas and VK. I don't know what's going on. We preach to
eachother about netiquette and proper quotation, but don't use some
basic politeness when communication to eachother. I am sure that I am
not the only one that feels that things have gotten a bit aggressive
here lately in too many threads. People don't come here to read personal
insults.

Back on-topic:
<news:18****************@PointedEars.de>

I found the thread now, but I don't see how it is relevant to W3C
specification.
Nov 23 '05 #27
Robert <ro****@noreply.x> writes:
I am sure that I am not the only one that feels that things have
gotten a bit aggressive here lately in too many threads. [...]


Absolutely

Arnaud
Nov 23 '05 #28
aundro wrote:
Robert <ro****@noreply.x> writes:
I am sure that I am not the only one that feels that things have
gotten a bit aggressive here lately in too many threads. [...]


Absolutely


Well, respect has to be earned. VK keeps on presenting his nonsense
as the truth, even though disproved in short and in length many times
by more than one regular of this group. Since he does not listen to
polite arguments, one has to find other ways to put him in his place.
In fact, the only reason why I have not killfiled him is that I am
afraid he is so experienced in posting nonsense looking serious, a
newbie, especially one little experienced in client-side scripting,
could actually fall for it.
PointedEars
Nov 23 '05 #29
VK
> > Robert <ro****@noreply.x> writes:
I am sure that I am not the only one that feels that things have
gotten a bit aggressive here lately in too many threads. [...]


Absolutely


[1]
As you may notice even in this thread, the OP problem has been solved
by me (VK) in my first post. You also can see that <Thomas
'PointedEars' Lahn> as usual did not contribute anything into solving
the problem but trached the thread with pointless references and
neurastenic comments.

If you look in this group archives you'll see that his contribution is
stable very low, and his posting style is stable barely tolerable. Just
few month ago he used to be kicked off from all thread by The Cabal
members - until he had found a secure spot - of being a watch dog. So
now he sees his primary job by running across all threads and barking
on VK.

[2]
I personally state myself as a tolerant person (mostly). My posts may
be sometimes overly pathetic or wrong. You are totally free of errors
only if you don't do anything. But I always trying to find the truth -
even if it's going to be not my truth. Two arguments only I do not
accept and go ballistic:
"It's not true because N said it"
"It cannot be because the books/docs do not say that"
[3]
I visited <microsoft.public.scripting.jscript> and I have to admit that
in comparison of *styles* it looks like a Victorian evening party
against of a Wild West saturday night saloon. I doubt that clj will
ever get this level of refinement, but definitely there are some things
to improve to not scare hell out of newcomers. Personally I'll start to
shave now and hide the gun from my belt to the pocket.
:-)

Nov 23 '05 #30
Thomas 'PointedEars' Lahn wrote:
aundro wrote:

Robert <ro****@noreply.x> writes:
I am sure that I am not the only one that feels that things have
gotten a bit aggressive here lately in too many threads. [...]


Absolutely

Well, respect has to be earned. VK keeps on presenting his nonsense
as the truth, even though disproved in short and in length many times
by more than one regular of this group.


You don't have to earn not being insulted.
You can utterly disagree with someone without resorting to calling
someone a complete idiot. There are occasions that I thought that VK
made erroneous comments, or more often I simply could not understand
him, but insults don't help. Just warn the 'newbie' if you feel he is
being given wrong information. In the past I have given some wrong
information by accident or ignorance, and did not mind being corrected
if in a reasonably polite manner.
Nov 23 '05 #31
VK wrote:
> Robert <ro****@noreply.x> writes:
>> I am sure that I am not the only one that feels that things have
>> gotten a bit aggressive here lately in too many threads. [...]
>
> Absolutely

[1]
[...] You also can see that <Thomas 'PointedEars' Lahn> as usual


As usual _to you_. Not everything you are unable to comprehend is nonsense.
did not contribute anything into solving the problem
And I did not intend to as there was already a working solution. This is
not a support forum, but a newsgroup. I corrected a statement made by
RobG ...
but trached the thread with pointless references
.... by commenting on the reference that was already given by RobG(!)
regarding that statement and provided the correct one which still
backed his argument. This I already explained to you in
<news:73****************@PointedEars.de>, but you still not only
ignore it but try to turn that against me since it does not fit
your humble perception of the world.
[...]
If you look in this group archives you'll see that his contribution
is stable very low,
Another of your lies I can live with. There are other people, even
one I scored down for forging headers, who will disagree with you.
and his posting style is stable barely tolerable. Just
few month ago he used to be kicked off from all thread by The Cabal
members - until he had found a secure spot - of being a watch dog.
You write as you manage to understand. I wonder what "The Cabal" is
in your mind.
So now he sees his primary job by running across all threads and barking
on VK.
No, my primary job here alas has had to change into correcting the utter
nonsense you continue to post as the Holy Truth, so that others cannot
possibly fall for it.
[2]
I personally state myself as a tolerant person (mostly). My posts may
be sometimes overly pathetic or wrong. You are totally free of errors
only if you don't do anything.


I don't despise people who are wrong. Nobody's perfect. I despise people
like you who refuse to accept that they have been proven wrong, who wind
around and continue to claim they are right. I despise people who ignore
the Truth of Reality, who seek to twist it to fit their, and only their,
needs.
PointedEars
Nov 23 '05 #32
VK
Thomas 'PointedEars' Lahn wrote:
I wonder what "The Cabal" is in your mind.
It's a shameful question for a person who's claiming himself to be a
newsgroup rules and netiquette specialist. If you think that it's a
profanity then you are deeply wrong. The rest you can google out
yourselve. You may start from here:
<http://www.linux.it/~md/usenet/gr3.htm>

Thomas 'PointedEars' Lahn wrote: woof, woof, woof...


grrrrh! grrrrh!

:-)

Nov 23 '05 #33
VK wrote:
Thomas 'PointedEars' Lahn wrote:
I wonder what "The Cabal" is in your mind.
It's a shameful question for a person who's claiming himself
to be a newsgroup rules and netiquette specialist. [...]


It is not. I asked about your definition. One that may you think
in some way fits

| Just few month ago he used to be kicked off from all thread by
^^^^^^^^^^^^^
| The Cabal members

in <news:11**********************@g14g2000cwa.googleg roups.com>.
<http://www.linux.it/~md/usenet/gr3.htm>


So you have not understood that either.
PointedEars
Nov 23 '05 #34
Well I got the damb thing working now, well the other day.

With all the bad vibes I wish I had solved the thing myself in the first
place. Well whether I would have been able to is another thing, I never came
across document.open/close before and do not know how I would have been able
to find it without knowing it existed in the first place, so to speak.

Anyway thank you all for helping me out with this one I have had this bug
hanging round for quite a while now I even think it used to be in IE as well
!

Here's to proper integerity.

Thanks again all input is welcome :)
Aaron
Nov 23 '05 #35
Thomas 'PointedEars' Lahn <Po*********@web.de> writes:
Well, respect has to be earned.


But civil behavior should not.

It doesn't matter if one thinks that the other person is an idiot, no
matter how obvious it sometimes seems, bashing the person will not
change that. No matter if I'm right in everything I say, attacking
another poster will not bring anything but, perhaps, brief personal
gratification, and it *will* be one more voice lowering the level and
tone of the group, setting a bad example for everybody else.

The tone in this group *is* worsening, and have been for a while.
Even traditionally reasonable posters have begun going for the
person, not the error of his argument.
Or, more bluntly: I don't *really* care if someone thinks someone else
is an idiot, but if the someone need to wave it in front of me, I
*will* think he is acting like one. You can all do better than that!
So, I dare everybody to go a week without attacking another poster :)

/L 'Never argue with idiots. They merely bring you down to their level,
then beat you with experience'
--
Lasse Reichstein Nielsen - lr*@hotpop.com
DHTML Death Colors: <URL:http://www.infimum.dk/HTML/rasterTriangleDOM.html>
'Faith without judgement merely degrades the spirit divine.'
Nov 23 '05 #36

This discussion thread is closed

Replies have been disabled for this discussion.

Similar topics

4 posts views Thread by Stuart Perryman | last post: by
5 posts views Thread by Xarky | last post: by
11 posts views Thread by shankwheat | last post: by
4 posts views Thread by Tim Mackey | last post: by
4 posts views Thread by guiromero | last post: by
By using this site, you agree to our Privacy Policy and Terms of Use.