You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Eelco Hillenius (JIRA)" <ji...@apache.org> on 2008/10/08 23:01:44 UTC
[jira] Resolved: (WICKET-1591) let BrowserInfoPage be customizable
/ extendable
[ https://issues.apache.org/jira/browse/WICKET-1591?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Eelco Hillenius resolved WICKET-1591.
-------------------------------------
Resolution: Won't Fix
I think what we have is flexible enough, and it is easy enough to provide a custom implementation.
> let BrowserInfoPage be customizable / extendable
> ------------------------------------------------
>
> Key: WICKET-1591
> URL: https://issues.apache.org/jira/browse/WICKET-1591
> Project: Wicket
> Issue Type: Improvement
> Components: wicket
> Affects Versions: 1.3.3
> Reporter: Peter Ertl
> Assignee: Eelco Hillenius
> Fix For: 1.5-M1
>
>
> When using
> IRequestCycleSettings.setGatherExtendedBrowserInfo(true)
> wicket will display a intermediate page with the following text:
> "If you see this, it means that both javascript and meta-refresh are not support by your browser configuration.
> Please click <a wicket:id="link" href="#">this link</a> to continue to the original destination."
> Especially when the browser starts up java (sloooow!) this screen will be visible for a few seconds. It would be nice if you could customize this screen as it is very irritating to non-english speakers.
> Maybe something like
> IRequestCycleSettings.setGatherExtendedBrowserInfoPage(MyBrowserInfoPage.class)
> would be good
> "public class MyBrowserInfoPage extends BrowserInfoPage"
> Also wicket users could extend the browser test by more checks.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.