I've made a login form in gwt with a textbox, a passwordtextbox and a
button.
everything is fine, but browser isn't asking me to store the password.
Do I have to make the button a html submit input and create another
page? or is there a way to tell the browser this is a login form?
th
I think you must use a form
panel<http://google-web-toolkit.googlecode.com/svn/javadoc/2.3/com/google/gwt/user/client/ui/FormPanel.html>
if you want the browser ask store some input.
2011/7/20 Paolo Inaudi
> I've made a login form in gwt with a textbox, a passwordtextbox
On Jul/20/2011 18:03, Paolo Inaudi wrote:
I've made a login form in gwt with a textbox, a passwordtextbox and a
button.
everything is fine, but browser isn't asking me to store the password.
Do I have to make the button a html submit input and create another
page? or is there a way t
Reposting to mailing list.
Original Message
Subject: Re: login form
Date: Thu, 21 Jul 2011 18:56:09 -0700 (PDT)
From: Josh
To: "Ionuț G. Stan"
These links touches on it. If your forms are not in the pages HTML
then browsers will not recognize them as a login pass
Hello,
I'm trying to replicate browser autocomplete on a login form. For
example, every time you go to the login page, I'd like the username
and password field to be prepopulated with the username/password you
used last. Not only that, but if you clear the username and double
click
If you want to have browsers auto-complete username/password in your
application's login form, you probably did (*I* did) this:
1. follow recommandations from
http://code.google.com/p/google-web-toolkit-incubator/wiki/LoginSecurityFAQ,
i.e. your form and fields have to be in the original m
y the applicationCreator), in
a div that makes them hidden (use visibility and not display: none).
>From GWT, re-visibilize them if you need em. That should work.
On Nov 21, 11:04 pm, tieTYT <[EMAIL PROTECTED]> wrote:
> Hello,
>
> I'm trying to replicate browser autocomplete on a login
From GWT, re-visibilize them if you need em. That should work.
>
> On Nov 21, 11:04 pm, tieTYT <[EMAIL PROTECTED]> wrote:
>
> > Hello,
>
> > I'm trying to replicate browser autocomplete on a login form. For
> > example, every time you go to the login page, I
t; > bootstraps GWT (normally auto-generated by the applicationCreator), in
> > a div that makes them hidden (use visibility and not display: none).
> > From GWT, re-visibilize them if you need em. That should work.
>
> > On Nov 21, 11:04 pm, tieTYT <[EMAIL PROTECTED]>
mal modus operandi, the boxes are added dynamically by the
> > > javascript.
>
> > > The solution is to have the boxes in the static HTML file that
> > > bootstraps GWT (normally auto-generated by the applicationCreator), in
> > > a div that makes them
's normal modus operandi, the boxes are added dynamically by the
> > > > javascript.
>
> > > > The solution is to have the boxes in the static HTML file that
> > > > bootstraps GWT (normally auto-generated by the applicationCreator), in
> > > >
On 23 nov, 10:57, tieTYT <[EMAIL PROTECTED]> wrote:
> I've already tried doing this and it doesn't solve the problem at
> hand. IE(s) don't seem to ask you to save the username/password when
> you do this. Here are the things I've tried with your idea:
> Wrapping these inputs in a form in the
Thanks, that helped. For some reason adding a submit handler works
but formPanel.submit() didn't. Also, I didn't know you could define
the type of a button tag. That may have made all the difference.
On Nov 23, 6:28 am, Thomas Broyer <[EMAIL PROTECTED]> wrote:
> On 23 nov, 10:57, tieTYT <[EMAI
ield so I can call back into
my instance from doLogin().
Hope this helps others trying to use this technique.
On Feb 26, 10:21 am, Thomas Broyer wrote:
> If you want to have browsers auto-complete username/password in your
> application's login form, you probably did (*I* did
On 21 avr, 04:21, jrray wrote:
>
> This technique would be more convenient if "doLogin" wasn't a static
> method.
>
> I tried to change to non-static, such as:
>
> private native void injectLoginFunction() /*-{
> $wnd.__gwt_login = th...@com.example.myapp.client.app::doLogin
> ();
>
Thanks. I see now that this is discussed in the GWT FAQ and I
understand why my attempt at using "this" in a callback doesn't work.
On Wed, Apr 22, 2009 at 7:17 PM, Thomas Broyer wrote:
>
>
>
> On 21 avr, 04:21, jrray wrote:
>>
>> This technique would be more convenient if "doLogin" wasn't a s
There is even a simpler solution without using JSNI at all. Set the
form's action to just "javascript:;" and put the login logic to the
form's submitHandler:
FormPanel form =
FormPanel.wrap(Document.get().getElementById("login"), false);
form.setAction("javascript:;");
form.addFormPanel(new
What version of GWT are you using Viliam, form.addFormPanel() doesn't
seem to exist anymore?
On Apr 27, 12:32 am, Viliam Durina wrote:
> There is even a simpler solution without using JSNI at all. Set the
> form's action to just "javascript:;" and put the login logic to the
> form's submitHandler
Actually, just confirming this, all the solutions presented here *do
not* work in webkit browsers (chrome, safari), right? Looks like it
works in firefox ok. I haven't found any alternative solutions in my
searches, so seems like our options are still:
1) Use methods presented here, but won't wo
On May 6, 4:45 pm, markww wrote:
> Actually, just confirming this, all the solutions presented here *do
> not* work in webkit browsers (chrome, safari), right? Looks like it
> works in firefox ok. I haven't found any alternative solutions in my
> searches, so seems like our options are still:
>
+1 on that - if you can, don't make the same mistake!
We also put in some hacks to get the login page "GWT controlled". In
retrospect, it was a poor decision. Its much cleaner to assume that the GWT
page is only reachable once authenticated.
--Sri
P.S. And as luck would have it, as I typed this e
Thanks for the heads up, was just going down that route.
I'm fine with using a regular html form, just not sure where to put
it. Twitter has a login form on their main splash page, which is
ideal. I am thinking I could do the same. My main page is already a
jsp page. I can do something
m, just not sure where to put
> it. Twitter has a login form on their main splash page, which is
> ideal. I am thinking I could do the same. My main page is already a
> jsp page. I can do something like:
>
> // myproject.jsp
>
> ... login text fields ...
>
>
>
Apparently in recent Chrome the HTML form elements need name attributes for
the setAction()-approach to work.
--
You received this message because you are subscribed to the Google Groups
"Google Web Toolkit" group.
To unsubscribe from this group and stop receiving emails from it, send an email
The submitting to a javascript URL was working great. However, Chrome has
decided to stop working (currently on version 20.0.1132.47 m).
And the only thing that seems to make it work, is doing a submit straight
to the servlet from the login form, which is a real pain (and a major
change
1132.47 m).
>
> And the only thing that seems to make it work, is doing a submit straight
> to the servlet from the login form, which is a real pain (and a major
> change).
>
> Anyone else notice that Chrome has stopped working for auto complete?
>
>
> On Friday, 7 May 2010 0
So all this form/FormPanel mangling implies that the tag is required
to be present in the original markup yes? Otherwise, one could just have
the username and password fields in the orig. markup and manually submit to
server by trapping an onclick to a simple button and then construct the
req
Correct. The form must be the thing doing the submit.
Although, as I pointed out, Chrome stopped working with a JavaScript call
to trigger the form to submit. So I now let the form do its own submit.
All I use GWT for is positioning the widgets.
It sucks, but it's the only way I could get it
Gotcha. Thanks much for the quick reply and good info! - j
On Monday, August 27, 2012 10:47:18 PM UTC-7, Craig Mitchell wrote:
>
> Correct. The form must be the thing doing the submit.
>
> Although, as I pointed out, Chrome stopped working with a JavaScript call
> to trigger the form to submit.
e user.
}
Or is it just for autocomplete?
Den torsdagen den 26:e februari 2009 kl. 18:21:23 UTC+1 skrev Thomas Broyer:
>
> If you want to have browsers auto-complete username/password in your
> application's login form, you probably did (*I* did) this:
> 1. follow recommand
Or is it just for autocomplete?
>
>
>
> Den torsdagen den 26:e februari 2009 kl. 18:21:23 UTC+1 skrev Thomas
> Broyer:
>>
>> If you want to have browsers auto-complete username/password in your
>> application's login form, you probably did (*I* did) this:
&g
forms??? thats so 2000s. use event based design like u mentioned and submit via
restful. using post get or update or whatever ur backend or api require.
sometimes u need to use forms for file xfer or other specialized means. just
keep in mind that not using forms can and does break usability / a
I'm a little confused. The way Tomas showed (above) used to work with
Autocomplete, however, Chrome decided it wasn't going to play nice with
that any more.
The only solution I could find was to do a login with a form. Eg: ...
I don't know how to get Autocomplete working in Chrome with GWT RP
If you (or anyone) can offer a solution not using a form, I'm all ears.
> As, yes, forms are so 2000s, and I would rather not use them.
>
Best way to do auth IMO is to either:
- redirect to a "standard login form" (like Google does, for instance
for Groups; have a
34 matches
Mail list logo
