You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@wicket.apache.org by Kirk Israel <ki...@kisrael.com> on 2007/12/21 21:15:41 UTC
IE7, loose.dtd, and the default Wicket error pages
So IE7 seems to choke on the default Wicket error pages (such as time
out) because it doesn't like the --s inside of
http://www.w3.org/TR/html4/loose.dtd
Our work around was to override the pages on a case per case basis:
getApplicationSettings().setPageExpiredErrorPage(TimeoutPage.class);
I don't know if there's fingerpointing of IE7 vs w3.org about this.
Being a pragmatic developer with "street" roots, I greatly dislike a
decent error page with a link to the front of the site being replaced
with an ugly "can't parse the XML" page, so I was wondering who will
bend first, IE7, w3.org, or Wicket? And is there another more
generalized solution to this problem?
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org
Re: IE7, loose.dtd, and the default Wicket error pages
Posted by Niels Bo <ni...@gmail.com>.
I see the same in IE6 after updating from 1.3.0-rc1 to 1.3.0-rc2.
I belive it it caused by the license comment placed before the DOCTYPE tag
in the page markup.
See:
https://issues.apache.org/jira/browse/WICKET-1241
https://issues.apache.org/jira/browse/WICKET-1241
Niels
Kirk Israel-2 wrote:
>
> So IE7 seems to choke on the default Wicket error pages (such as time
> out) because it doesn't like the --s inside of
> http://www.w3.org/TR/html4/loose.dtd
>
> Our work around was to override the pages on a case per case basis:
>
> getApplicationSettings().setPageExpiredErrorPage(TimeoutPage.class);
>
> I don't know if there's fingerpointing of IE7 vs w3.org about this.
> Being a pragmatic developer with "street" roots, I greatly dislike a
> decent error page with a link to the front of the site being replaced
> with an ugly "can't parse the XML" page, so I was wondering who will
> bend first, IE7, w3.org, or Wicket? And is there another more
> generalized solution to this problem?
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
> For additional commands, e-mail: users-help@wicket.apache.org
>
>
>
--
View this message in context: http://www.nabble.com/IE7%2C-loose.dtd%2C-and-the-default-Wicket-error-pages-tp14461685p14481357.html
Sent from the Wicket - User mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@wicket.apache.org
For additional commands, e-mail: users-help@wicket.apache.org