come out like
<tr> a </tr>
<tr> b </tr>
<tr> c </tr>
<tr> d </tr>
a b c d
when it should look like...
swap your tr's and td's around.
Because to get the result that you want, the code should be:
<td> a </td>
<td> c </td>
<td> b </td>
<td> d </td>
"<tr>" cannot exist inside of a "<td>", and "<td>" canot exist anywhere but inside of a "<tr>".. more-or-less the browser is trying it's best to render something..
ohh no wonder i am nub
Originally Posted by WebJoel
this sucks cuz
i need to generate more and more columns... not rows arg
im using some code on the backend to try to make columns and stuff oh well
now im going to have like 25 for loops (using XQuery!!)
Yes you can't put a table row inside of a table division but you can put a table inside of a table row if I'm not mistaken.
You might want to call "<td>" "table data" cells and not "table divisions", -lest we confuse newcomers.
Yes you can't put a table row inside of a table division
Nesting tables, -can be done but it's a bain and should be avoided.
Lol, and this is why I hate tables.
'nested tables' had a particularly deletarious effect upon WIN-98 2nd Edition with minimal system RAM. I used to have ~, and any page with 3 or 4 'table nestings' almost always resulted in a lovely BSOD. A 'stack overflow' was the official cause. Increasing the RAM helped but Win-98 had a 'software bug' that created this suseptability.
I much prefer using DIVisions, -they were made for and intended for just such nesting, and as such, work the processor much less.
And, -I have long since switched to XP (and Linux).
Users Browsing this Thread
There are currently 1 users browsing this thread. (0 members and 1 guests)