-
Notifications
You must be signed in to change notification settings - Fork 1.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[PM-12352] Incorporate the minimum amount of changes to ensure OverlayBackground instantiates on init of the extension #11134
base: main
Are you sure you want to change the base?
Conversation
…kground instantiates on init of the extension
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## main #11134 +/- ##
=======================================
Coverage 33.19% 33.19%
=======================================
Files 2780 2780
Lines 86410 86393 -17
Branches 16468 16462 -6
=======================================
Hits 28680 28680
+ Misses 55445 55429 -16
+ Partials 2285 2284 -1 ☔ View full report in Codecov by Sentry. |
New Issues
Fixed Issues
|
Converting this to a draft to ensure we don't accidentally merge the work in. |
🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-12352
📔 Objective
A number of issues are being reported in relation to autofill behavior for the extension. These include the following:
Replicate of the behavior described in these tickets is difficult to do, but more than likely the core issue revolves around how we are handling initialization of the
OverlayBackground
andTabsBackground
classes within theMainBackground
class of the extension.These two problematic classes are being instantiated behind a feature flag, which depends on config data from the server. The behavior described by end users points to some issue with triggering the behavior in those classes.
To resolve this, we need to pull the instantiation of those classes into the constructor of the
MainBackground
class, as was originally done. This will remove the potential of initializing the LegacyOverlayBackground entirely, but incorporating this fix represents the most logical course of action to resolve these issues that users are experiencing.We will be petitioning the community to verify that this fixes their issues through a side-loaded artifact. If this indicates a resolution for the majority of users, we will begin discussions on incorporating these set of changes as a hotfix for the extension.
⏰ Reminders before review
🦮 Reviewer guidelines
:+1:
) or similar for great changes:memo:
) or ℹ️ (:information_source:
) for notes or general info:question:
) for questions:thinking:
) or 💭 (:thought_balloon:
) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion:art:
) for suggestions / improvements:x:
) or:warning:
) for more significant problems or concerns needing attention:seedling:
) or ♻️ (:recycle:
) for future improvements or indications of technical debt:pick:
) for minor or nitpick changes