** MOVED FROM ORIGINAL THREAD **
=================
Is not the focus to generate a code which is W3C compliant, which means: moving towards XHTML strict compatibility up to XHTML 5 ?Quote:
Originally Posted by covoxer
Printable View
** MOVED FROM ORIGINAL THREAD **
=================
Is not the focus to generate a code which is W3C compliant, which means: moving towards XHTML strict compatibility up to XHTML 5 ?Quote:
Originally Posted by covoxer
Do you have any W3C compliance problems with current code?Quote:
Originally Posted by ab29
The actual Xtreme Web Designer Code is W3C compliant up to XHTML transitional (which means what it means). If it is currently sufficient for most of cases, it may be a limitation for others, and also regarding to the actual development of web technologies.
Which means it is W3C compliant. Case closed. ;)Quote:
Originally Posted by ab29
Well actually, in most cases people have problems with it not being a HTML4.1. Know why? Because a lot of the code snippets available on the web are HTML4. Using such a snippet with any sort of XHTML makes resulting code invalid as HTML4 code is not compatible with XHTML. On the other hand, if you find any XHTML Strict snippets, they will work just fine because XHTML Strict is compatible with XHTML Transitional.Quote:
If it is currently sufficient for most of cases, it may be a limitation for others, and also regarding to the actual development of web technologies.
So, following your thinking about possible limitations for other users, we should probably fall back to using HTML 4.1 standard. Right? ;)
As to the development of the web technologies, considering browser side, everything is even worse. We may sincerely hope that compliance to any W3C standard can make our code more compatible with browsers that support this standard. But unfortunately, this is pure theory. On practice we have a huge pile of browser specific quirks among most widely used browser engines. And the actual compatibility problem is to generate code that will look the same in all of them. W3C compliance doesn't help here at all. Even worse - currently it's harder to achieve consistent results with XHTML Strict. That's why we avoid it for now. Perhaps in future, when all major browsers become completely reliable in rendering code, it would be possible to switch to XHTML Strict. But not yet. And not until all current browsers will become completely forgotten. Don't forget, we still have to keep compatibility with IE6 which is one of the most used browsers!
Personally I don't believe that any serious browsers will appear in the near future that will not support even the old HTML4.1 standard. Never mention the pure XHTML Strict browser. Why? Quite a few reasons for this. First of all, billions of pages on the web are not XHTML. Many of them are poorly coded and doesn't even comply to HTML4. Who'll want to use browser that doesn't browse half of the web? Second, who needs to develop yet another browser engine if we already have not less than 4 of the highly developed, including 2 of them open source? Shall they drop support of the older standards? No, never. And finally, the whole XHTML ideology was based on the creating the standard that is easier to render. Thus the simpler browser software would be needed and the less hardware requirements implied. But it was 10 years ago. No need to write new browser software exists today as everyone can use existing code. And hardware had developed so much that even average mobile phone is capable of running fully functional all standards compliant browser software. So what's the point in creating strict browser software? None. And we see it in reality. Browser software appearing in mobile devices remains compatible with all the HTML legacy.
Where are the problems with XHTML strict, if I may ?Quote:
Even worse - currently it's harder to achieve consistent results with XHTML Strict.
Sorry. I can not fully disclose this subject in the properly short form for the forum discussion.Quote:
Originally Posted by ab29
Is it a question of efficiency of the HTML filter ?
Though, there exists opensource XHTML strict and CSS-based editors like this one, 100% Javascript code:
http://www.wymeditor.org/features/
How this relates to Xtreme?
We were speaking on an other thread about extending "the basic javascript library which is generated along with any HTML pages created using Xara Extreme (or web designer I guess)."
http://www.talkgraphics.com/showthread.php?t=42435
Yes. That discussion continues on that thread. Here we have an offspring thread about HTML standard used by Xtreme.