Issue 2578 - Many violations of the w3c HTML standard on openoffice.org webpages
Summary: Many violations of the w3c HTML standard on openoffice.org webpages
Status: CLOSED FIXED
Alias: None
Product: Infrastructure
Classification: Infrastructure
Component: Website general issues (show other issues)
Version: current
Hardware: All All
: P3 Trivial (vote)
Target Milestone: ---
Assignee: Unknown
QA Contact: issues@www
URL: http://www.openoffice.org
Keywords:
Depends on:
Blocks:
 
Reported: 2001-12-18 04:50 UTC by jsdever
Modified: 2003-12-06 14:52 UTC (History)
1 user (show)

See Also:
Issue Type: DEFECT
Latest Confirmation in: ---
Developer Difficulty: ---

Attachments
Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this issue.
Description jsdever 2001-12-18 04:50:05 UTC 
The openoffice.org webpages claim to be HTML 3.2 standard:
"-//W3C//DTD HTML 3.2//EN"
But they are far from it.  There are many problems with the structure of the
tags of the currently generated pages.  Some effort should be made to correct
the violations of the output from the various parts webpage generation code.

For example, at the bottom of the main openoffice.org index.html file (and every
other one I looked at) there is the following  incorrectly structured markup:

</TABLE>

</TD>
</TR>
 
<!-- end footer -->   

  </body>
</html>

  </body>
</html>
Comment 1 lsuarezpotts 2001-12-18 06:27:55 UTC 
The Collabnet designers who designed the page are aware of 
the issues. As it happens, the pages are constructed 
dynamically using servlets serving up page fragments which 
together make up the whole page. But I don't even have control 
over the project pages, which are often entire 
staroffice-generated pages.
Thanks for the tip. And if you want to communicate with the 
design staff, let me know,
Louis
community manager
PS. this sort of issue is better handled by an email to 
webmasters@openoffice.org.
Comment 2 michael.bemmer 2003-03-24 08:22:08 UTC 
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.
Comment 3 michael.bemmer 2003-03-24 08:26:36 UTC 
As agreed by Louis I will close these resolved fixed support-owned issues now.
If you have trouble with that, please re-open the issue.