Skip to content
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

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from

Conversation

cagonzalezcs
Copy link
Contributor

@cagonzalezcs cagonzalezcs commented Sep 18, 2024

🎟️ 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 and TabsBackground classes within the MainBackground 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

  • Contributor guidelines followed
  • All formatters and local linters executed and passed
  • Written new unit and / or integration tests where applicable
  • Protected functional changes with optionality (feature flags)
  • Used internationalization (i18n) for all UI strings
  • CI builds passed
  • Communicated to DevOps any deployment requirements
  • Updated any necessary documentation (Confluence, contributing docs) or informed the documentation team

🦮 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

…kground instantiates on init of the extension
@cagonzalezcs cagonzalezcs requested a review from a team as a code owner September 18, 2024 19:08
Copy link

codecov bot commented Sep 18, 2024

Codecov Report

Attention: Patch coverage is 0% with 4 lines in your changes missing coverage. Please review.

Project coverage is 33.19%. Comparing base (80d0f7e) to head (f002377).
Report is 2 commits behind head on main.

Files with missing lines Patch % Lines
apps/browser/src/background/main.background.ts 0.00% 4 Missing ⚠️
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.
📢 Have feedback on the report? Share it here.

Copy link
Contributor

github-actions bot commented Sep 18, 2024

Logo
Checkmarx One – Scan Summary & Detailsc069d44e-3682-4c57-ba8b-c134f16cceea

New Issues

Severity Issue Source File / Package Checkmarx Insight
MEDIUM Client_Privacy_Violation /apps/web/src/app/tools/access-intelligence/password-health.component.html: 45 Attack Vector
MEDIUM Client_Privacy_Violation /apps/web/src/app/tools/access-intelligence/password-health.component.ts: 54 Attack Vector
MEDIUM Client_Privacy_Violation /apps/web/src/app/tools/access-intelligence/password-health.component.ts: 52 Attack Vector
MEDIUM Client_Privacy_Violation /apps/web/src/app/tools/access-intelligence/password-health.component.ts: 48 Attack Vector
MEDIUM Client_Privacy_Violation /apps/browser/src/background/main.background.ts: 641 Attack Vector
MEDIUM Client_Privacy_Violation /apps/browser/src/background/main.background.ts: 976 Attack Vector
MEDIUM Client_Privacy_Violation /apps/browser/src/background/main.background.ts: 962 Attack Vector
MEDIUM Client_Privacy_Violation /apps/browser/src/background/main.background.ts: 619 Attack Vector
MEDIUM Client_Privacy_Violation /apps/browser/src/background/main.background.ts: 694 Attack Vector

Fixed Issues

Severity Issue Source File / Package
MEDIUM Client_Privacy_Violation /apps/web/src/app/tools/access-intelligence/password-health.component.html: 50
MEDIUM Client_Privacy_Violation /apps/web/src/app/tools/access-intelligence/password-health.component.html: 45
MEDIUM Client_Privacy_Violation /apps/web/src/app/tools/access-intelligence/password-health.component.html: 40
MEDIUM Client_Privacy_Violation /apps/web/src/app/tools/access-intelligence/password-health.component.html: 45

jprusik
jprusik previously approved these changes Sep 23, 2024
@cagonzalezcs cagonzalezcs marked this pull request as draft September 24, 2024 13:54
@cagonzalezcs
Copy link
Contributor Author

Converting this to a draft to ensure we don't accidentally merge the work in.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants