Results 1 to 2 of 2
2008-11-28, 03:01 #1
- Join Date
- May 2003
- Mid-Cheshire, England
- Thanked 3 Times in 3 Posts
Validation of HTML and CSS (Firefox 3.0)
I am a computing non-professional. However over the last 14 years I have gained some knowledge and experience in a number of aspects of computing. I would unreservedly acknowledge the help and assistance I have been fortunate to receive in Woody's Lounge.
My Web site at www.sandiwaygolf.co.uk/ has been developed over the last 10 years in FrontPage from versions FP97 through to FP2003. At present the site is being rebuilt by a third party using the Lasso Development Content Management System.
The problem I have had with the my FrontPage site has been with the difficulty of using FrontPage WYSIWG features and having non-compliant (proprietary) code created. To make the code compliant did become easier as FrontPage was developed over the years but I have only been partly successful in so doing.
I welcome the decision by my Golf Club management to redevelop their Web site in a content management system. However I find that the work done on the new site does not validate both in HTML and CSS. There are basic errors and numerous repetitious warnings. For example none of the pages have a <!DOCTYPE> declaration. I am told by the developer that the errors and warnings are known and are the consequence of using the Lasso Development Content Management System. I find the response, at best curious. To me, as far as possible both HTML and CSS should be written as near compliant as is possible if not, at the very least, to ensure backward compliance as the rapid development of everything to do with the Web continues.
So I am seeking views and opinions on the validation of the code not only in the Lasso Development Content Management System but also in general terms.
2008-11-28, 13:31 #2
- Join Date
- Feb 2001
- Silicon Valley, USA
- Thanked 93 Times in 89 Posts
Re: Validation of HTML and CSS (Firefox 3.0)
Generally speaking, browsers still have differences if you omit the DOCTYPE declaration. In quirks mode, developers tend to implement "hacks" to adapt to different browsers, or to ignore browsers that they do not take the time to personally test.
I can find information on Lasso, and on a CMS product named dCore that works with Lasso, but even assuming your developers are using this combination, it's not clear to me how pages actually are generated (e.g., based on a template, done 100% in code) so it's not obvious how you can insert the DOCTYPE for use in validating and tuning the site.