Cesar Gonzalez

Thank you for the feedback everyone. [A fix for this issue is now in review](https://github.com/bitwarden/clients/pull/8214), and should be available within the `v2024.3.1` extension release. The workaround for this problem, until...

The next version is `v2024.3.1`, which has been submitted to all web stores. The extension should be released upon approval, and is already appearing within Chrome and Edge. Mozilla takes...

Hello everyone, I've taken some time to review this issue and attempted to dig into a possible reason for why it might be happening. I'm still not sure on the...

@Lippiece Thanks for that, though we've seen reports of the issue appear in a regular manner... at least once a month since first being reported, though usually not by a...

@RafaelKr Hello, I'm a Front End Engineer with Bitwarden. Thank you for providing this contribution, even if it had to be reverted due to the experienced performance issues. Todd asked...

@RafaelKr Thanks for providing that context, it'll be helpful as our team continues to work through improving the autofill behavior. I like your idea for implementing some kind of watcher...

@jff @mikibakaiki I've been asked to re-review this proposal and continue discussion on the feature request. I think that this feature request is interesting, and definitely worth pursuing. I know...

This PR is reverted, but was used in re-working the ShadowDOM support with the PR linked above your comment. If a specific website isn't working, then likely its a different...

A bug was introduced where ShadowDOM elements that contain any child nodes are ignored. This has been resolved in a recently merged PR - https://github.com/bitwarden/clients/pull/9063 I'm willing to bet that's...

That fix doesn't relate to MV3 specifically, and any updates to the extension moving forward for the moment will be cross-version compatible with MV2 on FF/Safari and MV3 on Chrome....