Cesar Gonzalez

We worked to solidify MV3 in Chrome first due to the hard deadline that Google set for sunsetting MV2. The process for that implementation was approached in a backwards compatible...

Note to reviewers: These feature flags are obsolete now, as their usage within the extension has been removed entirely as of the `v2024.2.0` release. This PR just cleans up those...

@withinfocus The client side removal of the feature flag will be introduced with the upcoming release, `v2024.2.0`. The removal of this flag is present here - https://github.com/bitwarden/clients/pull/7642 I can definitely...

@withinfocus @trmartin4 Are we in a good position to merge this change in? Just looking to clear the Jira ticket for this task.

Fantastic thank you Matt! As soon as an approval is provided, I'll make sure this gets merged in.

@jflaflamme2 @aaron-mota Interesting, I'm not able to replicate this behavior in either regard... including attempting to replicate this as described by users in other websites/browsers. The original issue reported in...

@bigric68 As I mentioned in my previous post, still not able to replicate on my side. Have you tried turning off the inline menu, as I suggested above? I'm trying...

Thank you for that @aaron-mota Narrowing it down to that specific feature helps... still looking for a way to replicate the behavior on our side, but I'll provide an update...

I'm re-opening this issue to hopefully gather more feedback on this problem. There are two scenarios where Bitwarden might attempt to blur a field in such a manner. The first...

Ok, thank you for the context... we're still working on identifying a reason for this issue, but your feedback will help us narrow down why it might be happening.