On Wed, February 1, 2006 3:06 pm, John Nichel wrote:
> I also don't _have_ to declare variables, don't _have_ to call
> mysql_close, etc, but that doesn't make it a good practice. The above
> 'standard' is pretty and all, but how many browsers out there are 100%
> standards compliant? Quoting wil
David Dorward wrote:
Robert Cummings wrote:
Slop?
Yes, slop, ie sloppy.
authors may specify the value of an attribute without any quotation
marks. The attribute value may only contain letters (a-z and A-Z),
digits (0-9), hyphens (ASCII decimal 45), periods (ASCII decimal 46),
On Wed, 2006-02-01 at 18:34, David Dorward wrote:
> Richard Lynch wrote:
>
> >>> There's no excuse for writing slop.
>
> > "We recommend using quotation marks even when it is possible to
> > eliminate them."
>
> Presumably because its less hassle to do so then to try to remember the
> exceptions
Richard Lynch wrote:
>>> There's no excuse for writing slop.
> "We recommend using quotation marks even when it is possible to
> eliminate them."
Presumably because its less hassle to do so then to try to remember the
exceptions. It doesn't make code that ignores that suggestion "slop".
--
Dav
On Wed, February 1, 2006 2:52 pm, David Dorward wrote:
> Robert Cummings wrote:
>
>> >
>> I also took the liberty of adding double quotes to your attributes.
>> There's no excuse for writing slop.
>
> Slop?
>
> authors may specify the value of an attribute without any quotation
> marks. The att
Change it to:
input name="xname[]"
On Wed, February 1, 2006 10:07 am, Mauricio Pellegrini wrote:
> Hi ,
> I have a HTML page with a form in which there are some inputs like
> these:
>
> input type=text name=xname value="3303"
> input type=text name=xname value="9854"
> ..
Robert Cummings wrote:
>
> I also took the liberty of adding double quotes to your attributes.
> There's no excuse for writing slop.
Slop?
authors may specify the value of an attribute without any quotation
marks. The attribute value may only contain letters (a-z and A-Z),
digits (0-9)
Mauricio Pellegrini wrote:
Thank you all for your valuable support.
The problem is solved.
Note:
This kind of input definition (without the brackets) actually *DOES*
create an array under HTML 4.x (and its subindexes are accesible thru
javascript)
If that's the case (I can't find a
Thank you all for your valuable support.
The problem is solved.
Note:
This kind of input definition (without the brackets) actually *DOES*
create an array under HTML 4.x (and its subindexes are accesible thru
javascript)
You forgot the array append operator:
>
> ..
Please don't hijack threads.
Mauricio Pellegrini wrote:
Hi ,
I have a HTML page with a form in which there are some inputs like
these:
input type=text name=xname value="3303"
input type=text name=xname value="9854"
input type=text name=xname value="n..."
On Wed, 2006-02-01 at 11:07, Mauricio Pellegrini wrote:
> Hi ,
> I have a HTML page with a form in which there are some inputs like
> these:
>
> input type=text name=xname value="3303"
> input type=text name=xname value="9854"
>
> input type=text name=xname value="
The input name must include [] (brackets) to let php know it's an array.
Ex: input type=text name=xname[] value="3303"
On Feb 1, 2006, at 9:07 AM, Mauricio Pellegrini wrote:
Hi ,
I have a HTML page with a form in which there are some inputs like
these:
input type=text name=xname va
Mauricio Pellegrini wrote:
Hi ,
I have a HTML page with a form in which there are some inputs like
these:
input type=text name=xname value="3303"
input type=text name=xname value="9854"
input type=text name=xname value="n..."
the name of the input is al
Hi ,
I have a HTML page with a form in which there are some inputs like
these:
input type=text name=xname value="3303"
input type=text name=xname value="9854"
input type=text name=xname value="n..."
the name of the input is always the same ( xname )
This
14 matches
Mail list logo
