Is there a place for us to see all the submitted feedback for the new extension?
I forget exactly what I submitted (I know it was kind of lengthy) and would like to re-verify it with the new update.
Is there a place for us to see all the submitted feedback for the new extension?
I forget exactly what I submitted (I know it was kind of lengthy) and would like to re-verify it with the new update.
As far as I can see, not one central location. Itâs mainly in these three threads:
A relatively quick âworkaroundâ could be, to go to your profile here in this forum and to âactivityâ. Depending on how many other posts you submitted, you could find your posts in the relevant threads relatively quickly.
Unfortunately I submitted the feedback via their survey form and not here.
Hi @MFKDGAF The new extension will arrive in the coming weeks so there will likely be another round of input once recent released.
I read that as ânext yearâ
We already had two releases of the beta version (one in October and one in November), so I see no reason to doubt that a December release is around the corner.
Hereâs a little derp in translation: Autofill
and Fill and save
. I think a single form of the word should be used. I believe Fill
is the right form, as thatâs used in the button too (when itâs available, ofc)!
Will the feedback actually be listed to by the developers? I along with other from Reddit submitted feedback for the new iOS app about some broken features and that seemed to be ignored and wasnât fixed until 3 months after its global release.
I would support such a change in terminology. For one, it would remove the common misunderstanding that âautofillâ means the same thing as â(auto)fill on page loadâ â which it doesnât.
@Micah_Edelblut The implementation of the credit card form detection does appear to be buggy, after all. For a credit card form using form fields as described in this post, the beta browser extension (2024.11.9991) does not show any credit cards in the âAutofill Suggestionsâ section.
@Micah_Edelblut Hereâs an another example of failure to display Identity items as Autofill Suggestions, even though the web page clearly contains form input fields for Identity data (a form that I was ultimately able to autofill by searching for the Identity item and manually triggering the autofill function in the kebab menu):
It doesnât make sense that the Identity fields were detected when autofilling, but not detected when deciding whether to display Identity items in the Autofill Suggestions list.
Thanks for these examples! Iâll pass them along to the team.
Thank you everyone for testing the extension preview and providing feedback to the team. This week, Bitwarden will be submitting updates to the extension stores for all browser, including the UI update. As such, we encourage you to resume using the primary Bitwarden app, rather than the beta listing, which will not continue to receive updates.
Thank you again for your support and feedback!
@Micah_Edelblut Does that mean that between now and the when the new extension becomes available in app stores, bug reports for 2024.11.9991 will be accepted on Github (instead of issues being immediately closed because it is not a production version)?
If you are still not accepting bug reports for 2024.11.9991 on Github, then I would recommend keeping this thread open until the production version is available in app stores.
The new feedback thread is linked below (alternatively, you can create specific feature requests or post formal bug reports in the appropriate locations).