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
On Tuesday, September 4, 2012 1:26:37 AM UTC+2, Craig Mitchell wrote:
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
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 /
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: form
action=login method=GET.../form
I don't know how to get
Is there any reason for not using just gwt HTML or somthing else with
@UiHandler(loginButton) to make a RPC-call for log in?
Ex:
UiBinder:
g:HTMLPanel
g:TextBox ui:field=username /
g:PasswordTextBox ui:field=password /
g:HTML ui:field=loginButton LOGIN /g:HTML
/g:HTMLPanel
Just for autocomplete. If you don't care about autocomplete, I'd recommend
doing it as you say with GWT RPC.
On Tuesday, 28 August 2012 22:19:37 UTC+10, Fille wrote:
Is there any reason for not using just gwt HTML or somthing else with
@UiHandler(loginButton) to make a RPC-call for log
So all this form/FormPanel mangling implies that the form 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
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
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. So
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).
I should point out that it still works great in IE and Firefox. Just not
Chrome.
On Tuesday, 3 July 2012 17:07:44 UTC+10, Craig Mitchell wrote:
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
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
+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
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 like:
Why don't you just use JAAS? You could then protect your GWT page in
web.xml, and then instruct your app server to redirect to login page if
the user is not logged in. You can also setup custom roles and permissions -
the code is largely copy/paste and rest of the stuff is declarative in your
What version of GWT are you using Viliam, form.addFormPanel() doesn't
seem to exist anymore?
On Apr 27, 12:32 am, Viliam Durina viliam.dur...@gmail.com 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
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
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 t.bro...@gmail.com wrote:
On 21 avr, 04:21, jrray jrobert...@gmail.com wrote:
This technique would be more
On 21 avr, 04:21, jrray jrobert...@gmail.com 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
This is a useful technique, thanks. You didn't mention that
injectLoginFunction() needs to be called around the same time as
form.setAction(...).
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
20 matches
Mail list logo
