the phx is used to change the color per secton instead of using 7 templates (1 for home 1 for each main page and 1 for each main page children where the examples are) we used ultimateparent to determen what section we are in and then use phx to see if we are in that section and show the right color for the headers and then another phx part for the frame used in the examples so we only used 2 templates now 1 for home and one for the rest.
the /td> part is not in the form its not even in the source only when you look at it with ff using the generatesource view its there. I have no idea where it comes from.
Dimmy
Dimmy,
It’s a beautiful site.
I ran the Bestellen page through WC3 validation and noticed a few things:
should be
since it’s used more than once on the page. You’ll have to adjust the .css file accordingly too.
The /tr> error (which also shows up in IE6) appears to be causing a number of cascading errors. Have you looked for it in the page’s template? Sometimes it helps to paste the template page code into the WC3 validate by direct input page:
http://validator.w3.org/#validate_by_input
Templates should validate even without the content present.
There are some other errors reported (possibly a missing or extra <div> or </div> tag) but most appear trivial and may disappear when you fix the errors mentioned above.
Hope this helps.
Bob
you see it in IE but look at the source its not there... looks like its placed by someting els maybe javascript?
its weard
