18 Nov
2007
18 Nov
'07
6:45 p.m.
On 18/11/2007, M. Blanc <manuel.blanc(a)gmail.com>
wrote:
> <input name="17" style="position: absolute; top: -100em"
type="text"
> class="text"/>
>
> (that is, the second input tag in the first div inside the login
> form) is the culprit.
>
> Just change its type to "hidden" and Safari will ask you if you want
> to store the login data, or will fill it in if you've already saved
> it.
The suggestion will break the behavior of #defaultAction: in any
Seaside form.
What are those fields for?
These fields are there to define the default action of the form, e.g.
the callback to be triggered when ENTER is pressed while having the
focus on a text field.
If anybody finds a better non-javascript and cross browser portable
solution to this problem, we would be glad to include it with Seaside?
Maybe it would be time to replace this very old hack with something
better?
They positioned out of the screen, couldn't the
div have
style="display: none"?
Changing or removing these fields will break the desired behavior.
I also guess the input names are numbers because they
need to be
unique within the page... would it make sense to name them from
their magritte description?
This is Seaside that assigns the names.
Lukas
--
Lukas Renggli
http://www.lukas-renggli.ch