Where it is not automatic, can the user guide the extension on what needs to be filled in?

Moftangiu

Hi!

Is there any possibility for the user to "teach the extension", that for a given site, Y field means Y element?

Like .. this input form means that you will put here the year of the CC expiration? Some sort of mapping?

Long story:

Some 3 years ago I raised an issue about a site (present in a few countries) where the browser extension does not complete the month and year of the expiration date of the card.

I gave details, someone from you(1Password) logged in the site, checked the payment page, confirmed the problem and told me that will be fixed sometime in the future.

I don't know if the problem is with the site or the extension but in the end, for me, the user, nothing changed.

So, after a few years in which I continued to fill in the year and month manually, I decided to try again and maybe even find another way of solving this kind of issues.

Thanks!

---

1Password Version: Not Provided
Extension Version: 2.27.1
OS Version: W11 23H2
Browser: Chrome, Brave

Dave_1P

Hello @Moftangiu! 👋

I'm sorry that you're still running into a filling issues on a website that you've previously reported. There isn't a tool that will allow you to train the 1Password extension in that way, instead 1Password in the browser using it's filling brain to detect the fields that need to be filled.

Are you able to share the address of the website in question? I can look into the issue that was filed and see if there are any updates.

I look forward to hearing from you.

-Dave

ref: dev/core/core#8220

Moftangiu

Hi!

Thanks for the clarification on training the autocomplete part of the extension.

The mentioned website can be found on 3 domains, www.emag.ro, www.emag.hu, www.emag.bg

As I mentioned, in the payment page, the autocomplete is done perfectly, except the 2 fields, month/year of the cc expiration date.

If I remember correctly, the problem has been checked on .ro variant.

Thank you!

Dave_1P

@Moftangiu

Thank you for posting the domain names. I've taken a look and I see that the issue is still open in our developer's backlog. I've let them know that you can still reproduce the issue and are eager to see us release a fix.

-Dave

ref: dev/core/core#8220

Moftangiu

Thank you @Dave_1P :)

Dave_1P

Thanks again for reporting the issue and for following up. Hopefully it can be fixed in a future update to 1Password.

-Dave

Moftangiu

Considering that after 2 years you were able to find the issue in the backlog, there is a reason to hope that it will be solved someday but considering that it's been a few years since the first report, that hope is very, very small :)

Dave_1P

I've added a comment to the internal issue, thanks again for flagging this again.

-Dave

Moftangiu

Thank you! :)

Dave_1P

👍🙂