'Keep Logged In' checkbox at me.com (MobileMe)

pjrobertson

I can't seem to get 1Pwd to fill the checkbox for 'keep me signed in for 2 weeks' whenever I log in.

I've tried deleting my existing 1Pwd Login and making a new one when signing in. It registers the checkbox when creating the Login but doesn't give it a name/ID.



Looking at the me.com source, it looks like the fields are all done with Javacript, but that the checkbox has an ID 'KeepLoggedIn'. I've tried that as well as 'keeploggedin' and neither seem to work <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/sad.gif' class='bbc_emoticon' alt=':(' />

thightower

[quote name='pjrobertson' timestamp='1284799793' post='11408']

I can't seem to get 1Pwd to fill the checkbox for 'keep me signed in for 2 weeks' whenever I log in.

I've tried deleting my existing 1Pwd Login and making a new one when signing in. It registers the checkbox when creating the Login but doesn't give it a name/ID.



Looking at the me.com source, it looks like the fields are all done with Javacript, but that the checkbox has an ID 'KeepLoggedIn'. I've tried that as well as 'keeploggedin' and neither seem to work <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/sad.gif' class='bbc_emoticon' alt=':(' />

[/quote]



Hi pj



I looked at one of my logins for .me I haven't changed it in a long time, at some point 1P saved it, although it still doesn't work. My saved login had the field name "keepLoggedIn" (note lower case "k" uppercase "L" and "I") But it doesn't work either. I gave a re save a shot and it no longer grabs the field name just as you said.



So I dunno sorry, one of the team will need to comment on this one.

MikeT

Hi pjrobertson,



It appears that due to Apple using Javascript to handle the state of the checkbox and no name= value to the checkbox, 1Password is unable to work with it. We are investigating ways to handle these better for a future release.



You’ll need to either turn off autosubmit for the site to check the checkbox yourself each time you fill in, or use the Go and Fill to have 1Password log you in automatically.



To turn off the autosubmit for the site:[indent]

Open 1Password, select the site's Login item, press Command+E (or press the edit button) to edit it, and change its Submit option to Never.[/indent]

thightower

[quote name='MikeT' timestamp='1284829479' post='11429']

Hi pjrobertson,



It appears that due to Apple using Javascript to handle the state of the checkbox and no name= value to the checkbox, 1Password is unable to work with it. We are investigating ways to handle these better for a future release.



You’ll need to either turn off autosubmit for the site to check the checkbox yourself each time you fill in, or use the Go and Fill to have 1Password log you in automatically.



To turn off the autosubmit for the site:[indent]

Open 1Password, select the site's Login item, press Command+E (or press the edit button) to edit it, and change its Submit option to Never.[/indent]

[/quote]





Hmm I tried no auto submit by pressing the option key while filling my info and its a no go for me.



Edit : Also tried the change to never submit and it doesn't work either <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/sad.gif' class='bbc_emoticon' alt=':(' />, oh well for me I don't log in that often. Sorry PJ



Guess its a manual input for the keep signed in portion, at least in my trials.

pjrobertson

Thanks for the updates.



I thought it'd be Apple's use of javascript as opposed to normal HTML.

I'm surprised nobody else has brought it up, me.com can't be all that popular I guess <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/tongue.gif' class='bbc_emoticon' alt=':P' />



My only idea for the time being - which isn't very robust - would be to use something like applescript and keystroke 'Tab' then 'space' before hitting 'enter'.



Hopefully you guys can come up with a clean solution <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />

khad

Yeah, at this time you will have to manually check the box when logging in. I think what Mike was saying was that if you disable autosubmit for your Me.com login, you will have the [i]opportunity[/i] to check that box before it is submitted. Unless Apple redesigns the site, there is not much else we can do. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/sad.gif' class='bbc_emoticon' alt=':(' />



We are looking into improving this in the future.

thightower

Yep I should have gotten that one,



Can you tell I pushed back from the Mac this weekend, I did manage to watch a few good movies though.



Thanks khad for switching the light bulb on in my head. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/smile.gif' class='bbc_emoticon' alt=':)' />

khad

You wouldn't happen to have a spare, eh? I could use a new one today. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_smile.png' class='bbc_emoticon' alt=':-)' />

Ward

It's been nearly three months since this thread appeared. "Keep Logged In" is still a problem. I'm posting this reply to add a little more detail.



When I saved fresh Me.com logins in both OmniWeb and Safari, five fields are saved:

[list]

[*]a Text field with no field name or value

[*]username & password - fortunately these work

[*]a Checkbox field with no field name and a checked value - mostly likely came from "Keep Logged in"

[*]another Text field with no field name and an underscore (_) value

[/list]

-- Ward

khad

Unfortunately, Apple is not providing a name in the code for the checkbox. Without this we cannot reference it to toggle it.



The only option would be to blindly toggle all checkboxes which would have disastrous effects on other logins. <img src='http://forum.agile.ws/public/style_emoticons/<#EMO_DIR#>/skype_sadsmile.png' class='bbc_emoticon' alt=':-(' />



I'm sorry I don't have a better answer but we are at the mercy of Apple in this regard I believe. Of course, that has never stopped us before and we are making some great improvements to our form filling code which may very well mitigate this situation in the future. I'm sorry I don't have a time frame for you.