Just thinking. When right-clicking a Hyperlink, which starts a new
instance of the app in a separate window/tab, how would one figure out the
user (that is logged in to the original instance)? I assume the new
instance starts up (onModuleLoad()) and knows nothing about the instance
from
Actually, I think the answer is here:
http://code.google.com/p/google-web-toolkit-incubator/wiki/LoginSecurityFAQ
On Monday, June 4, 2012 10:40:53 AM UTC-7, Mike Dee wrote:
Just thinking. When right-clicking a Hyperlink, which starts a new
instance of the app in a separate window/tab, how
And opening a new window is when authentication comes into play. The user
hasn't logged into the new instance of the application (opened in the new
window). Hence we are back to the original problem.
With a regular web app, this wouldn't be a problem. The state of whether
the user is logged
On Monday, June 4, 2012 12:06:42 AM UTC+2, Mike Dee wrote:
And opening a new window is when authentication comes into play. The user
hasn't logged into the new instance of the application (opened in the new
window). Hence we are back to the original problem.
With a regular web app,
I think I understand what you are saying. In this case, the app is a
medical app and there are requirements that the app timeout after a period
of inactivity (which is usually short: 15 to 30 minutes). When logging in,
an event is triggered and the app state is logged in. Currently, the
If you're using Activities and Places, you can have a link like
http://www.yourApp.com/entryPoint.html#stateInfo=something
The state information in the URL triggers the page to load to a specific
point, the exact same as this Google Groups page does. That way, opening
the link would open a
Actually, I made a mistake. The problem doesn't seem to be the
authentication (which simply checks the session). I disabled the
authentication and it still happens.
I believe this is the way GWT is supposed to work. A GWT is one page. The
going back and forward through pages is simulated
Depending on how you're implementing your hyperlinks (if they are foo
links), then you could add a method to your handler to first check if the
user is authenticated, and then forward them to the target of the link. Of
course foo links would need to be considerate of the CTRL+click, middle
Here is the confusing thing about links (HyperLink and Anchor). Picture a
simple CRUD situation where one does a search, the search results appear,
and one can click on something to be shown the details. When Hyperlink
is right-clicked, the usual options appear. If an app requires
If loading the app (when you're authenticated) doesn't bring you to the place
the URL represents, then your app is broken.
Your issue is either with auth or app initialization, not with hyperlinks.
Google Groups for instance brings you back to where you were when hitting F5.
--
You received
I set href to javascript:;. You could instead use CSS to style the
cursor to be a pointer to make it look real, but javascript:; is the
quickest and easiest.
Derek
On May 17, 7:40 am, Matthew Pocock turingatemyhams...@gmail.com
wrote:
Hi,
I have several g:Anchor elements in my UiBinder
On Thursday, May 17, 2012 1:40:39 PM UTC+2, Matthew Pocock wrote:
Hi,
I have several g:Anchor elements in my UiBinder design. I attach OnClick
handlers to these to do interesting things. In the browser, these anchors
are being rendered as a elements lacking an href attribute. When the
12 matches
Mail list logo
