Sorry, that should have been:
>You can *not* detect Javascript support with it.
Sven
On 23.04.2015 14:43, Sven Meier wrote:
Hi,
when you have JavaScript disabled, the page will request itself via
meta-refresh, that's intended.
>If BrowserInfoPage has set the ClientInfo properties then JavaScript
is enabled
I don't think this is correct: WebClientInfo and ClientProperties are
always set. You can detect Javascript support with it.
Regards
Sven
On 23.04.2015 09:05, Martin Grigorov wrote:
Double check that JavaScript is disabled.
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Thu, Apr 23, 2015 at 12:06 AM, Chris <[email protected]> wrote:
Hi Martin,
do you have a tip for following problem?
Thanks!
I have disabled Javascript in Firefox and inserted following code
below
but nevertheless, the page does not display "If you see this, it
means that
both javascript and meta-refresh are not support by your browser
configuration. Please click this link <
http://localhost:8080/wicket/bookmarkable/org.apache.wicket.markup.html.pages.BrowserInfoPage;jsessionid=5694CB335CDA79B343ADF5D4DC3E029C>
to continue to the original destination.“ This message shortly pop ups
when setting a breakpoint but then refers to the original page content.
The client info properties are set.
Wicket App:
public void init() {
super.init();
getRequestCycleSettings().setGatherExtendedBrowserInfo(true);
Page:
WebClientInfo clientInfo = WebSession.get().getClientInfo();
clientInfo.getProperties();
br Chris
Am 21.04.2015 um 14:29 schrieb Martin Grigorov
<[email protected]>:
http://www.wicket-library.com/wicket-examples-6.0.x/hellobrowser/
shows it
https://github.com/apache/wicket/tree/master/wicket-examples/src/main/java/org/apache/wicket/examples/hellobrowser
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Apr 21, 2015 at 3:21 PM, Chris <[email protected]> wrote:
Hi, could you give a small example how to reference the
BrowserInfoPage?
thanks
Am 21.04.2015 um 13:39 schrieb Martin Grigorov
<[email protected]
:
Java != JavaScript
If BrowserInfoPage has set the ClientInfo properties then
JavaScript
is
enabled
Martin Grigorov
Wicket Training and Consulting
https://twitter.com/mtgrigorov
On Tue, Apr 21, 2015 at 2:09 PM, Chris <[email protected]> wrote:
Andrew, thanks a lot!
How could I in addition check if Javascript is enabled so that
I can
add a
default Panel in case if it is not enabled?
The following 2 lines do not work as it returns false although
JS is
enabled.
WebClientInfo clientInfo = WebSession.get().getClientInfo();
if (clientInfo.getProperties().isJavaEnabled()) …
br, Chris
Am 21.04.2015 um 05:24 schrieb Andrew Geery
<[email protected]
:
In AjaxLazyLoadPanel#getLazyComponent(String), you should be
using
the
id
parameter, not "pList", when creating the PListPanel.
Andrew
@Override
public Component getLazyLoadComponent(String id) {
return new PListPanel("pList", pModel); //
change
the first param from "pList" to id
}
On Mon, Apr 20, 2015 at 11:10 PM, Chris <[email protected]> wrote:
Hi all,
I am following the example from
http://www.mkyong.com/wicket/how-do-use-ajaxlazyloadpanel-in-wicket/
but
get following error:
Last cause: Cannot replace a component which has not been added:
id='pList', component=[PListPanel [Component id = pList]]:
[AjaxLazyLoadPanel [Component id = pList]]
By the way, is the checking for JavaEnabled valid or still
needed?
I
have
JavaScript enabled but the method #isJavaEnabled returns false;
WebClientInfo clientInfo = WebSession.get().getClientInfo();
if (clientInfo.getProperties().isJavaEnabled()) {
add(new AjaxLazyLoadPanel("pList", pModel) {
@Override
public Component getLazyLoadComponent(String id) {
return new PListPanel("pList", pModel);
}
}).setOutputMarkupId(true);
} else {
add(new PListPanel("pList", pModel);
}
Thanks, Chris
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]