Path: csiph.com!fu-berlin.de!uni-berlin.de!individual.net!not-for-mail
From: Arno Welzel <usenet@arnowelzel.de>
Newsgroups: comp.lang.php
Subject: Re: Is it legitimate to have a continuous TABLE through multiple FORMs?
Date: Thu, 25 Apr 2019 14:09:00 +0200
Lines: 71
Message-ID: <gidmatFqspeU1@mid.individual.net>
References: <f00fdd04-e13e-4aa8-98a6-43b8cdbbd996@googlegroups.com> <q9rq6d$rf6$1@gioia.aioe.org> <gidbkjFol28U1@mid.individual.net>
Mime-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit
X-Trace: individual.net /Ix2vBF8/762UPErwLKvcg2SETteolZ+Q9c6e/pyoeQm9Osj9Q
Cancel-Lock: sha1:Vf3IbMEBtQzyNomnchpU5Ooi5yQ=
In-Reply-To: <gidbkjFol28U1@mid.individual.net>
Content-Language: en-US
Xref: csiph.com comp.lang.php:17891

On 25.04.19 11:06, Arno Welzel wrote:

> On 25.04.19 09:49, R.Wieser wrote:
> 
>> Dan,
>>
>>> The funny thing is, it runs fine.  The Browser doesn't complain
>>> about it, although my IDE complains (appropriately, imo) of
>>> nesting issues.
>>
>> Have you tried (looking at the example you posted) to move the FORM tag from 
>> just above the TABLE tag to just below it (just infront of the TR tag) ?
> 
> Which is not valid either. <form> must not be a child of <table>.
> 
> See:
> 
> <https://www.w3.org/TR/html52/tabular-data.html#the-table-element>
> <https://developer.mozilla.org/en-US/docs/Web/HTML/Element/table>
> 
> That's why I recommended using a HTML validator to check the result.
> Just because elements are properly nested it does not mean that it's
> valid HTML.
> 
> It may be neccessary to do more refactoring than just moving tags around.

And for the sake of peace with R. Wieser who believes, it don't know,
what I'm talking about - a more specific example, how it *could* be:

1) Never put a <form> as a child of <table> itself - this is not allowed
and procudes invalid HTML

2) Never interleave tags

So the a simplified example for the code fragment *could* be like this:

<div id="main">
  <div class="container">

    <!-- first form here with a table *inside* -->

    <form class="xxxx" action="xxxx.php" method="post">
      <table width="100%">

        <!-- all the content for this form here -->

      </table>
    </form>

    <!-- second form here with another table *inside* -->

    <form class="xxxx" action="xxxxxx.php" method="post">
      <table width="100%">

        <!-- all the content for this form here -->

      </table>
    </form>

   </div>
</div>

Personally I would redesign the whole thing and not use TABLE at all but
 DIV elements only CSS grids or bootstrap. These could be responsive as
well, if needed.



-- 
Arno Welzel
https://arnowelzel.de