refactor: ENABLE_MV3 flag cleanup#26059
Conversation
fix: skip MV3-only tests on MV2 instead of marking them as passing
- push-platform-notifications
|
CLA Signature Action: All authors have signed the CLA. You may need to manually re-run the blocking PR check if it doesn't pass in a few minutes. |
Builds ready [3bb6394]
Page Load Metrics (259 ± 251 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
Codecov ReportAttention: Patch coverage is
Additional details and impacted files@@ Coverage Diff @@
## develop #26059 +/- ##
===========================================
- Coverage 69.97% 69.97% -0.00%
===========================================
Files 1411 1411
Lines 49995 50000 +5
Branches 13805 13809 +4
===========================================
+ Hits 34981 34984 +3
- Misses 15014 15016 +2 ☔ View full report in Codecov by Sentry. |
|
Looks solid to me 👍🏻 thanks for the refactor ! |
Builds ready [c180fad]
Page Load Metrics (255 ± 251 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
|
@HowardBraham, all the tests are passing and code looks good. I ran the below tests using the below commands. Could you make the changes to these files too. |
87180b4 to
0088293
Compare
Builds ready [0088293]
Page Load Metrics (443 ± 323 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|
|
Builds ready [7c61ca7]
Page Load Metrics (568 ± 412 ms)
Bundle size diffs [🚨 Warning! Bundle size has increased!]
|




Description
The way that the
ENABLE_MV3flag was processed was kind of a mess. Sometimes it wasn't checking both options of'true'andundefined, sometimes it was only checkingbrowser.runtime.getManifest().manifest_version, and it was always loquacious.This PR centralizes it and defines it as:
Related issues
Supersedes: #25242
(@legobeat started working on an aspect of this, but it got stale. This PR incorporates his work.)
Manual testing steps
Screenshots/Recordings
Before
After
Pre-merge author checklist
Pre-merge reviewer checklist