Path: csiph.com!usenet.blueworldhosting.com!feeder01.blueworldhosting.com!peer01.iad.highwinds-media.com!news.highwinds-media.com!feed-me.highwinds-media.com!post01.iad.highwinds-media.com!fx33.iad.POSTED!not-for-mail
From: Robert Baer <robertbaer@localnet.com>
User-Agent: Mozilla/5.0 (Windows NT 5.0; rv:12.0) Gecko/20120422 Firefox/12.0 SeaMonkey/2.9
MIME-Version: 1.0
Newsgroups: comp.lang.javascript
Subject: Re: How fetch data from form for javascript screening
References: <ti0hz.37337$Z95.7322@fx29.iad> <7944450.CDJkKcVGEf@PointedEars.de> <Itdhz.1$uD.0@fx17.iad> <1692390.PYKUYFuaPT@PointedEars.de>
In-Reply-To: <1692390.PYKUYFuaPT@PointedEars.de>
Content-Type: text/plain; charset=UTF-8; format=flowed
Content-Transfer-Encoding: 8bit
Lines: 145
Message-ID: <P8hhz.310$WL3.241@fx33.iad>
X-Complaints-To: DMCA@thecubenet.com
NNTP-Posting-Date: Wed, 13 Jul 2016 01:51:43 UTC
Date: Tue, 12 Jul 2016 17:51:43 -0800
X-Received-Bytes: 5662
X-Received-Body-CRC: 1086376835
Xref: csiph.com comp.lang.javascript:30853

Thomas 'PointedEars' Lahn wrote:
> Robert Baer wrote:
>
>> Thomas 'PointedEars' Lahn wrote:
>>> Robert Baer wrote:
>>>> <script type="text/javascript">
>>>> // ** Screening code to use follows
>>>
>>> “Screening”?
>> * Yes; ASSuME i can get the data entered in the form fields,
>
> In theory, you can.
* Yah; the rub is in the practice...

>
>> i want to test according to certain criteria and REJECT the "e-mail"
>> attempt.
>
> The proper term for that is “form validation”.
* Thanks; documentaton duly changed.

>
>>>>      tstE= EBody[subjptr];
>>>
>>> 1. Assignment to undeclared identifier.
>>>
>>> 2. “EBody” should probably be “eBody”.
>> * Well,the assignment does that.
>
> Does what?
* The assignment declares the identifier.

> You have to declare the identifier one of a variable or this is
> at least error-prone.  (In the recommended strict mode, it throws a
> ReferenceError exception.)
* Have changed them to read: var tstE= EBody[subjptr];

>
>> I used the name EBody  for the array;
>> could have mixed the character cases at randumb for all javascript cares.
>
> Only identifiers for constructors/classes and constant(-like value)s should
> start with a capital character (constructor’s/class’s identifiers should be
> camel-case, constant’s identifiers should be all-uppercase), to tell them
> apart.
* do not know about constructors, but have changed all EBody to eBody.

>
>>>>     <form name="dataholder" action="">
>>>
>>> How can the user submit that form without script support?
>> * I know absolutely NOTHING how forms work.
>
> Learn it.
>
>> * for an input form that DOES work without script support, see […]
>
> You do realize that it was a rhetoric question, yes
* no.

>
>>> Use stylesheet rules, avoid style attributes.
>> * I know less about style sheets than a fly.
>
> Learn it.
>
>>>>         <input type="text" class="form-control" name="QN" id="#">
>>>
>>> Invalid ID except in HTML5.<http://validator.w3.org/>
>> * Stolen coding that i am fiddling with in futile attempts to get info
>> from form to javascript.
>
> This is not a free support forum for script-kiddies doing copy&  pray, but a
> newsgroup for (aspiring) software developers.
>
>>>> […]
>>>>         <!-- The browser must use the tpe for crude checkfor te @ sign
>>>>         -->
>>>
>>> I beg your pardon?
>>     Note: input type="email"; the browser must be doing the checking for
>> an "@" sign - input must be like x@x and not xxx.
>
> The rules are considerably more complex than that, and you may want to use
> your own validator instead since the built-in rules are too restrictive (and
> work only in HTML5 user agents anyway).
* 1) The code i am building on is all HTML5.
   2) i plan to add more restrictive rules as checking for an "@" only 
is rather lame.
   3) if that has more rules, nobody is talking.

>
>>>> <script type="text/javascript">
>>>>
>>>> // do not know what to do to get those variables
>>>
>>> That is not a question.
>> * OK, it was a statement. _HOW_ do i get this to work?
>>     Code stolen from http://www.oil4lessllc.com/index-4.html.
>
> See above.  You need a minimum clue before it makes sense to give you
> further advice.  But this is not JavaScript/DOM 101; you need to *follow*
> the *references* to *free* documentation that you have been given, and
> *read* about the basics there.
* I tried SIX other schemes from "references" as read in "free" 
documentation, and NONE work.
   None of those said anything about "basics".

>
>>>> //  following gives undefined
>>>> //    Qmsg=document.getElementsByName("form-control").innerHTML ;
>>>> //    document.writeln(Qmsg+"|<BR>");
>>>
>>> getElement*s*ByName
>> * Yes; online guides indicated a message field/block is an array;
>
> It is not; instead, the getElement*s*ByName() method returns a reference to
> an array-like DOM object (that implements at least the NodeList interface).
> Compare getElementById().
>
>> that reading from a multi-line field/block is done by a set (array) of
>> elements.
>
> This has nothing to do with whether the field is multi-line (i.e. is a
> textarea).  What “block” are you talking about?
* The box i see; a block of character space.

>
>>     I could change that,
>
> You cannot, this feature is built into the DOM implementation.
>
>>     but the change will not fix the rest of the
>> problems.
>
> The main problem is that you do not have the slightest clue what you are
> doing or talking about, and you appear to be unwilling to make an effort
> changing that.
* Effort? Spending many hours,working with "examples" of code said to work?
   Even tho the result is zilch, the effort is a lot.
   Got frustrated and asked for help.

>
   Thanks.