Hyperlinks blocked by ClickListeners
0 views
Skip to first unread message
Sarah (skatc)
Nov 20, 2008, 7:24:48 PM11/20/08
to Google Web Toolkit
It seems that when you add a ClickListener to a Hyperlink, clicking on
the produced anchor causes the listener to fire, but does not navigate
to the anchor's href. Is this intentional? Is there a way to make
the listener "return true" so that the click event bubbles up to the
anchor and opens the link after the listener fires?
the produced anchor causes the listener to fire, but does not navigate
to the anchor's href. Is this intentional? Is there a way to make
the listener "return true" so that the click event bubbles up to the
anchor and opens the link after the listener fires?
alex.d
Nov 21, 2008, 2:32:37 AM11/21/08
to Google Web Toolkit
Yes it is intentional because you have to implement HistoryListener
and do the navigation manual(due to AJAX-nature of your application).
"Do the navigation" mostly means you have to hide/show some parts of
your app. Read the manual on HistoryListener.
and do the navigation manual(due to AJAX-nature of your application).
"Do the navigation" mostly means you have to hide/show some parts of
your app. Read the manual on HistoryListener.
Reply all
Reply to author
Forward
0 new messages