Browser Extension 4.5.6 won't fill disabled fields

Greetings @pinskerj,

We'll have to consider this carefully. While I can see why filling twice has the potential to be frustrating we also have reports where filling has resulted in 1Password filling disabled fields that can then not be undone by the user because the fields are disabled. Of the two the latter seems worse to me. We do want to make 1Password as intelligent as we can though.

Now saying that I'm seeing somewhat different behaviour after saving a test Login item and trying to fill. As the check to see if a field is disabled is a runtime check and the checkbox is the first item filled, being the first input item on the page, the other two fields are enabled once the extension attempts to fill them. I had a little trouble with the password field as it seems the site might be using two fields layered on top of each other but with a small edit to the Login item everything indicates that the checkbox and two fields were all successfully filled from one fill instruction. Of course I can't easily test this as I'm not about to cause a failed login attempt on a site like that.

The first test is to see what you happens if you create a new Login item by following the steps outlined on our page How to save a Login manually in your browser. For testing you will probably want to turn submit after filling off either just for this Login item (the submit option becomes visible when you edit the Login item inside of 1Password) or temporarily via the general 1Password preference in the Browsers tab. After saving a new Login item and with no changes to the data stored in the web for details filling would tick the checkbox and then fill in the username, seemingly leaving the password unfilled. What I then noticed though was there are multiple fields stored in the Login item under the web form details section. One of those fields is titled password-clear and stored the text DS Logon Password. If I deleted the text (it's important to leave the field) and saved then when I tried filling a freshly loaded copy of the login page it ticked the checkbox and then filled both fields.

I was testing 1Password for Mac 6.3.2 with Vivaldi. It may be we're seeing a difference in version or browser and I'll happily see what happens with a different configuration if this is the case.