We recently migrated our very old, aging Ruby on Rails client portal to Xojo. Our clients enter a lot of the same information each time and their web browsers would store text they entered in the past. The control name was the same each time, so that worked w/no support from the application. It of course was a function of the browser.
Switching to the Xojo Web framework, since it creates new names each time for the widgets, this function no longer works. We are getting a lot of kick back on that.
Is there any way to make that work again?
I’ m not familar with Xojo web edition,
Could you store data in longtime cookies then?
Autocomplete in the browser works by recognizing text field names. The “name” of your text field in the running WE app will be the “name” given to the field in the IDE. For example…
- Create a new project, drop a WebTextField onto a page, give it the name “email”.
- Run.
- Start typing your email address into that field, and you should see autocomplete working.
If you can’t name your controls consistently, or you need the name “name”, you might try using JavaScript to set the name of the control after it’s created. Xojo does everything with “id” anyway, so that should not hurt anything.
-Brad
I wonder if it has to do with the widgets being in a container control and added dynamically? I do see the name="blah" attributes but for some reason the browser is not bringing up items that were previously entered.
You can test the container theory with a static container. Also, try that “blah” one without a container.