It's the very basic browser feature, without any extensions. Just click twice on input, or start typing in a field you have had already submitted before, and previous values will be offered for you. This is standard feature of FF, Chrome, and I guess some more browsers.
On Dec 23, 5:59 pm, Michael W <[email protected]> wrote: > Skrat, > > Are you talking about the Google Autofill, Roboform Autofill feature? > Which means browser remembers your form entry and next time once you > click Autofill from browser, the form is refilled. > > Or just want to prepopulate your form processed by your program. > > On Dec 22, 9:22 am, skrat <[email protected]> wrote: > > > > > Hmm, that script inserted forms problem, might be fatal. > > > I guess security should be handled by browsers, and all non-XHR forms > > are leveraging this feature. please > > > On Dec 22, 3:07 pm, Thomas Broyer <[email protected]> wrote: > > > > On Dec 22, 2:53 pm, skrat <[email protected]> wrote: > > > > > Hi all, > > > > > I am curious about, how can one enable, or force a browser to remember > > > > value inside text inputs (TextBox) values. In browsers it basically > > > > works when you submit a form, then all values are remembered, and next > > > > time you open that form, you will be provided with autocomplete box. > > > > All major browsers works like this. > > > > > Since in apps, that decides to use XML, JSON or GWT RPC, values in > > > > forms are actually not submitted, and thus not remebered. We just read > > > > those values and don't do any submit, we do XHR instead. > > > > > Any ideas how to get back this very useful browser feature? > > > > This is a hack but if you really want it: > > > - use a form > > > - expose a GWT method as a JS 'global' function (e.g., > > > myExportedGwtMethod) > > > - set the form's action to call the exported method > > > ("javascript:myExportedGwtMethod()") > > > - do your XHR/RPC call from within your exported GWT method > > > > Note that (I'm almost sure this isn't the case, for any form except > > > login forms, but just in case) this might only work if the form is > > > actually part of the original HTML markup of the page (i.e. not > > > inserted by script). > > > > It's not worth it IMO; except for login forms eventually, even if it > > > goes against the most basic security rules, just because of the > > > enhanced UX. -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
