But how can we know that for some pages users don't want to force the quirks mode? I'm big -1 on stripping the xml declaration for all pages by default. That would break any application where the users are relying on <xml declaration making IE use quirks mode.
We should focus on the problem itself, and that is the Apache header between the <?xml declaration and doctype which is what completely breaks IE. Now I can see two simple solution. Either wraps the header comment with <wicket:remove> or move the header comment after doctype. -Matej On Dec 28, 2007 1:55 AM, Juergen Donnerstag <[EMAIL PROTECTED]> wrote: > that is true but that is the intend, isn't it: make sure that no page > makes IE to change into quirks mode. > > Juergen > > > On Dec 28, 2007 1:31 AM, Matej Knopp <[EMAIL PROTECTED]> wrote: > > The thing is that setStripXmlDeclarationFromOutput is a global change > > and it affects all pages. > > > > -Matej > > > > On Dec 28, 2007 12:44 AM, Juergen Donnerstag > > > > <[EMAIL PROTECTED]> wrote: > > > I think 1139 makes sense and we should still aim to find a solution > > > for it. The way we have solved it is by using > > > getMarkupSettings().setStripXmlDeclarationFromOutput(true) which > > > removes the xml declaration from the output (and by using the xhtml > > > doctype in the base page). And we don't even need the meta tag since > > > the html header contains the encoding as well. It seems to work fine > > > for some inhouse utility apps which are used globally. Is changing the > > > default setting to much of a change for now? > > > > > > Juergen > > > > > >
