Forum OpenACS Development: Re: Checks for HTML standard compliance
I've started bumping my head on the task, starting from /admin UI. Right now the following pages look ok:
Headaches start at /admin/site-map/ though... in there you may find that forms are being nested into a table in an illegal way from HTML 4.01 Strict perspective.
It is really not obvious how to get out of that without redesigning the page. We could use a div instead than a table layout for the list for example.
This is just for the sake of keeping current UI unaltered for the user, of course. We could just have forms handled in their respective page.
Which is best for you?
Is this because of how ad_form works?
Using html (or the q-forms package ), multiple submit buttons can be embedded in the same form.
Submitted forms can then take action according to the name and value returned with the submit button; other submit button's name and value attributes are ignored.
the page was easy to fix by wrapping the input fields into a div (see ). Validation-wise there is no need to revamp this page.
anyhow, i've added quotes to the HTML attributes of the admin pages of acs-subsite were i found it missing, since for variable attribute values omitting quotes is always dangerous.
Therefore, i've implemented some support to capture the server output optionally  and fixed with that tool a few more validation problems of the admin pages. The problem with the site-map page is actually a nasty one, since the old code implemented a form starting in one table cell and ending in another one, which is invalid HTML. The fixed version  does not look exactly as before, but i think it is still sufficiently easy to understand. Other options would be to start the form before a <tr>, but i have no idea to achieve this with the list template.
Anyway, I have looked at your technique to log ns_return and maybe I will come up with something to reduce some passages.
I've set up a wiki page  for the pages I've fixed (and checked) so far to avoid duplication of work. please update this page as well (also, everybody else is invited to help). I found as well several public pages which needed some fixing.