Feature Request: Support Universal Autofill in apps created using WebCatalog

I'd like to +1 Ian's request. Having hopped on the Sonoma bandwagon I was hoping these apps made by Safari would be able to work with 1Password's auto-fill (I was really hoping that Safari extensions would come over for free but they don't – so I filed FB12487876 requesting that). It now makes sense why 1Password's app auto-fill doesn't work but I really really really want it to work.

I've used Unite and Fluid in the past with varying levels of success but really yearned for a Safari solution. Now that we have it, not being able to use 1Password is a huge killjoy to using it.

I hope that you all can prioritize supporting new features of macOS and get this built. Thanks!

@jsorge

Thank you for the feedback, I've passed along your request to the team. 🙂

-Dave

ref: PB-34131847

Thanks @1P_Dave -- I appreciate the full explanation, and the honesty, and appreciate that you have to prioritise your workload based on customer demand.

I did originally ask for this to be reinstated as an option in settings that you give your customers, with the advice that downgrading Universal Autofill to supporting ad-hoc signatures could potentially compromise security, and then it is our choice rather than yours to take that risk. That would be a simple solution -- but that was not responded to.

I completely agree with @jsorge. With Apple now providing support for browser-based apps I would really really really hope you will support these. 🤞🙏

It might be a more niche feature right now, but when the ability to do this is released with Sonoma demand from your customers will surely increase.

@1P_Dave BTW -- from my perspective Universal Autofill working with ad-hoc signatures was not a "bug" as you call it. It was a killer "feature", that then got removed without proper explanation.

That was the annoyance for me. 😊

Thank you again for the feedback and suggestions, all of your comments have been passed along to our product and development teams. 🙂

-Dave

+1 from me for support of the Credential Provider Extension API on macOS (just like you do on iOS and iPadOS).

Main reason for me is the native implementation from Apple is plentifold faster than using the buggy 1Password Extension for Safari.

Please.

Thanks for the input @ianto I've noted it internally. Nice to talk with you again.

@1P_Dave @1P_Tommy I made a community account just to comment on this. I've loved 1Password ever since I switched over from Dashlane and evangelize it to friends and colleagues!
The only single complaint I have is the lack of support for working with WebCatalog.

As a software engineer, I get it -- backlogs get swamped, tickets accumulate and pile up. On the other hand, the work needed to support this feature (allow ad-hoc signatures) is like a 1/2 pointer, maybe 3 points if you factor in user warning modals, writing tests, and manual testing.

I would really love to see this feature get implemented as it's the only stain on an otherwise spectacular product!

@wey

Welcome to the community! 😊

Thank you for the feedback, I've passed along your request and comments to the team internally.

-Dave

@wey -- Thank you thank you for chipping in your comments. I'm a total 1Password evangelist as well, but I feel like this issue has been overlooked as niche, but I know for sure there are lots of others who have the same issue, but just don't comment. So thank you. 😊