Cesar Gonzalez

I encountered this issue as well and found that the problem I was having in particular was with the initialization call for the sticky sidebar being placed within a $(document).ready()...

@C10H12N2O @cgarren I've reviewed the problems reported in this ticket, and have verified that this issue no longer exists when autofilling forms on these pages. It appears that at some...

@wnelson03 @andrewda Hello, I'm a Front End Engineer with Bitwarden. Todd asked me to take a look at this community PR and help identify a path forward for merging the...

@wnelson03 > Unless the stored TOTP secret was completely invalid... Yeah, this is the scenario that I found was causing issues. You're right in saying that if for some reason...

@andrewda Thank you once again for your contribution! QA has tested and approved your changes. We will be merging this work into the `Browser v2023.7.0` release, and the updated behavior...

@jjspace As of this moment, we don't have a definitive reason for why this is happening or how to fix it. That said, I dug around a bit to see...

@joshuataylor Thanks for providing this bug report. We are aware of some issues present with the inline menu on websites that handle DOM re-hydration through AJAX (Such as in the...

Thanks for those examples. We do have a PR that intends to resolve a different issue that might also help to resolve this lingering DOM element issue. https://github.com/bitwarden/clients/pull/7952 Beyond that,...

This issue is a duplicate of https://github.com/bitwarden/clients/issues/7837 and https://github.com/bitwarden/clients/issues/8030. The reason this happens is due to our usage of Custom Elements, and a know bug within Firefox that prevents referencing...

I've taken a look at this and identified a path forward on resolution of the issue. If we render the UI elements for the overlay as a `` with an...