Non compliant W3, XHTML 1.0 strict

User 1947912 Photo


Registered User
114 posts

Hello. I was just wondering why a fresh XHTML 1.0 Strict document created within html editor 2010 is non compliant immediately. It seems that the openeing html tag should be reaplced with <html xmlns="http://www.w3.org/1999/xhtml"> and when using many other editors this tag is automatically inserted. HTML editor is one of my favorite text editors so I was just wondering if there was a reason for this or if its simply an error and if so can it be changed. Thank you.
www.andysmotorcycles.com
support@andysmotorcycles.com
(01782) 818097
Order motorcycle, scooter and motocross parts, spares and accessories online now.
User 1947912 Photo


Registered User
114 posts

The only way to get this correct is by using the new page wizard which does replace the non compliant <head> tag, however using this method there is no way to turn off the colour attributes for links which is automatically inserted within the html and as we all know stict doc types do not allow and form of syle code to be inserted via xhtml and must be inserted via css so is there a work around or update for this problem. Thank you
www.andysmotorcycles.com
support@andysmotorcycles.com
(01782) 818097
Order motorcycle, scooter and motocross parts, spares and accessories online now.
User 562592 Photo


Registered User
2,038 posts

You can change it in your preferences.
The philosopher has not done philosophy until he has acted upon the mere conviction of his idea; for proof of the theory is in the act, not the idea.

My Web Development Company: http://www.innovatewebdevelopment.com (Created with Coffee Cup Software).

My Personal Website: http://www.EricSEnglish.com

User 1947912 Photo


Registered User
114 posts

Let me explain a little better.
I have changed my default doc type in preferences to XHTML 1.0 Strict. If I start a new blank page the default code does not change to compliant W3 code but remains exactly the same as any other html document. The only error is with the <html> tag which is not compliant with XHTML 1.0 strict and should be <html xmlns="http://www.w3.org/1999/xhtml">

However, when you create a new document using the new page wizard and choose XHTML 1.0 strict this <html> tag is corrected to the compliant code mentioned above however the only problem is that as default the wizard generates link colour codes which you cannot turn off within the opening <body> tag. This is usefull however for Strict document styling is not permitted within HTML and must instead be implemented using css.

I was just wondering if there is a reason for this or if it is just an error? Its not a problem changing the code everytime i create a new document however I thought this may be a little confusing for newcomers to the software.

If iv missed something id be happy to know. Thank you.
www.andysmotorcycles.com
support@andysmotorcycles.com
(01782) 818097
Order motorcycle, scooter and motocross parts, spares and accessories online now.
User 364143 Photo


Guest
5,410 posts

This may be something the developers can look into for the next release. For now, you can save the initial page code for XHTML 1.0 Strict as a snippet to replace the auto generated code for those docs.
CoffeeCup... Yeah, they are the best!
User 1947912 Photo


Registered User
114 posts

Yes this is what I have done.
This realy is not a problem as I usualy always run my code through HTML tidy anyway, just to drop any typo's i may have made along the way.
This is however something that needs a quick look at by the developers since W3 validation is so tightly integrated within the software. Apart from that I cannot say I have any issues with HTML editor and I have even stopped using Dreamweaver since.

Is there actually a propper thread for posting software bugs found within any of cc's app's? If so could you please link. Thanks guys...
www.andysmotorcycles.com
support@andysmotorcycles.com
(01782) 818097
Order motorcycle, scooter and motocross parts, spares and accessories online now.
User 364143 Photo


Guest
5,410 posts

Just put in a support ticket describing the situation. This can be forwarded to the developers.
CoffeeCup... Yeah, they are the best!

Have something to add? We’d love to hear it!
You must have an account to participate. Please Sign In Here, then join the conversation.