Autofill in login form?

Safari doesn't seem to want to remember and fill the login and
password fields of the login form for me… Does it work for you?

--
Damien Pollet


_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

> Safari doesn't seem to want to remember and fill the login and
> password fields of the login form for me… Does it work for you?

As far as I know Safari only remembers form fields if the whole URLs  
matches exactly.

Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch



_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On 18 Nov 2007, at 08:58, Lukas Renggli wrote:

>> Safari doesn't seem to want to remember and fill the login and
>> password fields of the login form for me… Does it work for you?
>
> As far as I know Safari only remembers form fields if the whole URLs
> matches exactly.

If that were the case,

        http://localhost:8080/seaside/pier?command=PULogin

should work, but it doesn't.

(And the '?command=PULogin' in the URL above is not the culprit  
either, as you can check by switching the main class to 'PUPierMain',  
disabling view for others in the root page and going to http://
localhost:8080/seaside/pier).

Cheers
--mbj

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On 18 Nov 2007, at 01:11, Damien Pollet wrote:

> Safari doesn't seem to want to remember and fill the login and
> password fields of the login form for me… Does it work for you?

If you look at the html of http://localhost:8080/seaside/pier?
command=PULogin

the line:

<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.

Cheers
--mbj




_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On 18/11/2007, M. Blanc <[hidden email]> 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.

Just being curious…

What are those fields for?
They positioned out of the screen, couldn't the div have style="display: none"?
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?

--
Damien Pollet
type less, do more [ | ] http://typo.cdlm.fasmz.org


_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

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


_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On 18 Nov 2007, at 18:45, Lukas Renggli wrote:

Could you give an example of what gets broken in the login form by  
the suggestion?

Thanks.
--mbj




_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

Probably nothing in the login form.

The change you suggest is not related to Pier or Magritte, but to  
Seaside. Have a look at the functional Seaside Test Suite at http://localhost/seaside/tests/alltests 
  -> Default Form. I doubt that after your change this test still  
pases in Safari, FireFox, Opera and IE.

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch


_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On 18 Nov 2007, at 19:06, Lukas Renggli wrote:

>> Could you give an example of what gets broken in the login form by
>> the suggestion?
>
> Probably nothing in the login form.

Couldn't then Pier login form use a special subclass of WAFormTag  
with a different version of 'before' ?

> The change you suggest is not related to Pier or Magritte, but to
> Seaside. Have a look at the functional Seaside Test Suite at http://
> localhost/seaside/tests/alltests
>   -> Default Form. I doubt that after your change this test still
> pases in Safari, FireFox, Opera and IE.

Mmm, I remember reading a few weeks ago about an excellent browser-
dependant automated testing tool, but cannot remember its name right  
now.

Cheers
--mbj



_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

>>> Could you give an example of what gets broken in the login form by
>>> the suggestion?
>>
>> Probably nothing in the login form.
>
> Couldn't then Pier login form use a special subclass of WAFormTag
> with a different version of 'before' ?

All forms in Pier are automatically generated using Magritte.

>> The change you suggest is not related to Pier or Magritte, but to
>> Seaside. Have a look at the functional Seaside Test Suite at http://
>> localhost/seaside/tests/alltests
>>  -> Default Form. I doubt that after your change this test still
>> pases in Safari, FireFox, Opera and IE.
>
> Mmm, I remember reading a few weeks ago about an excellent browser-
> dependant automated testing tool, but cannot remember its name right
> now.

Try with this and tell me if it helps?

Name: Seaside2.8a1-lr.530
Author: lr
Time: 19 November 2007, 9:47:17 am
UUID: c57f1bd2-bcb5-4d3a-8592-d3c7b814d178
Ancestors: Seaside2.8a1-lr.529

- trying to fix default action

Cheers,
Lukas

--
Lukas Renggli
http://www.lukas-renggli.ch


_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki

On 19 Nov 2007, at 09:47, Lukas Renggli wrote:

> Try with this and tell me if it helps?
>
> Name: Seaside2.8a1-lr.530
> Author: lr
> Time: 19 November 2007, 9:47:17 am
> UUID: c57f1bd2-bcb5-4d3a-8592-d3c7b814d178
> Ancestors: Seaside2.8a1-lr.529
>
> - trying to fix default action

I've found you probably meant Firefox when you said "... only  
remembers form fields if the whole URLs matches exactly".

Regarding Safari (2 and 3) and Omniweb, the fix works great everytime.

Thanks
--mbj

_______________________________________________
SmallWiki, Magritte, Pier and Related Tools ...
https://www.iam.unibe.ch/mailman/listinfo/smallwiki