You've mentioned this at least once before. Is it something that you've submitted a bug report about? Can you provide an example of Legacy creating such incorrectly nested tables. I've always imported my created pages into my own HTML editor and while I've noticed a lot of small errors such as missing closing tags, etc, I've never seen the issue with the tables. Either I've overlooked it or it's from a type of pages I've never created.
Keep in mind that W3C regards the use of tables as outdated and recommends better constructs (DIV tags, etc.). I guess all of this sort of dates Legacy's created HTML as already somewhat out of date. Maybe they do need to look at this matter again and bump it up in priority before the competition starts creating pages with full HTML5 sound and video. Brian in CA -----Original Message----- From: Ron Ferguson [mailto:[email protected]] Sent: Wednesday, September 18, 2013 2:01 PM To: [email protected] Subject: Re: [LegacyUG] Webpages Ward, Purely in the interest of avoiding wasted discussion may I make it clear that the problems of font size are not connected at all with the incorrect nesting of tables. Problems due to nesting mainly arise when one wishes to enclose Legacy pages in headers and footers, or more seriously if a side column (eg. for an index) is created Ron Ferguson http://www.fergys.co.uk/ Legacy User Group guidelines: http://www.LegacyFamilyTree.com/Etiquette.asp Archived messages after Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Archived messages from old mail server - before Nov. 21 2009: http://www.mail-archive.com/[email protected]/ Online technical support: http://www.LegacyFamilyTree.com/Help.asp Follow Legacy on Facebook (http://www.facebook.com/LegacyFamilyTree) and on our blog (http://news.LegacyFamilyTree.com). To unsubscribe: http://www.LegacyFamilyTree.com/LegacyLists.asp
