[EMAIL PROTECTED] wrote: > Not really an outstanding issue but... > > I am planning to have the next XWatch release based on XWiki 1.4 and, > because of GWT's problems with browser standards mode rendering, I need a > method to remove the document type declaration in the standard xwiki > pages. The simplest solution would be to add a parameter to handle the > declaration in htmlheader.vm. Now, since Watch is deployed as a xar, I > cannot do that watch-specific and I need it in platform-web. The specific > issue bothering me is at: http://jira.xwiki.org/jira/browse/XWATCH-104 . > > WDYT? > Is it ok to allow the users to request a page with a specific doctype? Is > it ok to do it this way? (the cleaner solution, but harder to implement, > would be to have the doctype specified at content render time e.g. > $response.setDoctype("standard")) > If all above true, can we have this in 1.4? >
For the moment I committed the fastest, simplest, least dangerous solution, which is to skip the doctype completely when using noDoctype=true in the request URL. I don't really see a need for many doctypes, as htmlheader is supposed to be used only with HTML, and we should really encourage users to write XHTML strict compliant code (dream on...). We'll see if we need custom doctypes in htmlheader when html5 and xhtml2 are out and usable. -- Sergiu Dumitriu http://purl.org/net/sergiu/ _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
