Have the following things been fixed in 1Password 4?
I've been using 1Password 3 for quite a while and in that time have become aware of more than a few of its shortcomings. I was wondering which of those shortcomings have been addressed in 1Password 4.
Here's the few that I can recall right now, in no particular order:
1) Inability to tab into the "Field Value" column from the "Field Name" column after creating a new Field.
2) Overwhelmingly North American localisation for the Wallet Items, eg. Social Security Number, Hunting License and especially Bank Account types such as Checking and Line Of Credit
3) "Display in Browser" status only visible for an item if you enter Edit mode.
4) "Password" field in Login items truncated owing to the (more often than not) invisible existence of an unused "Drop an image here to customize" placeholder, necessitating the constant widening of the 1Password window to allow the whole password to be displayed.‡
5) Complete inability to edit multiple Login items at once - this is a big one.
6) Possible bug that causes the OS to enter, "secure keyboard mode" whenever 1Password is Hidden, even if it's locked. This interferes with Typinator's functionality, for example. The only workaround is to quit 1Password.
7) Possible bug that causes folders containing nested folders to always display their contents after every launch. For example, if there is a folder, "Banking", containing folders "Savings A/Cs" and "Checking A/Cs", a toggle appears next to the, "Banking", folder, allowing the user to hide or show the nested folders. If this toggle is set to "hide", the toggle will be automatically set to "show" after a quit and re-launch.
8) The apparent complete lack of purpose of the "Checkbox" Field Type, except perhaps as a historical record of a setting chosen during the registration process for a new website.
Like I say, those are just the ones I can think of right now. Hopefully those of you using the new version will be able to advise which of these things have been fixed or are no longer an issue for some other reason.
Look forward to the input.
24hpp
‡ Copying the field isn't always appropriate, so a visual inspection of the password is necessary, usually by pressing the Option key. For example, OS X 10.8 doesn't allow you to copy and paste passwords into HFS Encryption password dialogues - they must be entered manually. Some websites I've encountered also exhibit this characteristic.
Comments
-
(6) doesn't appear to be fixed yet, according to the thread here.
0 -
You can download a demo version of 1P 4 and try it; it'll use your 1P 3 data without issue, and you can go back to 1P 3 at any time.
(1) and (4) are fixed, at least. (5) is effectively fixed because you can add multiple Web sites to a single login item.
(8) is useful for the common "remember me"/"stay signed in" option.
0 -
You can download a demo version of 1P 4 and try it; it'll use your 1P 3 data without issue, and you can go back to 1P 3 at any time.
Guess I may do that. Thanks.
Glad to hear (1) and (4) are fixed.
Not sure what you mean by (5) being "effectively fixed"—can you alter the details of multiple items simultaneously? That doesn't appear to be what you've described.
(8): This is what it was supposed to do in 3, but didn't. Are you saying that if you create a Checkbox item with the Field Name corresponding to the text adjacent to the checkbox in the website, it'll apply the setting you assign to that Checkbox item to the website's checkbox automatically when applying login details? If so, then that's great. I'm surprised though, because when I last discussed this with Agilebits' support, it was explained as being a very difficult thing to do.
0 -
(8) You're right — I just assumed the feature worked, but I constructed a simple test page and it doesn’t, still. The sites where I thought it worked, it turns out they're using cookies. I can’t really think of why this would be so difficult to do, but I can imagine why this has fallen down the list a bit.
0 -
I imagined (5) was a problem because you were using the same login details for multiple sites. Instead, you can add multiple sites to a single login, which is less error-prone in any case. If you're trying to do anything else, perhaps you should make an explicit feature request describing your use case.
0 -
Re: (8)
I can’t really think of why this would be so difficult to do, but I can imagine why this has fallen down the list a bit.
Then I think I'm justified in asking, why does it still exist?
Re: (5). I'm talking about editing multiple entries simultaneously, eg. amending the email address associated with multiple accounts if you have to change it (eg. when a provider goes down, as happened to me).
If you're trying to do anything else, perhaps you should make an explicit feature request describing your use case.
Certainly did, a long time ago. All the points I listed in my original post, bar (6) and (7), were submitted to Agilebits well prior to the release of 1P4.
0 -
Hi guys,
1) Inability to tab into the "Field Value" column from the "Field Name" column after creating a new Field.
Definitely fixed.
2) Overwhelmingly North American localisation for the Wallet Items, eg. Social Security Number, Hunting License and especially Bank Account types such as Checking and Line Of Credit
Not fixed and not likely to be so for a while. We are trying to find a way to use localization to handle this but the further we go on this; the more difficulties we find because of different terms in different country, which then breaks how the interface looks because the term is too long, and so on.
We'll figure something out but for now, we have other priorities we need to work on.
3) "Display in Browser" status only visible for an item if you enter Edit mode.
Not fixed, we'll work on a different way to show this in the future.
4) "Password" field in Login items truncated owing to the (more often than not) invisible existence of an unused "Drop an image here to customize" placeholder, necessitating the constant widening of the 1Password window to allow the whole password to be displayed.
Not sure what you mean? We don't use that placeholder anymore. Based on what nriley said, it appears to be fixed. :)
5) Complete inability to edit multiple Login items at once - this is a big one.
Nope, there's no bulk editing in 1Password 4. You can only edit one item at a time.
6) Possible bug that causes the OS to enter, "secure keyboard mode" whenever 1Password is Hidden, even if it's locked. This interferes with Typinator's functionality, for example. The only workaround is to quit 1Password.
We tried everything but this is a system action we can't control, like what roustem said.
7) Possible bug that causes folders containing nested folders to always display their contents after every launch. For example, if there is a folder, "Banking", containing folders "Savings A/Cs" and "Checking A/Cs", a toggle appears next to the, "Banking", folder, allowing the user to hide or show the nested folders. If this toggle is set to "hide", the toggle will be automatically set to "show" after a quit and re-launch.
It appears to work fine here for me. Not able to reproduce it based on what you said. I collapsed the folder containing the nested folder, restarted 1Password and it stay collapsed.
8) The apparent complete lack of purpose of the "Checkbox" Field Type, except perhaps as a historical record of a setting chosen during the registration process for a new website.
I don't understand what you mean here. Do you mean that 1Password is not setting the checkbox properly on the site? It should be but it may be inaccurate. If you find sites where 1Password can't check the box, let us know, and we'll investigate it.
Then I think I'm justified in asking, why does it still exist?
We save all the details we can when you ask 1Password to auto-save the data. As we continue to improve our extensions, eventually, those data will be used in the future if when we do fix the issues with the checkbox.
0 -
1) Inability to tab into the "Field Value" column from the "Field Name" column after creating a new Field.
Definitely fixed.
Great news. One down.
2) Overwhelmingly North American localisation for the Wallet Items, eg. Social Security Number, Hunting License and especially Bank Account types such as Checking and Line Of Credit
Not fixed and not likely to be so for a while. We are trying to find a way to use localization to handle this but the further we go on this; the more difficulties we find because of different terms in different country, which then breaks how the interface looks because the term is too long, and so on.
That's not good news.
3) "Display in Browser" status only visible for an item if you enter Edit mode.
Not fixed, we'll work on a different way to show this in the future.
Okay.
4) "Password" field in Login items truncated owing to the (more often than not) invisible existence of an unused "Drop an image here to customize" placeholder, necessitating the constant widening of the 1Password window to allow the whole password to be displayed.
Not sure what you mean? We don't use that placeholder anymore. Based on what nriley said, it appears to be fixed.
Anyone who's used 1P 3 will know what I mean. If you don't use that placeholder anymore, it shouldn't be an issue. That's two.
5) Complete inability to edit multiple Login items at once - this is a big one.
Nope, there's no bulk editing in 1Password 4. You can only edit one item at a time.
That's not good news either. One of your own support guys on Goodness knows what forum you were using at the time (maybe you should spend less time migrating your forums?) admitted he lamented the lack of such a thing on occasion.
6) Possible bug that causes the OS to enter, "secure keyboard mode" whenever 1Password is Hidden, even if it's locked. This interferes with Typinator's functionality, for example. The only workaround is to quit 1Password.
We tried everything but this is a system action we can't control, like what roustem said.
Please pass this on to the Typinator devs who, as the last respondent on that thread points out after Roustem's post, place the blame squarely on 1Password.
7) Possible bug that causes folders containing nested folders to always display their contents after every launch. For example, if there is a folder, "Banking", containing folders "Savings A/Cs" and "Checking A/Cs", a toggle appears next to the, "Banking", folder, allowing the user to hide or show the nested folders. If this toggle is set to "hide", the toggle will be automatically set to "show" after a quit and re-launch.
It appears to work fine here for me. Not able to reproduce it based on what you said. I collapsed the folder containing the nested folder, restarted 1Password and it stay collapsed.
If this is genuinely fixed in 1P4, then that's three.
8) The apparent complete lack of purpose of the "Checkbox" Field Type, except perhaps as a historical record of a setting chosen during the registration process for a new website.
I don't understand what you mean here. Do you mean that 1Password is not setting the checkbox properly on the site? It should be but it may be inaccurate. If you find sites where 1Password can't check the box, let us know, and we'll investigate it.
nriley above has found through testing that this doesn't work. Maybe you could ask him which site he was using for his test?
Then I think I'm justified in asking, why does it still exist?
We save all the details we can when you ask 1Password to auto-save the data. As we continue to improve our extensions, eventually, those data will be used in the future if when we do fix the issues with the checkbox.
So I was right: currently it's nothing more than a historical record.
Well, at least I know where I stand. Thanks for the comprehensive reply.
0 -
It didn't work on several common sites (e.g., iCloud) but just to eliminate any possibility that the site was the problem, I created a very simple Web page which contained only username, password and checkbox fields. 1Password failed on this page.
Here it is:
You can see that it saves correctly:
but filling only fills the username/password fields, not the checkbox.
Hope that helps.
0
