I haven’t looked very closely at the 8.5 beta yet, but xPages has got me quite excited. One thing I noted though is that the pages are generated as HTML 4.01 Strict. Now standards-compliance mode is great! But what about pumping out XHTML?
Specifically, is it possible to have the xPages generate code that is valid XHTML 1.0 Strict?
There is a LOT of the corporate world still running very old browsers, mixed applications, etc. where pure XHTML is not an option.
XPage output is pretty much XHTML-compliant, though the doctype is transitional. Of course, you can override the doctype if-needed, and still leverage a lot of XPage functionality while outputting pure XHTML.
Subject: Which part of XHTML the old browsers don’t understand?
I think you need to have something like IE3 not to understand XHTML. But even then I don’t understand why it would not accept XHTML which is just well formed HTML. Quite interesting corporate policy would be to use IE3 with the latest Domino version utilizing XPages!
For me Xpages generate the same old HTML !DOCTYPE unless I change it.
It’s our corporation’s policy that all web content must be XHTML 1.0 Strict. The cited reason for the policy is universal accessibility. There are other good reasons, of course, especially as we increase our use of XML technologies such as XSLT and we are considering mixing in XForms.