I just ran into a situation trying to change the sort order in nph-build (see ....)
because my link.html is between <tr>...</TR> tags.
<P>
What I was getting on the screen was all the category names at the top, with
the links all at the bottom..
<P>
This was because the category name was inserted into the HTML after the TABLE tag, but
between <TR> tags. It _looked_ like the category names were all being processed first,
then the links. After a dozen edits and changes, I looked very, very closely at the
html..
<P>
This is a really good example of why you should really make all the inserted templates
and files adhere to the same format. Either a ROW or a complete TABLE.
<P>
This is the _most_ obscure bug I have ever tracked down, and it showed the _same_ in both
NN and MSIE (which is unusual). Usually one or the other will alert you to where the
potential problem is, so the first thing to do is look at your page in the other other
browser. If it looks the way you expected, it's an HTML/style thing.
<P>
In this case, both browsers handled the broken HTML the same way, even fomatting it the
same inside a containing table, and made it look like it was perl/cgi problem.
<P>
I got lucky looking for it --- in the HTML the "links" looked the way they should be,
not grouped into a top and bottom section, so I finally realized it had to be an HTML
thing.
<P>
Here is an excerpt of the HTML:
</TR>
<P><B>Cool Link #2 was found in : </B><BR> <A HREF="http://www.postcards.com/pcSQL/pages/Categorized_Sites/index.html">Categorized Sites</A></p>
<TR VALIGN=TOP ALIGN=RIGHT>
<TD ROWSPAN=2 WIDTH=122 VALIGN=MIDDLE ALIGN=RIGHT>
<P>
by doing this, I created the bizzare bug I've ever had to track. It's Miller time!!
===
If you are interested, the whole file is at:
http://postcards.com/...n_table_example.html It's pretty amazing how this formats ... not at all what you'd expect.
[This message has been edited by pugdog (edited November 28, 1999).]
because my link.html is between <tr>...</TR> tags.
<P>
What I was getting on the screen was all the category names at the top, with
the links all at the bottom..
<P>
This was because the category name was inserted into the HTML after the TABLE tag, but
between <TR> tags. It _looked_ like the category names were all being processed first,
then the links. After a dozen edits and changes, I looked very, very closely at the
html..
<P>
This is a really good example of why you should really make all the inserted templates
and files adhere to the same format. Either a ROW or a complete TABLE.
<P>
This is the _most_ obscure bug I have ever tracked down, and it showed the _same_ in both
NN and MSIE (which is unusual). Usually one or the other will alert you to where the
potential problem is, so the first thing to do is look at your page in the other other
browser. If it looks the way you expected, it's an HTML/style thing.
<P>
In this case, both browsers handled the broken HTML the same way, even fomatting it the
same inside a containing table, and made it look like it was perl/cgi problem.
<P>
I got lucky looking for it --- in the HTML the "links" looked the way they should be,
not grouped into a top and bottom section, so I finally realized it had to be an HTML
thing.
<P>
Here is an excerpt of the HTML:
Code:
</TR>
<P><B>Cool Link #2 was found in : </B><BR> <A HREF="http://www.postcards.com/pcSQL/pages/Categorized_Sites/index.html">Categorized Sites</A></p>
<TR VALIGN=TOP ALIGN=RIGHT>
<TD ROWSPAN=2 WIDTH=122 VALIGN=MIDDLE ALIGN=RIGHT>
<P>
by doing this, I created the bizzare bug I've ever had to track. It's Miller time!!
===
If you are interested, the whole file is at:
http://postcards.com/...n_table_example.html It's pretty amazing how this formats ... not at all what you'd expect.
[This message has been edited by pugdog (edited November 28, 1999).]
HTML nasty bug with tables....