Red Hat Bugzilla – Bug 117949
Weirdness with customising Portal/Portlet applications when running in XHTML
Last modified: 2007-04-18 13:04:08 EDT
Description of problem: I changed the site output to XHTML and all is fine except when customising a portlet. The page only partially loads, and the bebop stylesheets [used by the portlet custom app] cause the rest of the page HTML to load in the customise text-area. I havent an example, as camden wanted me to revert back to HTML output, but when you come to have a look at this, contact me and I'll temporarily change the workspace-index.xsl to XHML output to demo. NB> This was in a 'theme' on the camden staging box Version-Release number of selected component (if applicable): How reproducible: each time Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info:
We recommend against outputting XHTML since it offers no concrete benefits over HTML 4.0 and it has less widespread browser support. Also, with free text entry fields (eg CMS body text) users will not typically take care to enter XHTML, so the resulting complete pages will not be wellformed even if the HTML from XSL template is. If there are specific XSL changes you can provide, we can incorporate them, but otherwise I'll close this as not a bug.
cheers Dan thats cool - we had chosen HTML 4 for camden & generic templates - for the same reasons as you highlight, just that Arturo suggested I query