Public report of mozilla-mobile/firefox-ios, published 14 November 2026. It has the same score, grades and number of
findings as the full report. The details of security findings (where they are in the code, which known
vulnerabilities and which passwords or keys were found) are left out, so nobody can use them against the project.
Public
Executive reportMeasured under the Code Assurance Index, an open standard for code quality, using its published scoring rules (rubric version 2026.11.4). Assert signed this survey and filed it in the standard's public register, where anyone can look it up by its survey ID. Check this survey →
Signed and filed in the standard's public register, 14 November 2026, 09:31 UTC · Survey ID cd_7d50c7b5c16f4898a8a4d78050c8eb9e
mozilla-mobile/firefox-ios
Measured 14 November 2026, 09:26 UTC, at code version 11226b9
Test reliability is not measured: The suite could not be re-run, but the repository declares tests of its own unreliable.
Supply-chain provenance & signing is not measured: Supply-chain provenance is not scored (this pipeline releases no artifact), but its build steps or GitHub Actions workflows have integrity defects, or nothing watches its dependency set for published advisories.
CAI scoreWeak
CriticalWeakAdequateStrongExemplary
Up 3 since the last survey
The score is built from these lenses. Each lens grades one area of the code, such as how easy it is to change or how well it is protected. The weakest lens counts most, so one weak area pulls the score down instead of being averaged away.
A large codebase: 246,376 lines of product code in 33 projects, tests not counted · Estimated rebuild effort: about 2.4 person-years · Weakest lens: Code Health, 28
Findings by how serious they are
53 critical2306 serious266 minor
26 dimensions are left out of the score. For each one, we either couldn't measure it in this code, or found no evidence of the safeguard we look for, such as a tested backup restore. They count neither for nor against the score, and Limitations lists each one with its reason.
This survey was produced by
Canine Code Analyzer
Producer
Canine Development
Analyzer
Canine Code Analyzer engine 1.0.0
Measured
14 November 2026, 09:26 UTC
A measurement, not a certificate. The Code Assurance Index records a number
together with the evidence it was worked out from, so anyone can recalculate it, but it doesn't certify or guarantee
the code. The standard was written by Canine Development, which also builds the Canine Code Analyzer. It is open to any tool that
implements it, and today the Canine Code Analyzer is the only one that does.
The score is deterministic, which means the same code always gets the same score. We work it out with tools that follow published rules, and an AI model never decides it, so anyone who applies the same rules to the same code gets the same number. How it is done is explained under Methodology ▸
62of 62 dimensions measured by tools.
2596of 2625 findings point to an exact file and line, so you can open each one in the code. The other 29 concern the repository as a whole, such as missing documentation.
62dimensions across 7 lenses, read from 246,376 lines of product code in 33 projects.
mozilla-mobile/firefox-ios falls short of our standard for production, held back most by its Code Health lens, the quality of the code itself. It scores 44 out of 100 and is rated Weak, and 17 of its 53 critical findings are security problems.
Code Health, at 28, is the weakest lens and counts most in the score. The best first step for the work it takes is making the tests check their results, worth about 4 points. Adding type checking would lift Code Health itself, worth about 5 points. Raising Code Health to 70 would lift the score to about 56.
Nine pipeline steps install packages that can change without warning. Five settings leave the servers or containers unsafe, and ten sets of files in separate parts keep changing together, which points to hidden dependencies. Pinning what the pipeline installs, correcting the unsafe settings and making the hidden dependencies explicit would close these risks. Pinning each tool to an exact version would fix the two pipeline tools referenced by a changeable name, and fixing the weaknesses the scanner points to would deal with the security weakness in the code. The seven pages that block zooming need the zoom block removed.
The product code is 246,376 lines, about €350,000 to rebuild.
A lens is capped at Adequate while one of its dimensions scores below 4 out of 10, however well the rest of the lens does. That way a serious problem in one place always shows in the lens's rating.
How the score is built: what each lens counts forThe lenses don't count equally. The weakest lens counts most, the next weakest a little less, and so on, so a weak area pulls the score down instead of being averaged away. In the bar below, each part's width shows how much that lens counts and its colour shows its rating. Improving the widest part moves the score most, and as that lens improves, it counts for less, because another lens becomes the weakest.
If Code Health rose from 28 to 70, the lowest score rated Strong, the score would rise from 44 to about 56.
Code composition: what the lines of code are
Product code 62%Tests 38%
New since the last survey: 647 findings
These 647 critical or serious findings weren't in the previous survey, on 26 October 2026. The first 100 are listed here, and the findings file in the download package lists them all.
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift
Code Duplication · Members sharing a duplicated core (5 members, 50+ identical tokens) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewController.swift
Code Duplication · Members sharing a duplicated core (4 members, 50+ identical tokens) BrowserKit/Sources/Shared/InstallationUtils.swift
Code Duplication · Edited copy of a member (65 corresponding lines) firefox-ios/CredentialProvider/CredentialPasscodeRequirementViewController.swift
Code Duplication · Edited copies of one member (3 members, 47+ corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/EmptyPrivateTabsView.swift
Code Duplication · Edited copy of a member (50 corresponding lines) firefox-ios/Client/Telemetry/FxSuggestTelemetry.swift
Code Duplication · Edited copy of a member (48 corresponding lines) BrowserKit/Sources/SummarizeKit/UI/InfoViewFormatter.swift
Code Duplication · Edited copy of a member (50 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/LayoutManager/TabsSectionManager.swift
Code Duplication · Edited copies of one member (3 members, 44+ corresponding lines) firefox-ios/Client/Telemetry/SearchTelemetry.swift
Code Duplication · Edited copies of one member (6 members, 40+ corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/SyncManager/SyncManagerTelemetry.swift
Code Duplication · Edited copy of a member (36 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/BookmarksSaver.swift
Code Duplication · Edited copy of a member (43 corresponding lines) firefox-ios/Client/Application/UITestAppDelegate.swift
Code Duplication · Edited copy of a member (60 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift
Code Duplication · Edited copy of a member (41 corresponding lines) firefox-ios/Client/Frontend/Settings/HomepageSettings/HomePageSettingViewController.swift
Code Duplication · Edited copy of a member (43 corresponding lines) firefox-ios/Client/Frontend/TabContentsScripts/LoginsHelper.swift
Code Duplication · Edited copies of one member (3 members, 26+ corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeMLPAEndpointSetting.swift
Code Duplication · Edited copy of a member (31 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift
Code Duplication · Edited copy of a member (42 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift
Code Duplication · Edited copy of a member (32 corresponding lines) firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift
Code Duplication · Edited copy of a member (47 corresponding lines) firefox-ios/Client/Helpers/MenuBuilderHelper.swift
Code Duplication · Edited copy of a member (36 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift
Code Duplication · Edited copies of one member (3 members, 28+ corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift
Code Duplication · Edited copy of a member (28 corresponding lines) firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift
Code Duplication · Edited copy of a member (28 corresponding lines) firefox-ios/WidgetKit/OpenTabs/TabProvider.swift
Code Duplication · Edited copy of a member (37 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift
Code Duplication · Edited copy of a member (15 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReadabilityResult.swift
Code Duplication · Edited copy of a member (36 corresponding lines) BrowserKit/Sources/ActionExtensionKit/FirefoxURLBuilding.swift
Code Duplication · Edited copy of a member (35 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift
Code Duplication · Edited copy of a member (22 corresponding lines) focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift
Code Duplication · Edited copy of a member (31 corresponding lines) firefox-ios/Storage/Rust/RustLogins.swift
Code Duplication · Edited copy of a member (32 corresponding lines) firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEngineProvider.swift
Code Duplication · Edited copy of a member (24 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift
Code Duplication · Edited copy of a member (15 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift
Code Duplication · Edited copy of a member (28 corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Redux/BrowserActionsBuilder.swift
Code Duplication · Edited copy of a member (29 corresponding lines) firefox-ios/Storage/Rust/RustPlaces.swift
Code Duplication · Edited copy of a member (23 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift
Code Duplication · Edited copy of a member (34 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/General/AdBlockerSetting.swift
Code Duplication · Edited copy of a member (18 corresponding lines) BrowserKit/Sources/MenuKit/MenuAccountCell.swift
Code Duplication · Edited copy of a member (37 corresponding lines) REDACTED
Code Duplication · Edited copy of a member (22 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift
Code Duplication · Edited copy of a member (18 corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift
Code Duplication · Edited copy of a member (32 corresponding lines) firefox-ios/Client/Frontend/Browser/MainMenu/MainMenuConfigurationUtility.swift
Code Duplication · Edited copy of a member (27 corresponding lines) BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift
Code Duplication · Edited copy of a member (21 corresponding lines) BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift
Code Duplication · Edited copy of a member (28 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift
Code Duplication · Edited copy of a member (23 corresponding lines) BrowserKit/Sources/MenuKit/MenuCell.swift
Code Duplication · Edited copy of a member (25 corresponding lines) firefox-ios/Storage/SQL/SQLiteReadingList.swift
Code Duplication · Edited copy of a member (21 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReaderModeContentScript.swift
Code Duplication · Edited copy of a member (23 corresponding lines) firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift
Code Duplication · Edited copies of one member (3 members, 16+ corresponding lines) firefox-ios/Client/Frontend/Settings/AIControls/AIControlsSettingsView.swift
Code Duplication · Edited copy of a member (30 corresponding lines) firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift
Code Duplication · Edited copy of a member (23 corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift
Code Duplication · Edited copy of a member (31 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift
Code Duplication · Edited copy of a member (19 corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift
Code Duplication · Edited copies of one member (3 members, 21+ corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Sync15/RustSyncTelemetryPing.swift
Code Duplication · Edited copy of a member (30 corresponding lines) firefox-ios/Client/Telemetry/SearchTelemetry.swift
Code Duplication · Edited copy of a member (28 corresponding lines) firefox-ios/Storage/Rust/RustPlaces.swift
Code Duplication · Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Reader/SchemeHandler/ReaderFileRoute.swift
Code Duplication · Edited copy of a member (23 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionDetailsViewController.swift
Code Duplication · Edited copy of a member (37 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift
Code Duplication · Edited copy of a member (20 corresponding lines) firefox-ios/Client/TabManagement/Tab.swift
Code Duplication · Edited copy of a member (17 corresponding lines) BrowserKit/Sources/VPNKit/VPNAppAttestServer.swift
Code Duplication · Edited copy of a member (17 corresponding lines) firefox-ios/Client/Coordinators/CredentialAutofillCoordinator.swift
Code Duplication · Edited copy of a member (20 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift
Code Duplication · Edited copies of one member (4 members, 27+ corresponding lines) BrowserKit/Sources/ComponentLibrary/BottomSheet/BottomSheetViewController.swift
Code Duplication · Edited copy of a member (27 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift
Code Duplication · Edited copy of a member (18 corresponding lines) focus-ios/Blockzilla/BrowserViewController.swift
Code Duplication · Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift
Code Duplication · Edited copy of a member (15 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift
Code Duplication · Edited copy of a member (10 corresponding lines) firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEnginePrefsMigrator.swift
Code Duplication · Edited copy of a member (30 corresponding lines) firefox-ios/Client/Coordinators/Library/DownloadsCoordinator.swift
Code Duplication · Edited copy of a member (20 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift
Code Duplication · Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkDiffableDataSource.swift
Code Duplication · Edited copy of a member (10 corresponding lines) firefox-ios/Client/Telemetry/GleanUsageReporting.swift
Code Duplication · Edited copy of a member (17 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift
Code Duplication · Edited copy of a member (19 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift
Code Duplication · Edited copy of a member (14 corresponding lines) firefox-ios/CredentialProvider/Cells/EmptyPlaceholderCell.swift
Code Duplication · Edited copy of a member (22 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksPanelViewModel.swift
Code Duplication · Edited copy of a member (17 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserPrompts.swift
Code Duplication · Edited copy of a member (17 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift
Code Duplication · Edited copy of a member (17 corresponding lines) SampleBrowser/SampleBrowser/UI/Settings/SettingsViewController.swift
Code Duplication · Edited copy of a member (16 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift
Code Duplication · Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/AuthenticationManager/SensitiveViewController.swift
Code Duplication · Edited copy of a member (22 corresponding lines) firefox-ios/Client/Frontend/InternalSchemeHandler/ErrorPageHelper.swift
Code Duplication · Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift
Code Duplication · Edited copies of one member (3 members, 18+ corresponding lines) firefox-ios/Client/Frontend/Settings/ContentBlockerSettingViewController.swift
Code Duplication · Edited copy of a member (18 corresponding lines) focus-ios/Blockzilla/Siri/SiriShortcuts.swift
Code Duplication · Edited copy of a member (20 corresponding lines) BrowserKit/Sources/ActionExtensionKit/ActionShareItem.swift
Code Duplication · Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Translations/SchemeHandler/ModelsBufferRoute.swift
Code Duplication · Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift
Code Duplication · Edited copy of a member (20 corresponding lines) firefox-ios/Client/Frontend/Reader/View/ReaderModeStyleViewController.swift
Code Duplication · Edited copy of a member (26 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/MetadataFetcherHelper.swift
Code Duplication · Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift
Code Duplication · Edited copy of a member (25 corresponding lines) firefox-ios/Storage/Rust/RustAutofill.swift
Code Duplication · Edited copy of a member (20 corresponding lines) focus-ios/Blockzilla/BrowserViewController.swift
We compare every finding with the previous survey's. A finding that has only moved to another line in the same file counts as the same finding, so only new findings appear here. Advisory notes from the AI model are left out, because the model words them afresh in every survey.
Fixed since the last survey: 193 findings
These 193 critical or serious findings were in the previous survey, on 26 October 2026, and are gone from this one. The first 100 are listed here.
Cohesion (LCOM4) · Low cohesion: Date (LCOM4 7) firefox-ios/Shared/Date+relativeTimeString.swift
Rebuild cost: about €350,000 · Estimate
Cost to rebuild
€120,000 to €580,000, for 1,929 to 6,119 hours of work, about 2.4 person-years for 1 to 5 engineers
Difficulty of the problem
Standard, judged from the kind of software and how it is built. Code that solves a harder problem, such as payments or medical bookings, costs more per line to write.
Quality factor
×0.7 at a score of 44. Better code takes more work to write, so the factor is ×1.0 at a score of 70, lower below it and higher above it.
Size
Large: 246,376 lines of product code
What it is not
Not a quotation: nobody has offered to build it for that. Not a valuation: it says nothing about what the business is worth. Not a certified figure: no professional has signed it as one.
How the estimate is made: We price the hours a team would need to write this code again, at €60 to €95 an hour. Declarations and boilerplate are priced at a fast rate and logic at a slower one, and the logic is then multiplied by the difficulty of the problem and by the quality factor. The estimate can be about 30% off either way, and it moves most with the hourly rate and the difficulty. For this code, every line is priced as straight logic, which keeps the estimate on the low side.
Top priorities
The three actions that raise the score most for the work they take. The full ranked list is in the Roadmap.
1
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with WKEngineSessionTests.swift.
Raises the score by about 4 points · Low effort · Test Quality
2
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Raises the score by about 5 points · Medium effort · Type Safety
3
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
Raises the score by about 5 points · Medium effort · Large Files
Diagnosis: what the measurements show together
Each conclusion below combines several dimensions into one point that no single dimension shows, and lists the measurements it rests on.
Where the investment is most exposed · Value at risk
This code would cost about €350,000 to build again, about 2.4 person-years of work. Its weakest lens is Code Health, at 28 (Weak). Code Health is about how easy the code is to read and change safely, and code that is hard to read is slow and risky to change, so every future change costs more than it should. Because the weakest lens counts most in the score, work on Code Health also moves the score most.
Based on: the rebuild estimate · the Code Health grade · how much each lens counts
What to do: Start with the Code Health actions in Top priorities.
If you do one thing first · First action
Resolve the 1 Assertions commented out finding(s) in Test Quality. Of all the actions in this report, it raises the score most for the work it takes: about 4 points for low effort, because it clears the 1 Test Quality findings. The next survey will show the change in the score.
Based on: the ranked actions in Top priorities, by score gain and effort
What hard-to-read code costs each year · Cost
Four dimensions measure how easy the code is to work in: two measure how tangled its logic is, one how much of it is copied, and one how well each part sticks to a single job. In this codebase they average 6.4 out of 10. Code at that level is slower to change than clean code, and we estimate the extra work at 4% to 9% on every change. The history of the code shows how much it changes: about 134,505 lines over the last 90 days, which is about 545,492 lines a year. At that pace, the extra work comes to an estimated 53.7 to 322 engineer-days a year, and it grows as more code changes.
How this is estimated: The number of changed lines is measured from the history of the code. The rest rests on two assumptions of our own: code scoring 8 out of 10 or more adds no extra work, and each point below 8 adds 2.5% to 5.6% to every change, never less than 2% to 5% and never more than 40% to 60% in all; and an engineer changes 150 to 400 lines in a day. The result is a range for planning, not a measurement.
Based on: Cyclomatic Complexity · Cognitive Complexity · Code Duplication · Cohesion (LCOM4) · the code's change history
What to do: Start with the files listed under Churn × Complexity Hotspots, which change often and are hard to read, because that is where the extra work is paid most often.
Architecture — module dependency graph
Project dependencies, layered top-to-bottom; arrows show direction. Any dashed red edge points upward or sideways, which only happens where the projects form a dependency cycle. A graph without cycles has none.
Architecture: which parts of the code depend on which
The code is divided into modules, groups of code that each handle one part of the product, and a module depends on another when it uses code from it. The table lists the modules both down the side and across the top, in an order where each module should only use modules listed above it. A number in a cell means the module on that row uses the module in that column, and it counts the pairs of building blocks (types) that connect them. The one thing to look for is a mark above the diagonal line. It means two or more modules use each other in a loop (a dependency cycle), so none of them can be changed, tested or released on its own.
88 modules, with 136 dependencies between them. One loop runs through 26 of the modules, marked above the diagonal.
The table shows the 40 modules with the most connections; 48 more are left out to keep it readable.
Which modules use which. The module on each row uses the module in each column, and the number counts the pairs of types that connect them. A cell above the diagonal is part of a loop.
2 pairs of types, where a type in firefox-ios.Client.Assets.CC_Script.fathom uses a type in firefox-ios.Client.Assets.CC_Script.PasswordRulesParser_sys.
firefox-ios.Client.Assets.CC_Script.fathom uses firefox-ios.Client.Assets.CC_Script.PasswordRulesParser_sys, so a change to firefox-ios.Client.Assets.CC_Script.PasswordRulesParser_sys can break firefox-ios.Client.Assets.CC_Script.fathom, while a change to firefox-ios.Client.Assets.CC_Script.fathom can't break firefox-ios.Client.Assets.CC_Script.PasswordRulesParser_sys.
Position
Below the diagonal: firefox-ios.Client.Assets.CC_Script.fathom uses a module listed above it, which is the healthy direction.
10→36 focus-ios~BlockzillaPackage~DesignSystem uses repositorypart of a loop✕
Connections
12 pairs of types, where a type in focus-ios~BlockzillaPackage~DesignSystem uses a type in repository.
focus-ios~BlockzillaPackage~DesignSystem uses repository, so a change to repository can break focus-ios~BlockzillaPackage~DesignSystem, while a change to focus-ios~BlockzillaPackage~DesignSystem can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
11→36 focus-ios~BlockzillaPackage~UIComponents uses repositorypart of a loop✕
Connections
4 pairs of types, where a type in focus-ios~BlockzillaPackage~UIComponents uses a type in repository.
focus-ios~BlockzillaPackage~UIComponents uses repository, so a change to repository can break focus-ios~BlockzillaPackage~UIComponents, while a change to focus-ios~BlockzillaPackage~UIComponents can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
12→36 focus-ios~BlockzillaPackage~UIHelpers uses repositorypart of a loop✕
Connections
8 pairs of types, where a type in focus-ios~BlockzillaPackage~UIHelpers uses a type in repository.
focus-ios~BlockzillaPackage~UIHelpers uses repository, so a change to repository can break focus-ios~BlockzillaPackage~UIHelpers, while a change to focus-ios~BlockzillaPackage~UIHelpers can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
scripts uses scripts.update_from_application_services, so a change to scripts.update_from_application_services can break scripts, while a change to scripts can't break scripts.update_from_application_services.
Position
Below the diagonal: scripts uses a module listed above it, which is the healthy direction.
focus-ios~BlockzillaPackage~Onboarding uses focus-ios~BlockzillaPackage~UIHelpers, so a change to focus-ios~BlockzillaPackage~UIHelpers can break focus-ios~BlockzillaPackage~Onboarding, while a change to focus-ios~BlockzillaPackage~Onboarding can't break focus-ios~BlockzillaPackage~UIHelpers.
Position
Below the diagonal: focus-ios~BlockzillaPackage~Onboarding uses a module listed above it, which is the healthy direction.
14→15 focus-ios~BlockzillaPackage~Onboarding uses BrowserKit~WebEnginepart of a loop✕
Connections
1 pair of types, where a type in focus-ios~BlockzillaPackage~Onboarding uses a type in BrowserKit~WebEngine.
focus-ios~BlockzillaPackage~Onboarding uses BrowserKit~WebEngine, so a change to BrowserKit~WebEngine can break focus-ios~BlockzillaPackage~Onboarding, while a change to focus-ios~BlockzillaPackage~Onboarding can't break BrowserKit~WebEngine.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→16 focus-ios~BlockzillaPackage~Onboarding uses BrowserKit~Sharedpart of a loop✕
Connections
5 pairs of types, where a type in focus-ios~BlockzillaPackage~Onboarding uses a type in BrowserKit~Shared.
focus-ios~BlockzillaPackage~Onboarding uses BrowserKit~Shared, so a change to BrowserKit~Shared can break focus-ios~BlockzillaPackage~Onboarding, while a change to focus-ios~BlockzillaPackage~Onboarding can't break BrowserKit~Shared.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→21 focus-ios~BlockzillaPackage~Onboarding uses BrowserKit~ComponentLibrarypart of a loop✕
Connections
1 pair of types, where a type in focus-ios~BlockzillaPackage~Onboarding uses a type in BrowserKit~ComponentLibrary.
focus-ios~BlockzillaPackage~Onboarding uses BrowserKit~ComponentLibrary, so a change to BrowserKit~ComponentLibrary can break focus-ios~BlockzillaPackage~Onboarding, while a change to focus-ios~BlockzillaPackage~Onboarding can't break BrowserKit~ComponentLibrary.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→22 focus-ios~BlockzillaPackage~Onboarding uses BrowserKit~OnboardingKitpart of a loop✕
Connections
1 pair of types, where a type in focus-ios~BlockzillaPackage~Onboarding uses a type in BrowserKit~OnboardingKit.
focus-ios~BlockzillaPackage~Onboarding uses BrowserKit~OnboardingKit, so a change to BrowserKit~OnboardingKit can break focus-ios~BlockzillaPackage~Onboarding, while a change to focus-ios~BlockzillaPackage~Onboarding can't break BrowserKit~OnboardingKit.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
14→36 focus-ios~BlockzillaPackage~Onboarding uses repositorypart of a loop✕
Connections
69 pairs of types, where a type in focus-ios~BlockzillaPackage~Onboarding uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
focus-ios~BlockzillaPackage~Onboarding uses repository, so a change to repository can break focus-ios~BlockzillaPackage~Onboarding, while a change to focus-ios~BlockzillaPackage~Onboarding can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~WebEngine uses focus-ios~BlockzillaPackage~Onboarding, so a change to focus-ios~BlockzillaPackage~Onboarding can break BrowserKit~WebEngine, while a change to BrowserKit~WebEngine can't break focus-ios~BlockzillaPackage~Onboarding.
Position
Below the diagonal: BrowserKit~WebEngine uses a module listed above it, which is the healthy direction.
15→16 BrowserKit~WebEngine uses BrowserKit~Sharedpart of a loop✕
Connections
11 pairs of types, where a type in BrowserKit~WebEngine uses a type in BrowserKit~Shared.
BrowserKit~WebEngine uses BrowserKit~Shared, so a change to BrowserKit~Shared can break BrowserKit~WebEngine, while a change to BrowserKit~WebEngine can't break BrowserKit~Shared.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→17 BrowserKit~WebEngine uses MozillaRustComponents~FocusRustComponentsWrapperpart of a loop✕
Connections
1 pair of types, where a type in BrowserKit~WebEngine uses a type in MozillaRustComponents~FocusRustComponentsWrapper.
BrowserKit~WebEngine uses MozillaRustComponents~FocusRustComponentsWrapper, so a change to MozillaRustComponents~FocusRustComponentsWrapper can break BrowserKit~WebEngine, while a change to BrowserKit~WebEngine can't break MozillaRustComponents~FocusRustComponentsWrapper.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→23 BrowserKit~WebEngine uses BrowserKit~Commonpart of a loop✕
Connections
22 pairs of types, where a type in BrowserKit~WebEngine uses a type in BrowserKit~Common.
BrowserKit~WebEngine uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~WebEngine, while a change to BrowserKit~WebEngine can't break BrowserKit~Common.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
15→36 BrowserKit~WebEngine uses repositorypart of a loop✕
Connections
150 pairs of types, where a type in BrowserKit~WebEngine uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~WebEngine uses repository, so a change to repository can break BrowserKit~WebEngine, while a change to BrowserKit~WebEngine can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~Shared uses BrowserKit~WebEngine, so a change to BrowserKit~WebEngine can break BrowserKit~Shared, while a change to BrowserKit~Shared can't break BrowserKit~WebEngine.
Position
Below the diagonal: BrowserKit~Shared uses a module listed above it, which is the healthy direction.
16→17 BrowserKit~Shared uses MozillaRustComponents~FocusRustComponentsWrapperpart of a loop✕
Connections
1 pair of types, where a type in BrowserKit~Shared uses a type in MozillaRustComponents~FocusRustComponentsWrapper.
BrowserKit~Shared uses MozillaRustComponents~FocusRustComponentsWrapper, so a change to MozillaRustComponents~FocusRustComponentsWrapper can break BrowserKit~Shared, while a change to BrowserKit~Shared can't break MozillaRustComponents~FocusRustComponentsWrapper.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→23 BrowserKit~Shared uses BrowserKit~Commonpart of a loop✕
Connections
6 pairs of types, where a type in BrowserKit~Shared uses a type in BrowserKit~Common.
BrowserKit~Shared uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~Shared, while a change to BrowserKit~Shared can't break BrowserKit~Common.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
16→36 BrowserKit~Shared uses repositorypart of a loop✕
Connections
112 pairs of types, where a type in BrowserKit~Shared uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MozillaRustComponents~FocusRustComponentsWrapper uses BrowserKit~Shared, so a change to BrowserKit~Shared can break MozillaRustComponents~FocusRustComponentsWrapper, while a change to MozillaRustComponents~FocusRustComponentsWrapper can't break BrowserKit~Shared.
Position
Below the diagonal: MozillaRustComponents~FocusRustComponentsWrapper uses a module listed above it, which is the healthy direction.
17→23 MozillaRustComponents~FocusRustComponentsWrapper uses BrowserKit~Commonpart of a loop✕
Connections
15 pairs of types, where a type in MozillaRustComponents~FocusRustComponentsWrapper uses a type in BrowserKit~Common.
MozillaRustComponents~FocusRustComponentsWrapper uses BrowserKit~Common, so a change to BrowserKit~Common can break MozillaRustComponents~FocusRustComponentsWrapper, while a change to MozillaRustComponents~FocusRustComponentsWrapper can't break BrowserKit~Common.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
17→36 MozillaRustComponents~FocusRustComponentsWrapper uses repositorypart of a loop✕
Connections
190 pairs of types, where a type in MozillaRustComponents~FocusRustComponentsWrapper uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MozillaRustComponents~FocusRustComponentsWrapper uses repository, so a change to repository can break MozillaRustComponents~FocusRustComponentsWrapper, while a change to MozillaRustComponents~FocusRustComponentsWrapper can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
focus-ios~BlockzillaPackage~AppShortcuts uses focus-ios~BlockzillaPackage~UIComponents, so a change to focus-ios~BlockzillaPackage~UIComponents can break focus-ios~BlockzillaPackage~AppShortcuts, while a change to focus-ios~BlockzillaPackage~AppShortcuts can't break focus-ios~BlockzillaPackage~UIComponents.
Position
Below the diagonal: focus-ios~BlockzillaPackage~AppShortcuts uses a module listed above it, which is the healthy direction.
focus-ios~BlockzillaPackage~AppShortcuts uses focus-ios~BlockzillaPackage~Onboarding, so a change to focus-ios~BlockzillaPackage~Onboarding can break focus-ios~BlockzillaPackage~AppShortcuts, while a change to focus-ios~BlockzillaPackage~AppShortcuts can't break focus-ios~BlockzillaPackage~Onboarding.
Position
Below the diagonal: focus-ios~BlockzillaPackage~AppShortcuts uses a module listed above it, which is the healthy direction.
focus-ios~BlockzillaPackage~AppShortcuts uses BrowserKit~Shared, so a change to BrowserKit~Shared can break focus-ios~BlockzillaPackage~AppShortcuts, while a change to focus-ios~BlockzillaPackage~AppShortcuts can't break BrowserKit~Shared.
Position
Below the diagonal: focus-ios~BlockzillaPackage~AppShortcuts uses a module listed above it, which is the healthy direction.
18→36 focus-ios~BlockzillaPackage~AppShortcuts uses repositorypart of a loop✕
Connections
11 pairs of types, where a type in focus-ios~BlockzillaPackage~AppShortcuts uses a type in repository.
focus-ios~BlockzillaPackage~AppShortcuts uses repository, so a change to repository can break focus-ios~BlockzillaPackage~AppShortcuts, while a change to focus-ios~BlockzillaPackage~AppShortcuts can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~SiteImageView uses MozillaRustComponents~FocusRustComponentsWrapper, so a change to MozillaRustComponents~FocusRustComponentsWrapper can break BrowserKit~SiteImageView, while a change to BrowserKit~SiteImageView can't break MozillaRustComponents~FocusRustComponentsWrapper.
Position
Below the diagonal: BrowserKit~SiteImageView uses a module listed above it, which is the healthy direction.
19→23 BrowserKit~SiteImageView uses BrowserKit~Commonpart of a loop✕
Connections
8 pairs of types, where a type in BrowserKit~SiteImageView uses a type in BrowserKit~Common.
BrowserKit~SiteImageView uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~SiteImageView, while a change to BrowserKit~SiteImageView can't break BrowserKit~Common.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
19→36 BrowserKit~SiteImageView uses repositorypart of a loop✕
Connections
85 pairs of types, where a type in BrowserKit~SiteImageView uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~SiteImageView uses repository, so a change to repository can break BrowserKit~SiteImageView, while a change to BrowserKit~SiteImageView can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
36 pairs of types, where a type in MozillaRustComponents~MozillaRustComponentsWrapper uses a type in BrowserKit~Shared. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MozillaRustComponents~MozillaRustComponentsWrapper uses BrowserKit~Shared, so a change to BrowserKit~Shared can break MozillaRustComponents~MozillaRustComponentsWrapper, while a change to MozillaRustComponents~MozillaRustComponentsWrapper can't break BrowserKit~Shared.
Position
Below the diagonal: MozillaRustComponents~MozillaRustComponentsWrapper uses a module listed above it, which is the healthy direction.
578 pairs of types, where a type in MozillaRustComponents~MozillaRustComponentsWrapper uses a type in MozillaRustComponents~FocusRustComponentsWrapper. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MozillaRustComponents~MozillaRustComponentsWrapper uses MozillaRustComponents~FocusRustComponentsWrapper, so a change to MozillaRustComponents~FocusRustComponentsWrapper can break MozillaRustComponents~MozillaRustComponentsWrapper, while a change to MozillaRustComponents~MozillaRustComponentsWrapper can't break MozillaRustComponents~FocusRustComponentsWrapper.
Position
Below the diagonal: MozillaRustComponents~MozillaRustComponentsWrapper uses a module listed above it, which is the healthy direction.
20→23 MozillaRustComponents~MozillaRustComponentsWrapper uses BrowserKit~Commonpart of a loop✕
Connections
40 pairs of types, where a type in MozillaRustComponents~MozillaRustComponentsWrapper uses a type in BrowserKit~Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MozillaRustComponents~MozillaRustComponentsWrapper uses BrowserKit~Common, so a change to BrowserKit~Common can break MozillaRustComponents~MozillaRustComponentsWrapper, while a change to MozillaRustComponents~MozillaRustComponentsWrapper can't break BrowserKit~Common.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
20→36 MozillaRustComponents~MozillaRustComponentsWrapper uses repositorypart of a loop✕
Connections
506 pairs of types, where a type in MozillaRustComponents~MozillaRustComponentsWrapper uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
MozillaRustComponents~MozillaRustComponentsWrapper uses repository, so a change to repository can break MozillaRustComponents~MozillaRustComponentsWrapper, while a change to MozillaRustComponents~MozillaRustComponentsWrapper can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~ComponentLibrary uses focus-ios~BlockzillaPackage~DesignSystem, so a change to focus-ios~BlockzillaPackage~DesignSystem can break BrowserKit~ComponentLibrary, while a change to BrowserKit~ComponentLibrary can't break focus-ios~BlockzillaPackage~DesignSystem.
Position
Below the diagonal: BrowserKit~ComponentLibrary uses a module listed above it, which is the healthy direction.
BrowserKit~ComponentLibrary uses focus-ios~BlockzillaPackage~UIHelpers, so a change to focus-ios~BlockzillaPackage~UIHelpers can break BrowserKit~ComponentLibrary, while a change to BrowserKit~ComponentLibrary can't break focus-ios~BlockzillaPackage~UIHelpers.
Position
Below the diagonal: BrowserKit~ComponentLibrary uses a module listed above it, which is the healthy direction.
BrowserKit~ComponentLibrary uses focus-ios~BlockzillaPackage~Onboarding, so a change to focus-ios~BlockzillaPackage~Onboarding can break BrowserKit~ComponentLibrary, while a change to BrowserKit~ComponentLibrary can't break focus-ios~BlockzillaPackage~Onboarding.
Position
Below the diagonal: BrowserKit~ComponentLibrary uses a module listed above it, which is the healthy direction.
BrowserKit~ComponentLibrary uses BrowserKit~WebEngine, so a change to BrowserKit~WebEngine can break BrowserKit~ComponentLibrary, while a change to BrowserKit~ComponentLibrary can't break BrowserKit~WebEngine.
Position
Below the diagonal: BrowserKit~ComponentLibrary uses a module listed above it, which is the healthy direction.
BrowserKit~ComponentLibrary uses BrowserKit~SiteImageView, so a change to BrowserKit~SiteImageView can break BrowserKit~ComponentLibrary, while a change to BrowserKit~ComponentLibrary can't break BrowserKit~SiteImageView.
Position
Below the diagonal: BrowserKit~ComponentLibrary uses a module listed above it, which is the healthy direction.
21→23 BrowserKit~ComponentLibrary uses BrowserKit~Commonpart of a loop✕
Connections
37 pairs of types, where a type in BrowserKit~ComponentLibrary uses a type in BrowserKit~Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~ComponentLibrary uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~ComponentLibrary, while a change to BrowserKit~ComponentLibrary can't break BrowserKit~Common.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
21→36 BrowserKit~ComponentLibrary uses repositorypart of a loop✕
Connections
140 pairs of types, where a type in BrowserKit~ComponentLibrary uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~ComponentLibrary uses repository, so a change to repository can break BrowserKit~ComponentLibrary, while a change to BrowserKit~ComponentLibrary can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~OnboardingKit uses focus-ios~BlockzillaPackage~DesignSystem, so a change to focus-ios~BlockzillaPackage~DesignSystem can break BrowserKit~OnboardingKit, while a change to BrowserKit~OnboardingKit can't break focus-ios~BlockzillaPackage~DesignSystem.
Position
Below the diagonal: BrowserKit~OnboardingKit uses a module listed above it, which is the healthy direction.
BrowserKit~OnboardingKit uses focus-ios~BlockzillaPackage~Onboarding, so a change to focus-ios~BlockzillaPackage~Onboarding can break BrowserKit~OnboardingKit, while a change to BrowserKit~OnboardingKit can't break focus-ios~BlockzillaPackage~Onboarding.
Position
Below the diagonal: BrowserKit~OnboardingKit uses a module listed above it, which is the healthy direction.
BrowserKit~OnboardingKit uses BrowserKit~ComponentLibrary, so a change to BrowserKit~ComponentLibrary can break BrowserKit~OnboardingKit, while a change to BrowserKit~OnboardingKit can't break BrowserKit~ComponentLibrary.
Position
Below the diagonal: BrowserKit~OnboardingKit uses a module listed above it, which is the healthy direction.
22→23 BrowserKit~OnboardingKit uses BrowserKit~Commonpart of a loop✕
Connections
23 pairs of types, where a type in BrowserKit~OnboardingKit uses a type in BrowserKit~Common.
BrowserKit~OnboardingKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~OnboardingKit, while a change to BrowserKit~OnboardingKit can't break BrowserKit~Common.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
22→36 BrowserKit~OnboardingKit uses repositorypart of a loop✕
Connections
85 pairs of types, where a type in BrowserKit~OnboardingKit uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~OnboardingKit uses repository, so a change to repository can break BrowserKit~OnboardingKit, while a change to BrowserKit~OnboardingKit can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~Common uses MozillaRustComponents~FocusRustComponentsWrapper, so a change to MozillaRustComponents~FocusRustComponentsWrapper can break BrowserKit~Common, while a change to BrowserKit~Common can't break MozillaRustComponents~FocusRustComponentsWrapper.
Position
Below the diagonal: BrowserKit~Common uses a module listed above it, which is the healthy direction.
BrowserKit~Common uses MozillaRustComponents~MozillaRustComponentsWrapper, so a change to MozillaRustComponents~MozillaRustComponentsWrapper can break BrowserKit~Common, while a change to BrowserKit~Common can't break MozillaRustComponents~MozillaRustComponentsWrapper.
Position
Below the diagonal: BrowserKit~Common uses a module listed above it, which is the healthy direction.
BrowserKit~Common uses BrowserKit~OnboardingKit, so a change to BrowserKit~OnboardingKit can break BrowserKit~Common, while a change to BrowserKit~Common can't break BrowserKit~OnboardingKit.
Position
Below the diagonal: BrowserKit~Common uses a module listed above it, which is the healthy direction.
23→36 BrowserKit~Common uses repositorypart of a loop✕
Connections
141 pairs of types, where a type in BrowserKit~Common uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~AppAttestKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~AppAttestKit, while a change to BrowserKit~AppAttestKit can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~AppAttestKit uses a module listed above it, which is the healthy direction.
24→36 BrowserKit~AppAttestKit uses repositorypart of a loop✕
Connections
12 pairs of types, where a type in BrowserKit~AppAttestKit uses a type in repository.
BrowserKit~AppAttestKit uses repository, so a change to repository can break BrowserKit~AppAttestKit, while a change to BrowserKit~AppAttestKit can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~MenuKit uses focus-ios~BlockzillaPackage~Onboarding, so a change to focus-ios~BlockzillaPackage~Onboarding can break BrowserKit~MenuKit, while a change to BrowserKit~MenuKit can't break focus-ios~BlockzillaPackage~Onboarding.
Position
Below the diagonal: BrowserKit~MenuKit uses a module listed above it, which is the healthy direction.
BrowserKit~MenuKit uses BrowserKit~WebEngine, so a change to BrowserKit~WebEngine can break BrowserKit~MenuKit, while a change to BrowserKit~MenuKit can't break BrowserKit~WebEngine.
Position
Below the diagonal: BrowserKit~MenuKit uses a module listed above it, which is the healthy direction.
BrowserKit~MenuKit uses BrowserKit~SiteImageView, so a change to BrowserKit~SiteImageView can break BrowserKit~MenuKit, while a change to BrowserKit~MenuKit can't break BrowserKit~SiteImageView.
Position
Below the diagonal: BrowserKit~MenuKit uses a module listed above it, which is the healthy direction.
BrowserKit~MenuKit uses BrowserKit~ComponentLibrary, so a change to BrowserKit~ComponentLibrary can break BrowserKit~MenuKit, while a change to BrowserKit~MenuKit can't break BrowserKit~ComponentLibrary.
Position
Below the diagonal: BrowserKit~MenuKit uses a module listed above it, which is the healthy direction.
BrowserKit~MenuKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~MenuKit, while a change to BrowserKit~MenuKit can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~MenuKit uses a module listed above it, which is the healthy direction.
25→36 BrowserKit~MenuKit uses repositorypart of a loop✕
Connections
85 pairs of types, where a type in BrowserKit~MenuKit uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~MenuKit uses repository, so a change to repository can break BrowserKit~MenuKit, while a change to BrowserKit~MenuKit can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
1 pair of types, where a type in BrowserKit~Redux uses a type in BrowserKit~Shared.
The types involved
BrowserKit~Redux.Store → BrowserKit~Shared.Set
Direction
BrowserKit~Redux uses BrowserKit~Shared, so a change to BrowserKit~Shared can break BrowserKit~Redux, while a change to BrowserKit~Redux can't break BrowserKit~Shared.
Position
Below the diagonal: BrowserKit~Redux uses a module listed above it, which is the healthy direction.
BrowserKit~Redux uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~Redux, while a change to BrowserKit~Redux can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~Redux uses a module listed above it, which is the healthy direction.
26→36 BrowserKit~Redux uses repositorypart of a loop✕
Connections
4 pairs of types, where a type in BrowserKit~Redux uses a type in repository.
BrowserKit~SummarizeKit uses focus-ios~BlockzillaPackage~UIHelpers, so a change to focus-ios~BlockzillaPackage~UIHelpers can break BrowserKit~SummarizeKit, while a change to BrowserKit~SummarizeKit can't break focus-ios~BlockzillaPackage~UIHelpers.
Position
Below the diagonal: BrowserKit~SummarizeKit uses a module listed above it, which is the healthy direction.
BrowserKit~SummarizeKit uses BrowserKit~WebEngine, so a change to BrowserKit~WebEngine can break BrowserKit~SummarizeKit, while a change to BrowserKit~SummarizeKit can't break BrowserKit~WebEngine.
Position
Below the diagonal: BrowserKit~SummarizeKit uses a module listed above it, which is the healthy direction.
BrowserKit~SummarizeKit uses BrowserKit~Shared, so a change to BrowserKit~Shared can break BrowserKit~SummarizeKit, while a change to BrowserKit~SummarizeKit can't break BrowserKit~Shared.
Position
Below the diagonal: BrowserKit~SummarizeKit uses a module listed above it, which is the healthy direction.
BrowserKit~SummarizeKit uses MozillaRustComponents~FocusRustComponentsWrapper, so a change to MozillaRustComponents~FocusRustComponentsWrapper can break BrowserKit~SummarizeKit, while a change to BrowserKit~SummarizeKit can't break MozillaRustComponents~FocusRustComponentsWrapper.
Position
Below the diagonal: BrowserKit~SummarizeKit uses a module listed above it, which is the healthy direction.
BrowserKit~SummarizeKit uses BrowserKit~ComponentLibrary, so a change to BrowserKit~ComponentLibrary can break BrowserKit~SummarizeKit, while a change to BrowserKit~SummarizeKit can't break BrowserKit~ComponentLibrary.
Position
Below the diagonal: BrowserKit~SummarizeKit uses a module listed above it, which is the healthy direction.
BrowserKit~SummarizeKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~SummarizeKit, while a change to BrowserKit~SummarizeKit can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~SummarizeKit uses a module listed above it, which is the healthy direction.
27→34 BrowserKit~SummarizeKit uses BrowserKit~LLMKitpart of a loop✕
Connections
3 pairs of types, where a type in BrowserKit~SummarizeKit uses a type in BrowserKit~LLMKit.
BrowserKit~SummarizeKit uses BrowserKit~LLMKit, so a change to BrowserKit~LLMKit can break BrowserKit~SummarizeKit, while a change to BrowserKit~SummarizeKit can't break BrowserKit~LLMKit.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
27→36 BrowserKit~SummarizeKit uses repositorypart of a loop✕
Connections
96 pairs of types, where a type in BrowserKit~SummarizeKit uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~SummarizeKit uses repository, so a change to repository can break BrowserKit~SummarizeKit, while a change to BrowserKit~SummarizeKit can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~TabDataStore uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~TabDataStore, while a change to BrowserKit~TabDataStore can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~TabDataStore uses a module listed above it, which is the healthy direction.
28→36 BrowserKit~TabDataStore uses repositorypart of a loop✕
Connections
14 pairs of types, where a type in BrowserKit~TabDataStore uses a type in repository.
BrowserKit~TabDataStore uses repository, so a change to repository can break BrowserKit~TabDataStore, while a change to BrowserKit~TabDataStore can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~ToolbarKit uses focus-ios~BlockzillaPackage~UIHelpers, so a change to focus-ios~BlockzillaPackage~UIHelpers can break BrowserKit~ToolbarKit, while a change to BrowserKit~ToolbarKit can't break focus-ios~BlockzillaPackage~UIHelpers.
Position
Below the diagonal: BrowserKit~ToolbarKit uses a module listed above it, which is the healthy direction.
BrowserKit~ToolbarKit uses focus-ios~BlockzillaPackage~Onboarding, so a change to focus-ios~BlockzillaPackage~Onboarding can break BrowserKit~ToolbarKit, while a change to BrowserKit~ToolbarKit can't break focus-ios~BlockzillaPackage~Onboarding.
Position
Below the diagonal: BrowserKit~ToolbarKit uses a module listed above it, which is the healthy direction.
BrowserKit~ToolbarKit uses BrowserKit~Shared, so a change to BrowserKit~Shared can break BrowserKit~ToolbarKit, while a change to BrowserKit~ToolbarKit can't break BrowserKit~Shared.
Position
Below the diagonal: BrowserKit~ToolbarKit uses a module listed above it, which is the healthy direction.
27 pairs of types, where a type in BrowserKit~ToolbarKit uses a type in BrowserKit~Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~ToolbarKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~ToolbarKit, while a change to BrowserKit~ToolbarKit can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~ToolbarKit uses a module listed above it, which is the healthy direction.
29→36 BrowserKit~ToolbarKit uses repositorypart of a loop✕
Connections
87 pairs of types, where a type in BrowserKit~ToolbarKit uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~ToolbarKit uses repository, so a change to repository can break BrowserKit~ToolbarKit, while a change to BrowserKit~ToolbarKit can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~UnifiedSearchKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~UnifiedSearchKit, while a change to BrowserKit~UnifiedSearchKit can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~UnifiedSearchKit uses a module listed above it, which is the healthy direction.
30→36 BrowserKit~UnifiedSearchKit uses repositorypart of a loop✕
Connections
17 pairs of types, where a type in BrowserKit~UnifiedSearchKit uses a type in repository.
BrowserKit~UnifiedSearchKit uses repository, so a change to repository can break BrowserKit~UnifiedSearchKit, while a change to BrowserKit~UnifiedSearchKit can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~WebCompatReporterKit uses focus-ios~BlockzillaPackage~UIHelpers, so a change to focus-ios~BlockzillaPackage~UIHelpers can break BrowserKit~WebCompatReporterKit, while a change to BrowserKit~WebCompatReporterKit can't break focus-ios~BlockzillaPackage~UIHelpers.
Position
Below the diagonal: BrowserKit~WebCompatReporterKit uses a module listed above it, which is the healthy direction.
BrowserKit~WebCompatReporterKit uses focus-ios~BlockzillaPackage~Onboarding, so a change to focus-ios~BlockzillaPackage~Onboarding can break BrowserKit~WebCompatReporterKit, while a change to BrowserKit~WebCompatReporterKit can't break focus-ios~BlockzillaPackage~Onboarding.
Position
Below the diagonal: BrowserKit~WebCompatReporterKit uses a module listed above it, which is the healthy direction.
BrowserKit~WebCompatReporterKit uses BrowserKit~WebEngine, so a change to BrowserKit~WebEngine can break BrowserKit~WebCompatReporterKit, while a change to BrowserKit~WebCompatReporterKit can't break BrowserKit~WebEngine.
Position
Below the diagonal: BrowserKit~WebCompatReporterKit uses a module listed above it, which is the healthy direction.
BrowserKit~WebCompatReporterKit uses BrowserKit~Shared, so a change to BrowserKit~Shared can break BrowserKit~WebCompatReporterKit, while a change to BrowserKit~WebCompatReporterKit can't break BrowserKit~Shared.
Position
Below the diagonal: BrowserKit~WebCompatReporterKit uses a module listed above it, which is the healthy direction.
BrowserKit~WebCompatReporterKit uses BrowserKit~ComponentLibrary, so a change to BrowserKit~ComponentLibrary can break BrowserKit~WebCompatReporterKit, while a change to BrowserKit~WebCompatReporterKit can't break BrowserKit~ComponentLibrary.
Position
Below the diagonal: BrowserKit~WebCompatReporterKit uses a module listed above it, which is the healthy direction.
45 pairs of types, where a type in BrowserKit~WebCompatReporterKit uses a type in BrowserKit~Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~WebCompatReporterKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~WebCompatReporterKit, while a change to BrowserKit~WebCompatReporterKit can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~WebCompatReporterKit uses a module listed above it, which is the healthy direction.
31→36 BrowserKit~WebCompatReporterKit uses repositorypart of a loop✕
Connections
100 pairs of types, where a type in BrowserKit~WebCompatReporterKit uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~WebCompatReporterKit uses repository, so a change to repository can break BrowserKit~WebCompatReporterKit, while a change to BrowserKit~WebCompatReporterKit can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~MLPAKit uses BrowserKit~Shared, so a change to BrowserKit~Shared can break BrowserKit~MLPAKit, while a change to BrowserKit~MLPAKit can't break BrowserKit~Shared.
Position
Below the diagonal: BrowserKit~MLPAKit uses a module listed above it, which is the healthy direction.
BrowserKit~MLPAKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~MLPAKit, while a change to BrowserKit~MLPAKit can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~MLPAKit uses a module listed above it, which is the healthy direction.
BrowserKit~MLPAKit uses BrowserKit~AppAttestKit, so a change to BrowserKit~AppAttestKit can break BrowserKit~MLPAKit, while a change to BrowserKit~MLPAKit can't break BrowserKit~AppAttestKit.
Position
Below the diagonal: BrowserKit~MLPAKit uses a module listed above it, which is the healthy direction.
32→36 BrowserKit~MLPAKit uses repositorypart of a loop✕
Connections
10 pairs of types, where a type in BrowserKit~MLPAKit uses a type in repository.
BrowserKit~MLPAKit uses repository, so a change to repository can break BrowserKit~MLPAKit, while a change to BrowserKit~MLPAKit can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
BrowserKit~VPNKit uses BrowserKit~Shared, so a change to BrowserKit~Shared can break BrowserKit~VPNKit, while a change to BrowserKit~VPNKit can't break BrowserKit~Shared.
Position
Below the diagonal: BrowserKit~VPNKit uses a module listed above it, which is the healthy direction.
BrowserKit~VPNKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~VPNKit, while a change to BrowserKit~VPNKit can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~VPNKit uses a module listed above it, which is the healthy direction.
BrowserKit~VPNKit uses BrowserKit~AppAttestKit, so a change to BrowserKit~AppAttestKit can break BrowserKit~VPNKit, while a change to BrowserKit~VPNKit can't break BrowserKit~AppAttestKit.
Position
Below the diagonal: BrowserKit~VPNKit uses a module listed above it, which is the healthy direction.
33→36 BrowserKit~VPNKit uses repositorypart of a loop✕
Connections
32 pairs of types, where a type in BrowserKit~VPNKit uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~LLMKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~LLMKit, while a change to BrowserKit~LLMKit can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~LLMKit uses a module listed above it, which is the healthy direction.
BrowserKit~LLMKit uses BrowserKit~AppAttestKit, so a change to BrowserKit~AppAttestKit can break BrowserKit~LLMKit, while a change to BrowserKit~LLMKit can't break BrowserKit~AppAttestKit.
Position
Below the diagonal: BrowserKit~LLMKit uses a module listed above it, which is the healthy direction.
BrowserKit~LLMKit uses BrowserKit~SummarizeKit, so a change to BrowserKit~SummarizeKit can break BrowserKit~LLMKit, while a change to BrowserKit~LLMKit can't break BrowserKit~SummarizeKit.
Position
Below the diagonal: BrowserKit~LLMKit uses a module listed above it, which is the healthy direction.
BrowserKit~LLMKit uses BrowserKit~MLPAKit, so a change to BrowserKit~MLPAKit can break BrowserKit~LLMKit, while a change to BrowserKit~LLMKit can't break BrowserKit~MLPAKit.
Position
Below the diagonal: BrowserKit~LLMKit uses a module listed above it, which is the healthy direction.
34→36 BrowserKit~LLMKit uses repositorypart of a loop✕
Connections
24 pairs of types, where a type in BrowserKit~LLMKit uses a type in repository.
BrowserKit~QuickAnswersKit uses focus-ios~BlockzillaPackage~UIHelpers, so a change to focus-ios~BlockzillaPackage~UIHelpers can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break focus-ios~BlockzillaPackage~UIHelpers.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
BrowserKit~QuickAnswersKit uses focus-ios~BlockzillaPackage~Onboarding, so a change to focus-ios~BlockzillaPackage~Onboarding can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break focus-ios~BlockzillaPackage~Onboarding.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
BrowserKit~QuickAnswersKit uses BrowserKit~WebEngine, so a change to BrowserKit~WebEngine can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break BrowserKit~WebEngine.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
BrowserKit~QuickAnswersKit uses MozillaRustComponents~FocusRustComponentsWrapper, so a change to MozillaRustComponents~FocusRustComponentsWrapper can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break MozillaRustComponents~FocusRustComponentsWrapper.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
BrowserKit~QuickAnswersKit uses BrowserKit~SiteImageView, so a change to BrowserKit~SiteImageView can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break BrowserKit~SiteImageView.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
BrowserKit~QuickAnswersKit uses BrowserKit~ComponentLibrary, so a change to BrowserKit~ComponentLibrary can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break BrowserKit~ComponentLibrary.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
BrowserKit~QuickAnswersKit uses BrowserKit~OnboardingKit, so a change to BrowserKit~OnboardingKit can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break BrowserKit~OnboardingKit.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
BrowserKit~QuickAnswersKit uses BrowserKit~Common, so a change to BrowserKit~Common can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break BrowserKit~Common.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
BrowserKit~QuickAnswersKit uses BrowserKit~SummarizeKit, so a change to BrowserKit~SummarizeKit can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break BrowserKit~SummarizeKit.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
BrowserKit~QuickAnswersKit uses BrowserKit~MLPAKit, so a change to BrowserKit~MLPAKit can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break BrowserKit~MLPAKit.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
BrowserKit~QuickAnswersKit uses BrowserKit~LLMKit, so a change to BrowserKit~LLMKit can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break BrowserKit~LLMKit.
Position
Below the diagonal: BrowserKit~QuickAnswersKit uses a module listed above it, which is the healthy direction.
35→36 BrowserKit~QuickAnswersKit uses repositorypart of a loop✕
Connections
120 pairs of types, where a type in BrowserKit~QuickAnswersKit uses a type in repository. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
BrowserKit~QuickAnswersKit uses repository, so a change to repository can break BrowserKit~QuickAnswersKit, while a change to BrowserKit~QuickAnswersKit can't break repository.
Position
Above the diagonal, so it is part of a loop. Neither module can be changed, tested or released on its own until one of these dependencies is removed.
46 pairs of types, where a type in repository uses a type in focus-ios~BlockzillaPackage~DesignSystem. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses focus-ios~BlockzillaPackage~DesignSystem, so a change to focus-ios~BlockzillaPackage~DesignSystem can break repository, while a change to repository can't break focus-ios~BlockzillaPackage~DesignSystem.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses focus-ios~BlockzillaPackage~UIComponents, so a change to focus-ios~BlockzillaPackage~UIComponents can break repository, while a change to repository can't break focus-ios~BlockzillaPackage~UIComponents.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
61 pairs of types, where a type in repository uses a type in focus-ios~BlockzillaPackage~UIHelpers. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses focus-ios~BlockzillaPackage~UIHelpers, so a change to focus-ios~BlockzillaPackage~UIHelpers can break repository, while a change to repository can't break focus-ios~BlockzillaPackage~UIHelpers.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
30 pairs of types, where a type in repository uses a type in focus-ios~BlockzillaPackage~Onboarding. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses focus-ios~BlockzillaPackage~Onboarding, so a change to focus-ios~BlockzillaPackage~Onboarding can break repository, while a change to repository can't break focus-ios~BlockzillaPackage~Onboarding.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
104 pairs of types, where a type in repository uses a type in BrowserKit~WebEngine. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses BrowserKit~WebEngine, so a change to BrowserKit~WebEngine can break repository, while a change to repository can't break BrowserKit~WebEngine.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
156 pairs of types, where a type in repository uses a type in BrowserKit~Shared. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses MozillaRustComponents~FocusRustComponentsWrapper, so a change to MozillaRustComponents~FocusRustComponentsWrapper can break repository, while a change to repository can't break MozillaRustComponents~FocusRustComponentsWrapper.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses focus-ios~BlockzillaPackage~AppShortcuts, so a change to focus-ios~BlockzillaPackage~AppShortcuts can break repository, while a change to repository can't break focus-ios~BlockzillaPackage~AppShortcuts.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses BrowserKit~SiteImageView, so a change to BrowserKit~SiteImageView can break repository, while a change to repository can't break BrowserKit~SiteImageView.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
115 pairs of types, where a type in repository uses a type in MozillaRustComponents~MozillaRustComponentsWrapper. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses MozillaRustComponents~MozillaRustComponentsWrapper, so a change to MozillaRustComponents~MozillaRustComponentsWrapper can break repository, while a change to repository can't break MozillaRustComponents~MozillaRustComponentsWrapper.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
71 pairs of types, where a type in repository uses a type in BrowserKit~ComponentLibrary. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses BrowserKit~ComponentLibrary, so a change to BrowserKit~ComponentLibrary can break repository, while a change to repository can't break BrowserKit~ComponentLibrary.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
33 pairs of types, where a type in repository uses a type in BrowserKit~OnboardingKit. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses BrowserKit~OnboardingKit, so a change to BrowserKit~OnboardingKit can break repository, while a change to repository can't break BrowserKit~OnboardingKit.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
985 pairs of types, where a type in repository uses a type in BrowserKit~Common. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses BrowserKit~MenuKit, so a change to BrowserKit~MenuKit can break repository, while a change to repository can't break BrowserKit~MenuKit.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
39 pairs of types, where a type in repository uses a type in BrowserKit~Redux. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
39 pairs of types, where a type in repository uses a type in BrowserKit~SummarizeKit. Showing 25 of them; the rest are in namespace-graph.json in this report's bundle.
repository uses BrowserKit~SummarizeKit, so a change to BrowserKit~SummarizeKit can break repository, while a change to repository can't break BrowserKit~SummarizeKit.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses BrowserKit~TabDataStore, so a change to BrowserKit~TabDataStore can break repository, while a change to repository can't break BrowserKit~TabDataStore.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses BrowserKit~ToolbarKit, so a change to BrowserKit~ToolbarKit can break repository, while a change to repository can't break BrowserKit~ToolbarKit.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses BrowserKit~UnifiedSearchKit, so a change to BrowserKit~UnifiedSearchKit can break repository, while a change to repository can't break BrowserKit~UnifiedSearchKit.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses BrowserKit~WebCompatReporterKit, so a change to BrowserKit~WebCompatReporterKit can break repository, while a change to repository can't break BrowserKit~WebCompatReporterKit.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
repository uses BrowserKit~QuickAnswersKit, so a change to BrowserKit~QuickAnswersKit can break repository, while a change to repository can't break BrowserKit~QuickAnswersKit.
Position
Below the diagonal: repository uses a module listed above it, which is the healthy direction.
BrowserKit~ActionExtensionKit uses repository, so a change to repository can break BrowserKit~ActionExtensionKit, while a change to BrowserKit~ActionExtensionKit can't break repository.
Position
Below the diagonal: BrowserKit~ActionExtensionKit uses a module listed above it, which is the healthy direction.
BrowserKit~ContentBlockingGenerator uses repository, so a change to repository can break BrowserKit~ContentBlockingGenerator, while a change to BrowserKit~ContentBlockingGenerator can't break repository.
Position
Below the diagonal: BrowserKit~ContentBlockingGenerator uses a module listed above it, which is the healthy direction.
focus-ios~BlockzillaPackage~Licenses uses repository, so a change to repository can break focus-ios~BlockzillaPackage~Licenses, while a change to focus-ios~BlockzillaPackage~Licenses can't break repository.
Position
Below the diagonal: focus-ios~BlockzillaPackage~Licenses uses a module listed above it, which is the healthy direction.
At a glance — Code Health · 28% · Weak · gated by R1, R3, X5 ·
Findings mapped to OWASP categories; the specific CVEs/secrets are in the Security dimension cards below and findings.md (redacted only on the public version of this report).
OWASP category
Findings
Severity
A05:2025 — Injection
142
High / Critical
A02:2025 — Security Misconfiguration
8
High / Critical
A03:2025 — Software Supply Chain Failures
2
Medium
A01:2025 — Broken Access Control
2
Medium
Roadmap
Top priorities: Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up; Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package; Resolve the 1 Assertions commented out finding(s) in Test Quality — start with WKEngineSessionTests.swift.
Ranked by impact ÷ effort. "Helps" is the estimated gain on the 0–100 health score.
Do this
Helps
Effort
Dimension
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with WKEngineSessionTests.swift.
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Every finding carries one of four grades. Three say how serious it is. The fourth says this
survey could not settle it — and it is a grade, not a gap.
Critical — 53
A definite problem that already costs you something and drags the score down: a
missing authorisation check, a dependency with a known exploit, a build that does not reproduce. Failure here
tends to cause failures elsewhere.
Serious — 2306
Likely wrong, but not failing yet. It degrades
the codebase over a longer horizon and can cause failures elsewhere — not urgent this week, not something to
carry for two years either.
Minor — 266
Recorded, with no effect on how the codebase functions.
Present so the survey is complete, not because it needs doing.
Could not be resolved — 26
Something this survey could not settle
from the outside, and which could be critical or serious. Either a control was required and no
positive evidence of it exists in the repository — a backup job that nothing shows was ever restored from proves
nothing about restores — or our own analysis could not run over that part of the tree. This is not a clean
result. These are excluded from the score rather than awarded a pass, so the number on the cover neither
rewards nor penalises them: if you act on this survey without resolving them, you carry that risk yourself. Each
one is named under Limitations.
Methodology & how to trust this report
This survey is a deep, periodic assessment — run each sprint, monthly, or quarterly, taking the time to go wider and deeper than a quick check and surfacing in one coherent report what you'd otherwise piece together from a dozen separate tools. It scores deterministically: the same commit yields the same score, every run. All 62 evaluated dimensions are computed by tools and static analysis; no language model sets or judges any of them. Overall confidence is 0.9, the weighted average across measured dimensions.
Every figure here is one of two kinds, and we label which: ✓ Measured — a deterministic fact (LoC, complexity, coverage); ~ Modeled — an estimate from a stated model (cost, effort, value-at-risk), always a range with its assumptions, never a precise fact. We never present a modelled estimate as if it were measured. Perfect or absent scores carry their provenance too (ADR-0011): ✓ Tool-verified means the property itself was measured across the surface; ○ Nothing flagged means the probes came back clean — a claim bounded by what a repository can show; ⊘ Not evidenced means a working control (a tested restore, an automated rollback) showed no positive evidence — absence of evidence is not evidence of a control, so it's excluded from the score rather than awarded a spurious 10.
What we checked — 62 dimensions across the health lenses
Each chip is a dimension scored from real signals across architecture, testing, dependencies, security & compliance, documentation, git-history and code quality — in one coherent pass. A surface report typically covers a handful.
How to trust any code-health report — three questions
Can you open the finding? Real findings cite a repo-relative file and line you can open at the cited line — never an absolute scratch path. Here, 2596 of 2625 do; the remainder are repo-wide signals — a dimension-level measurement, not a single line. (Every path in this report is repo-relative by construction: paths are normalized at the producer and the report is rejected if any rooted path leaks through.)
Is there a tool behind the number? Every score below names the method that produced it: Roslyn, git or a scanner, not a narrative.
Does re-running give the same result? Run it again on the same commit and the score — and this report, byte for byte — is identical. A report whose numbers move between runs is describing the run, not the code.
This report answers yes to all three. That's the bar to hold any assessment to.
Tools & methods
The actual versions used this run (captured at analysis time) — re-run on the same commit for the identical score.
Method
Backs
Version
Evaluator
Roslyn static analysis
Complexity, cohesion, coupling, dead code, API surface, layering
What ran differently this time — a tool absent, degraded, or that fell back to an estimate. Named openly, not folded silently into the scores. A degraded run also records its exact cause in diagnostics.md.
D8 Code Coverage — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Coverage NOT MEASURED: the Swift half could not be measured — the Swift suite in . produced no coverage export. Coverage is excluded from the score rather than counted as a near-zero. This is OUR limitation, not a defect in the repo.
D10 Test Quality — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. The 6,492 test(s) behind this row are the ones the code-model census could read, and this repository also carries at least 20 test source file(s) (.py) that it cannot: it reads the test types the .swift frontend declared, so a suite in any other language is invisible to it. Skipped tests, zero-assertion tests and the other quality signals on this row are UNMEASURED in that suite — their absence from the counts above is a gap in this analyzer's language coverage, not a finding that those tests are sound.
D11 Test Reliability — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This repository declares 6 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.py, .swift), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Swift Package.swift/Package.resolved, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its SwiftPM dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares REDACTED, but the licence verdict published here was taken over its gem dependencies. Nothing was read about its npm dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D14 License Compliance — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. This repository declares a Python pyproject.toml/requirements.txt (pip/uv/Poetry), but the licence verdict published here was taken over its gem dependencies. Nothing was read about its Python dependencies' licensing in either direction, and a clean score on this card must not be read as covering them.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. D21's naming rules read C# through Roslyn and every other language through its sidecar model; these languages are left out (PHP's reading is its own change, a Roslyn-loaded VB or F# project has no population builder yet). Their declarations carry no naming verdict this run — this says nothing about whether their names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D21 Naming Consistency — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. PREREGISTRATION version 20's fallback (adjudication D21-sample3-v3): this rule kind was adjudicated below the 95 % precision gate, so its candidates are counted here and not published, and the score covers only the acronym-spelling and awaitable-suffix rules. The kind returns as rows only after it shows a measured precision; this says nothing about whether these names are consistent.
D22 Internal API Consistency — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. D22's deterministic call-shape rules are gated on C# first (docs/plans/deterministic-engine.md, P5): each other language is switched on only after its own concept suite and A/B gate pass. This says nothing about whether that surface is consistent.
D24 Comment Value — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. Each source language's comment syntax, and the code a comment annotates in it, needs its own proof before D24 judges it. Until then those comments are left unread, not counted as clean.
D28 Secrets (history) — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. `gitleaks` TIMED OUT after 466.7s against a 466.7s budget, so we killed its process tree. The budget is ours; the work may simply be larger than it allows. Nothing about this repository is asserted by the absence of a result; the budget is ours to raise, and raising it is our backlog item, not an action for this repository's owner.
D32 Data Compliance (PII/GDPR) — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. `BrowserKit/Sources/ActionExtensionKit/FirefoxURLBuilding.swift`, `BrowserKit/Sources/Common/ReaderMode/ReaderModeState.swift`, `BrowserKit/Sources/Common/Theming/ThemeType.swift`, `BrowserKit/Sources/ComponentLibrary/BottomSheet/NativeBottomSheetViewController.swift`, `BrowserKit/Sources/ComponentLibrary/Buttons/RoundedButtonWithImage.swift`, … (+113 more) produced a parse error, so every rule in this engine's `gdpr.yml` was absent there. That absence is NOT a clean result: these rules detect personal data crossing a boundary into a log sink, a URL or browser storage, and a file that was never parsed cannot report any of the three. The rest of the tree analysed normally and its rows above stand; only these files are unaccounted for. You can widen what we reach: fix the syntax error (or exclude the file deliberately) and re-scan to cover it.
AX1 Captive dependencies — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads Microsoft.Extensions.DependencyInjection registrations in C# and Spring beans in Java/Kotlin only, and this repository's container is Dip, whose lifetimes are not modelled yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
AXB2 Runtime readiness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. The dev server kept running but no port it opened served a page in the time allowed. (rule: no-answer). The renderer reported: the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "+ 2 modules / ./firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js 6.08 KiB [built] [code generated] / modules by path ./node_modules/ 473 KiB / modules by path ./node_modules/@mozilla/readability/*.js 92.2 KiB 3 modules / modules by path ./node_modules/page-metadata-parser/*.js 6 KiB 2 modules / ./node_modules/darkreader/darkreader.js 290 KiB [built] [code generated] / ./node_modules/dompurify/dist/purify.cjs.js 83.8 KiB [built] [code generated] / ./node_modules/script-loader/addScript.js 642 bytes [built] [code generated] / webpack 5.109.2 compiled successfully in 542 ms" No runtime evidence was gathered.
AXR1 Runtime accessibility — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. Render strategy: boot via DevServer (dev). the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "+ 2 modules / ./firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js 6.08 KiB [built] [code generated] / modules by path ./node_modules/ 473 KiB / modules by path ./node_modules/@mozilla/readability/*.js 92.2 KiB 3 modules / modules by path ./node_modules/page-metadata-parser/*.js 6 KiB 2 modules / ./node_modules/darkreader/darkreader.js 290 KiB [built] [code generated] / ./node_modules/dompurify/dist/purify.cjs.js 83.8 KiB [built] [code generated] / ./node_modules/script-loader/addScript.js 642 bytes [built] [code generated] / webpack 5.109.2 compiled successfully in 542 ms" No runtime evidence was gathered.
C1 Data Protection — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These personal data controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks personal data controls.
C2 Access Controls — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These authorization controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks authorization controls.
C3 Audit Trail — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These audit controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks audit controls.
GD1 Unfinished & placeholder code — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, F#, JavaScript/TypeScript, Dart, Ruby and Scala source only, and this repository's Python, Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
IC1 Incompleteness & stubs — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check reads C# syntax, JavaScript/TypeScript, Java, Dart, Ruby and Scala source only, and this repository's Python, Swift, c, objectivec is most of its product and is not read yet, so it had nothing of this repository's product to read. That is a gap in this analyzer's language reach — not a finding that the repository is free of what this check looks for.
M4 Documentation accuracy — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. M4 checks only the claim kinds adjudicated at or above 95 % precision: links and versions (PREREGISTRATION version 9), and artefact counts an order of magnitude off. Paths, command arguments, installs, environment variables, settings, projects, packages, routes, cd targets, infrastructure products and removed modules are read but not checked, and none of them is reported or counted.
P5 DR & Backup — not measured this run — This is a true statement about the repository that carries nothing for its owner to act on, so it is reported here rather than as a defect in their code. No backup/snapshot/replication config, RTO/RPO or restore-procedure documentation was found — and no production persistence was detected either (no data-access packages, no data-store services, no database resources), so there is nothing in this repository whose loss a DR control would recover. If this system's data lives in a platform or ops repo we can't see, that's where the DR evidence belongs.
R2 Cyclomatic Complexity — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 18 further occurrence(s) are not listed individually; the score already reflects all 58.
S1 Web-Security Posture — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. These web-security controls are read from declarative annotations, request middleware, entity/column names and guard methods in a C# source model, and none was loaded on this run, so there was nothing to gather. That is a gap in this analyzer's language reach — not a finding that the repository lacks web-security controls.
X1 Async correctness — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X10 Duplicated predicate — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. 3 further occurrence(s) are not listed individually; the score already reflects all 43.
X12 Unreachable branch — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X13 Undrained process stream — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X16 Unfloored truncation loop — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X19 Unrestored process-global state — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X2 Cancellation propagation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X21 Side-effecting pattern guard — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X23 Unguarded diagnostic materialisation — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X24 Document value interpolated into markup unescaped — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X27 Collection changed while being enumerated — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X29 Per-element action decided by a fixed element — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X3 Exception handling — measured, with a gap in what it reached — We measured this, but not all of it. What we did not reach is a gap on our side — a collector, parser or image we have not built yet — so the numbers on that dimension cover less than the repository, and the part left out is not evidence that it would have passed. 4 further occurrence(s) are not listed individually; the score already reflects all 44.
X30 Support guard that admits what it rejects — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
X4 Structured logging — not measured this run — We could not measure this here. That is a gap on our side — a collector, parser or image we have not built yet — and it is neither a defect in this repository nor evidence that the check would have passed. This check's reader does not cover most of the languages this repository's product is written in. What it read is kept, but it is too small a share to grade the product by. That is a gap in this analyzer's language reach — not a finding about this repository.
Repo exclusion declarations: 2 pattern(s) declared (.gitattributes linguist-generated/vendored, .editorconfig generated_code) excluded 0 source file(s) from code-quality scoring. Declarations are the repo's own visible statement that a tree is machine-written or vendored — auditable in any diff, honored by GitHub the same way.
Limitations & what we did not check
We assess the repository exactly as committed, and only the repository. By design we do not reach outside the source tree: the live cloud account, the running CI/CD pipeline, the host's branch-protection and approval rules, the production configuration, or a restore actually exercised against a backup are all out of scope. That boundary is a feature, not a gap — a repo-relative, deterministic scan re-runs identically on any commit and every finding opens at a real file and line, where a live audit can neither be reproduced nor traced. The visible consequence is that controls which leave no in-repo evidence are reported as "not evidenced" and excluded from the score rather than awarded a number a static scan cannot justify.
Per-dimension blind spots
For each dimension that was measured, what a static, repo-only scan structurally cannot see — the honest edge of the measurement, not a failure of it.
D1 Cyclomatic Complexity: Cyclomatic complexity counts branches statically — it cannot tell an essential decision tree from accidental tangle, nor see complexity that lives in data or configuration (large switch-case token tables, DSL lexers/parsers, data-as-code rule tables) rather than control flow: a tokenizer's many single-character cases read as high complexity though each branch is trivial.
D2 Cognitive Complexity: Cognitive-complexity heuristics approximate how hard code is to follow; genuine domain difficulty and well-named intent that eases reading are not captured.
D3 God Classes: "God class" is sized by members and responsibilities visible in the type — a deliberately broad facade over a coherent subsystem can read the same as an accidental grab-bag. For front-end JS the file-length check is cohesion-aware (a single-responsibility module — one class/IIFE — earns a 3× threshold), but cohesion is approximated from top-level declarations, not true dependency structure.
D4 Code Duplication: Duplication is token-similarity — an in-process token-stream comparison over sliding windows, with type-aware normalization — so it finds copy-paste, not semantic duplication expressed differently. Committed machine-written code (scaffolded migrations, designer/codegen output, protobuf/OpenAPI stubs, model snapshots) is EXCLUDED — its repetition is the tool's, not the team's — so the score reflects hand-written duplication only.
D5 Coupling: Coupling is measured between projects/assemblies — runtime coupling through DI, reflection, messaging or shared databases is invisible to a static reference graph.
D6 Cohesion (LCOM4): LCOM4 cohesion is syntactic — it infers connectivity from which methods touch which fields/methods by name, not from real runtime behaviour or intent.
D7 Architectural Integrity: Layering is checked against detected/declared rules — an architecture whose boundaries live in convention or in code review, not in a rule a scanner can read, is not enforced here.
D10 Test Quality: Assertion density is structural — it cannot tell a meaningful behavioural assertion from a trivial one, only that an assertion is present.
D12 Dependency Hygiene: Dependency health reads manifests and lockfiles — a vulnerability in a vendored/copied dependency, or risk from how a dependency is actually used, is outside this view.
D13 Secret Scanning: Secret detection is signature- and entropy-based on the current tree — a secret that does not match a known pattern, or one already rotated, will not be flagged (a clean scan is "nothing matched", not "no secrets exist").
D14 License Compliance: License compatibility is checked against declared package metadata and a policy — mislabelled or missing license metadata, and obligations that depend on how you distribute, are not resolved here.
D15 Churn × Complexity Hotspots: Churn hotspots come from git history — a freshly imported or squashed repository has no churn signal, and recent rewrites can mask a historically risky file.
D16 Bus Factor: Bus-factor is a time-decayed model of commit attribution (who has recently, repeatedly worked a file), not comprehension — pairing, review and reading-without-committing spread knowledge it can't see; bot commits and shared accounts still distort it.
D17 Explicit Debt: Acknowledged-debt signals (TODO/FIXME, suppressions, dead code) are textual — undocumented debt that nobody marked, and debt that lives in design rather than annotations, is invisible. Committed machine-written code (scaffolded migrations, designer/codegen output, generated stubs) is excluded — it is never the team's dead code to delete.
D19 Documentation Quality: Documentation quality publishes two things only: a runnable or packaged unit with no example, and a multi-project root README that maps none of its parts. It does not judge clarity, and its other checks (overview, licence, boilerplate, structure, empty sections, XML-doc coverage) are withheld after adjudication: their candidates are counted in the card's gaps, not shown as rows. A false statement in a document is M4's; units are .NET projects only.
D20 ADR Quality: ADR quality checks the structure of the decision records present: it cannot know about decisions made and never recorded, and it does not judge how well a record argues its case. Records in a language the section lexicon does not cover are not evaluated.
D21 Naming Consistency: Naming consistency compares each name with the convention its structural peers follow in this repository: it cannot tell whether a consistently used name is a good one, and languages other than C# and TypeScript are not measured.
D24 Comment Value: Comment value is measured as redundancy only: a comment that repeats its code's words is found, but a paraphrase in other words, a vague comment, or one the code contradicts is not, and whether a comment is valuable is not claimed. Comments in other scripts or languages, and outside C#, are not judged.
D26 Project Cohesion: Project focus is sized from members/namespaces per project — a project that is broad by deliberate design reads the same as one that has sprawled.
D27 Navigability: Indirection/navigability is structural — it measures hops to follow a call, not whether that indirection buys real flexibility or just ceremony.
D29 Static Analysis (SAST): SAST findings are pattern-based (semgrep) — it finds classes of bug it has rules for; logic flaws, auth/authorization gaps and issues needing runtime context are out of reach (and clean means "no rule matched").
D30 Dependency Vulnerabilities: CVE matching depends on accurate package/version metadata and on the advisory databases — a vulnerability with no published advisory, or in code not declared as a dependency, is not seen. Coverage needs a RESOLVED graph: an unpinned REDACTED, or a pom without a resolved build, yields partial coverage rather than a clean verdict. An ecosystem the analyzer cannot scan is reported as unmeasured, never as clean.
D31 IaC & Container Security: IaC scanning checks Dockerfiles/Terraform/Kubernetes against best-practice rules — it cannot see the live cloud account, runtime configuration, or drift between the committed config and what is actually deployed.
D32 Data Compliance (PII/GDPR): PII/GDPR signals are heuristic pattern matches in code — they flag likely handling concerns, not legal compliance, and cannot trace where data actually flows at runtime.
D34 Knowledge Freshness: Freshness is decayed commit RECENCY, not comprehension — code read often but rarely committed reads as orphaned, and stable code that genuinely needs no changes is penalised the same as forgotten code; bot/squash commits distort it like the bus factor.
D35 Change Coupling: Change coupling is co-change in COMMITS — files split across separate commits, or coupled only through a shared config/build step, read as uncoupled, and a sweeping commit (rename/format) is excluded so it doesn't couple everything. It shows that files change together, not WHY: a high coupling can be a healthy cohesive pair as readily as a hidden leak.
D43 Malicious Dependencies: Only packages some vulnerability database has already NAMED as malicious are seen — a compromise published in the last hours, or never reported at all, is invisible here, and this dimension reading 10 is not evidence that a dependency is trustworthy. There is no typosquat or dependency-confusion analysis: a package nobody has reported is simply absent from the feeds. Coverage is the dependency scan's: an ecosystem that could not be scanned is disclosed as unmeasured, never as clean.
D44 Platform End-of-Life: The support table is FROZEN, so it goes out of date by losing RECALL: a release that ended support after the table was written is missed until the table is refreshed, and this dimension reading 10 is not evidence that a platform is current. Only platforms the repository DECLARES in a place this pass reads are seen — a runtime named only in a REDACTED (D31's subject), in a CI workflow (D29's), or in a file this pass does not parse (go.mod, a Gemfile ruby directive) is invisible here, which is why a repository declaring none of them abstains rather than scoring. Only frameworks with a PUBLISHED support policy are tracked: React, Flask and Express publish none, so their age cannot be judged and their absence from a report is not a statement that they are supported.
AC2 Forms & labels: Label association is read from static markup — a label wired up at runtime (JS-set aria-labelledby, framework-injected ids) reads as missing, a present label says nothing about whether its text is correct. A known UI-library field component (e.g. a JSX <TextField>) is now checked conservatively — flagged only when it carries NO label/aria-label/aria-labelledby/id/name — but wrapper/context-labelled libraries (Chakra/Radix FormControl+FormLabel) aren't statically visible (possible false positive) and non-JSX lowercased components are still skipped. A click handler on a plain element is now asked for a name too (it is a control the author declared), but the subtree test that answers it is deliberately generous: any DYNAMIC text expression in the subtree counts as a name, so an icon chosen by a ternary ({cond ? <IconA/> : <IconB/>}) reads as named, and a glyph component from a library the icon-import list does not know still names its parent. A clean result is "no unlabelled control found", not a labelling proof.
AC3 Page structure: Page structure is read from the static markup tree — landmarks, headings and lang injected at runtime aren't seen, heading ORDER is checked structurally (not against the rendered visual hierarchy), and lang/title/main fire only on full documents, never partials, and the data-table check sees header-cell presence (a <th> exists), not whether each header correctly associates with its cells. Static readiness, not conformance.
AC6 Visual & motion safety: Contrast and motion safety are PARTIAL by construction — literal colours (hex/rgb/hsl/named) in inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS top-level declarations are read (same-rule/same-element colour+background pairs only); computed/runtime/theme colour, external-CDN stylesheets, CSS-in-JS dynamic (${…}) and nested-selector colours, cross-element pairs and image contrast stay out of reach, so a clean result is bounded by what the static CSS itself shows.
AX10 Code composition: Role is inferred from namespace/folder convention, not semantics — a domain concept living in a folder named "Services" reads as application, and the split is lines-of-code, not business value. The business-logic-share score is a SOFT, FLOORED signal: it contributes to the Architecture lens but is floored at the Critical gate, so an infrastructure-heavy design (a gateway, an ETL, a driver) is legitimately low without being nuked to zero.
AX9 CQS / query purity: Handlers are found by interface/name convention — a query handler using neither is not seen. Mutation is a resolved write/publish invocation (SaveChanges/repository/bus), so a write hidden behind a hand-rolled wrapper, reflection, or a string-keyed service locator resolves to a non-persistence type and isn't flagged; it detects that a query writes state, not whether the write is a legitimate read-side cache update. Clean means "no resolved write/publish in a query body", not a proof of CQS purity.
M4 Documentation accuracy: Documentation accuracy checks links, versions and artefact counts against the tree: other claims (paths, commands, settings, routes) are read but not checked, and it cannot run the onboarding or measure how long a real new joiner takes.
P4 Deployment & Rollback: Approval/branch-protection rules live in repository settings the scan cannot see — only their in-repo evidence (config files, workflows) is checked, so a control enforced purely in the host's settings reads as "not evidenced".
P6 Release Hygiene: Rollback/observability controls are inferred from repo artefacts (pipelines, dashboards-as-code) — controls configured in external tooling, with no in-repo trace, cannot be credited.
What it measures: How tangled the control flow is — methods with many branches are hard to test and change.
Method: Cyclomatic complexity per method (1 + decision points), computed exhaustively across production source; test projects separated by convention. Deterministic.
78 method(s) exceeded the cyclomatic complexity threshold of 15; the worst was TelemetryWrapper.gleanRecordEvent at 244. A further 23 method(s) were over the threshold but excluded as flat dispatchers (a long switch/match over independent cases: many branches, almost no nesting), the largest being ErrorPageHelper.swift.cfErrorToName at 83 — they are counted neither in the figure above nor in this dimension's score. 14 files carry no cyclomatic complexity row at all for this reason — every one of their over-threshold methods was excluded, so the exclusion is disclosed nowhere in the file itself: firefox-ios/Client/Nimbus/NimbusFeatureFlagLayer.swift (NimbusFeatureFlagLayer.checkNimbusConfigFor at 82), focus-ios/BlockzillaPackage/Sources/DesignSystem/Preview Files/AppColorsView.swift (AppColor.color at 37), firefox-ios/Client/Frontend/Settings/AppIconSelection/AppIcon.swift (AppIcon.displayName at 28), firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift (BrowserViewControllerState.reduceStateForGeneralBrowserAction at 23), firefox-ios/Client/Redux/GlobalState/PresentedComponentsState.swift (PresentedComponentsState.updateActiveComponents at 22), and 9 more not listed here. They are named here because the per-file figures other dimensions report are taken BEFORE this exclusion, so such a file can show a high maximum complexity elsewhere in this report and nothing here, with nothing to reconcile the two.
+ 59 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 1 body over 120 down to 120 or less in Cyclomatic Complexity — start with TelemetryWrapper.gleanRecordEvent (cyclomatic 244). — Refactoring it lifts Cyclomatic Complexity from 5.1 to about 5.8/10.
Detailed fixes: d1_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How hard the code is for a person to follow, beyond raw branching.
Method: Cognitive complexity per method (Sonar-style nesting-penalized score), computed exhaustively over production code, excluding test projects. Deterministic.
+ 119 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Bring the 2 bodies over 120 down to 120 or less in Cognitive Complexity — start with TelemetryWrapper.gleanRecordEvent (cognitive 183), BrowserSchema.update (cognitive 141). — This score is capped by its worst body, so a finding fixed alone moves it by almost nothing — the next one down takes its place. Refactoring these 2 together lifts Cognitive Complexity from 5.4 to about 5.8/10, projected with the scoring formula itself and assuming each lands exactly at 120; a cleaner split scores higher.
Detailed fixes: d2_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D3 · God Classes8.7 / 10Strong✓ Tool-verified
What it measures: Over-large classes that try to do too much ("god classes").
Method: God-class detection by line and method-count thresholds per logical type (partial classes unified), filtered for generated code and registration/contract false positives. Deterministic.
Resolve the 42 TooManyMethods finding(s) in God Classes — start with BrowserViewController.swift (3), BrowserCoordinator.swift, HomepageViewController.swift. — One of this dimension's main actionable groups (42 warning-level).
Resolve the 38 FileTooLong finding(s) in God Classes — start with BrowserViewController.swift (2), Strings.swift, bergamot-translator.js. — One of this dimension's main actionable groups (38 warning-level).
Resolve the 32 ClassTooLong finding(s) in God Classes — start with BrowserViewController.swift (2), REDACTED, BrowserCoordinator.swift. — One of this dimension's main actionable groups (32 warning-level).
Detailed fixes: d3_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: How much of the production code is copy-pasted: the share of production lines inside a reported copy (every copy of a duplicated block or of an edited member, each line once), 10 at none and 0 at a quarter of the lines.
Method: Code duplication via token-stream sliding windows with type-aware normalization (locals masked, type names preserved), scored on the share of production lines inside a reported copy (each line once; 10 at none, 0 at a quarter). Deterministic.
332 duplicated block group(s) detected. 8.3 % of the production lines (20,561 of 246,376) are in a reported copy. A further 531 rows report members as variants of one another; the share counts each copied line once, however many rows cite it. 1 of the 863 are in trees this repository does not ship — vendored, example/demo, project-template, fixture and benchmark code — and are ranked below the shipped groups rather than excluded from them: the duplication there is real and is still counted in this dimension's score. The dimensions that publish a production-file census leave those trees out of theirs, so this count is deliberately drawn over the wider population.
Edited copy of a member (9 corresponding lines) · ×41firefox-ios/Client/Extensions/UIViewController+Extension.swift:168
Edited copy of a member (13 corresponding lines) · ×29MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift:167
Edited copy of a member (6 corresponding lines) · ×27firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:157
+ 160 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 41 Edited copy of a member (9 corresponding lines) finding(s) in Code Duplication — start with WebsiteDataManagementViewController.swift (3), BackgroundAudioHelper.swift (2), UIViewController+Extension.swift. — One of this dimension's main actionable groups (41 warning-level).
Resolve the 32 Duplicated block (8 lines × 2) finding(s) in Code Duplication — start with PullRefreshView.swift (4), FeatureVariables.swift (2), NimbusCreate.swift (2). — One of this dimension's main actionable groups (32 warning-level).
Resolve the 29 Edited copy of a member (13 corresponding lines) finding(s) in Code Duplication — start with FxAKeychain.swift, JsonHelper.swift, PullRefreshView.swift. — One of this dimension's main actionable groups (29 warning-level).
Detailed fixes: d4_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D5 · Coupling8.8 / 10Strong✓ Tool-verified
What it measures: Whether volatile projects sit underneath others that depend on them (so their churn ripples upward), and whether project dependencies form cycles. A widely-depended-on but stable shared/kernel project is healthy, not penalised.
Method: Dependency cycles via elementary-DFS over real .csproj references, plus Martin instability (afferent/efferent) per project. Exhaustive over the reference graph, deterministic.
Coverage: Exhaustive · type-level: afferent/efferent coupling + cycles computed over every production type — the population is all types, not a name convention.
33 production modules (npm+SwiftPM), 0 dependency cycle(s), 0 unstable depended-on module(s). Read from the build's own module declarations; 5 module(s) off the main sequence, with abstractness counted on 30 of the 33 (the rest declare no modelled class or interface, export only macros, declare types in source no model reads, or have no source directory of their own).
Off the main sequence: DesignSystem · ×5
What to do
Resolve the 5 Off the main sequence finding(s) in Coupling. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d5_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether a class's methods are focused on a single responsibility.
Method: LCOM4 cohesion per production class with at least two methods: connected components of methods sharing state or calls, computed syntactically. Deterministic, not a proxy.
Coverage: Exhaustive · type-level: LCOM4 cohesion computed over every production class — the population is all types, not a name convention.
Resolve the 105 Low cohesion finding(s) in Cohesion (LCOM4) — start with FeatureVariables.swift (4), BrowserViewController.swift (3), PhotonActionSheet.swift (2). — One of this dimension's main actionable groups (105 warning-level).
Detailed fixes: d6_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the code respects its intended layering / architecture rules.
Method: Enforcement rung (Prevented/Verified/Documented) per checkable ADR via Roslyn, plus dependency cycles via the engine shared with D5/AX3. Deterministic, exact.
No mechanizable ADR was identified, so enforcement is not measured. Dependency cycles not checked (no project-reference graph; where this repository's language has an import-cycle lens, cycles are reported there).
Detailed fixes: d7_recommendation.md.
Do you agree with this assessment?
D10 · Test Quality9.3 / 10Adequategated by 1 critical finding✓ Tool-verified
What it measures: Whether the tests truly assert behaviour rather than just running the code.
Method: Per-test assertions, skips, and mock references analyzed via Roslyn; structured skip-reason tags (BUG:/ENV:) separate documented deferrals from debt. Deterministic.
19 skipped, 257 zero-assertion, no mocking-framework packages referenced (hand-written doubles or no mocking) across 6492 tests. Measured on the .swift suite only — at least 20 test source file(s) (.py) went unread, so its test quality is unmeasured and is not in these counts.
Test project verifies nothing: StoragePerfTestsfirefox-ios/firefox-ios-tests/Tests/StoragePerfTests/StoragePerfTests.swift:11
What to do
Resolve the 1 Assertions commented out finding(s) in Test Quality — start with WKEngineSessionTests.swift. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 256 No assertions finding(s) in Test Quality — start with TelemetryWrapperTests.swift (61), ConversionEventTrackerTests.swift (13), ToolbarMiddlewareTests.swift (7). — One of this dimension's main actionable groups (256 warning-level).
Resolve the 19 Skipped test finding(s) in Test Quality — start with BrowserCoordinatorTests.swift (3), TabTests.swift (2), AppleIntelligenceUtilTests.swift (2). — One of this dimension's main actionable groups (19 warning-level).
Detailed fixes: d10_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether dependencies are current, not deprecated, and not bloated. Known vulnerabilities are D30's.
Method: Manifest scan via dotnet list package across all projects; worst-signal-per-package deduction (capped-linear for deprecation, prerelease and outdated) per KLoC. Known-vulnerable packages are D30's and are not charged here (rubric-2026.11.2). Exhaustive.
2 outdated direct SwiftPM dependencies, 2 pinning defect(s). 8 of 12 direct dependencies had their releases listed (0 naming no readable repository, 4 pinned to a branch or a revision rather than a version). SwiftPM has no package registry: a dependency is a repository URL and its releases are that repository's semver tags, so currency is answered by listing tags rather than by querying an index. Only a newer tag on the SAME MAJOR is reported — a `from:` requirement admits everything below the next major and nothing above it, so a major crossing needs a Package.swift edit rather than an update, and naming the update as its remedy would be wrong. Whether any dependency is DEPRECATED or ABANDONED is not graded and cannot be: a repository publishes no such marker, and there is no registry that could carry one. Known CVEs in this dependency graph are D30's question.
Floating branch dependency: fuzi · ×2
Outdated: kingfisher · ×2
What to do
Resolve the 2 Floating branch dependency finding(s) in Dependency Hygiene. — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d12_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any secrets (keys, tokens, passwords) have leaked into the code.
Method: In-process native secret scanner (entropy plus signature patterns) across all tracked files; no external tool. A clean result is a measured 10, not no-data zero. Deterministic.
Secret scan ran and found no leaked secrets. 1 detection(s) were excluded as holding no minted credential in material that runs: a name, reference or comparison rather than a value, a readable phrase or pattern, a value that declares itself fake, or development, test, example, mock or demo material.
What it measures: Whether the licenses of third-party packages are compatible with your policy.
Method: Third-party package licenses resolved from declared package metadata and checked against the configured policy (allow/deny/copyleft). Deterministic; clean = no incompatible license found at metadata depth.
0 of 1 shipped gem(s) use a banned license. Licences were resolved from rubygems.org over the 1 runtime gem(s) this repository declares. It commits no Gemfile.lock to close that set over, so the verdict covers the declarations rather than the whole resolved graph. Development-group and `add_development_dependency` gems are excluded: they are not distributed with this repository. ★ COVERAGE OF THIS VERDICT: it grades this repository's gem dependencies and nothing else. The repository also declares a Swift Package.swift/Package.resolved, REDACTED and a Python pyproject.toml/requirements.txt (pip/uv/Poetry), and the licences of those dependency graphs were NOT read by this pass — a gap in this engine's coverage, not a statement about them. So this result says the graded closure carries no banned licence; it does NOT say this repository's licensing is clear.
What it measures: Files that change often and are also complex — the riskiest hotspots.
Method: Per production file churn times cyclomatic complexity over a rolling window, computed from git and Roslyn/JS/Razor analysis. Exhaustive, deterministic per commit date.
Top hotspots: firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift (49×30=1470); firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift (33×19=627); firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift (17×31=527) Repeated repair below the complexity floor: BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift (8 of 8 changes were fixes); firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift (7 of 13 changes were fixes); firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift (7 of 11 changes were fixes)
Resolve the 26 Repeated repair finding(s) in Churn × Complexity Hotspots — start with WebCompatReportSheetViewController.swift, TabTrayViewController.swift, BookmarksViewController.swift. — One of this dimension's main actionable groups (26 warning-level).
Resolve the 6 Hotspot finding(s) in Churn × Complexity Hotspots — start with BrowserViewController.swift, BrowserCoordinator.swift, BrowserViewController+WebViewDelegates.swift. — One of this dimension's main actionable groups (6 warning-level).
Detailed fixes: d15_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D16 · Bus Factor9.1 / 10Exemplary✓ Tool-verified
What it measures: Whether knowledge is concentrated in too few people (the "bus factor").
Method: Living knowledge per author via time-decayed commit attribution (6-month half-life, focus weighting) across largest source files. Deterministic, avoids blame's mechanical-refactor false positives.
104 source file(s) have their living knowledge concentrated in one author (≥90% of recent, decayed contribution). The largest is scripts/update_release_notes.py. Counted over 1112 of the 2156 production source files in this repository: 1041 are under the ~2,400-byte size floor this dimension measures over, and the remaining 3 have no attributable history left to measure.
Off-boarding risk: anonymized user #1 · ×10
Further sole-owners (lower concentration)
✓ On the Gold path — maintain.
Detailed fixes: d16_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Acknowledged debt left in the code — TODOs, dead code, suppressed warnings.
Method: Roslyn syntactic debt markers (suppressions/TODO/FIXME/HACK/empty-catch/commented-code/Obsolete) plus SymbolFinder dead-code analysis; weighted-debt-per-KLoC density deducted 2.0x per unit. Deterministic, exhaustive.
393 deducted task-comment markers across 246376 LoC (0.2/KLoC) → score 9.7. Task comments only: this repository's language is read without a compiler, so D17's suppression, dead-code and commented-out-code arms did not run and this score counts fewer marker kinds than a .NET repository's would.
TodoComment repeated across 25 filesfirefox-ios/Client/TabManagement/TabWebView.swift:37
What to do
Resolve the 300 TodoComment finding(s) in Explicit Debt — start with MenuTests.swift (10), ContextMenuState.swift (9), WKNavigationHandler.swift (8). — One of this dimension's main actionable groups (300 warning-level).
Resolve the 59 FixmeComment finding(s) in Explicit Debt — start with Nimbus.swift (4), FxAccountManager.swift (3), Deferred.swift (3). — One of this dimension's main actionable groups (59 warning-level).
Resolve the 5 XxxComment finding(s) in Explicit Debt — start with screenshots_locales.py, TestHistory.swift, BrowserViewController.swift. — One of this dimension's main actionable groups (5 warning-level).
Detailed fixes: d17_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the project's documentation is clear, complete, and useful.
Method: Every README, docs/ document and root guide parsed by its markup and measured in Unicode letters. Published: a runnable or packaged .NET project whose README (or a document it links, or a root guide) shows no example, and a root README naming none of three or more projects. Overview, licence, boilerplate, wall-of-text, empty-section and XML-doc rows are measured and withheld (counted in gaps) after adjudication. Deterministic, exhaustive, advisory.
1 of 1 documentation facets pass in full. 22 document(s) read across 1 unit(s).
✓ On the Gold path — maintain.
Detailed fixes: d19_recommendation.md.
Do you agree with this assessment?
D20 · ADR Quality9.9 / 10Exemplary✓ Tool-verified
What it measures: Whether architecture decisions are recorded well (context, decision, consequences).
Method: Every ADR read by its section structure: nine located rules (a missing Decision, Context or Consequences section, a stale status, two records deciding the same question, a dangling supersede link, a number-only title, a single option, no named cost, no status where the log uses one, no enforcement field where the log adopted one), each a fixed deduction from 10; the score is the mean over evaluated records. Deterministic, no model. Advisory.
1 of 15 evaluated ADRs have a defect readable from the log itself (a missing or empty section, no title, a single option, consequences with no cost, no status, a missing enforcement field, a status the log contradicts, a dangling link, an unlinked second decision on one question, a date that is no calendar day). How well each record argues its case is not measured.
ADR consequences name no costadr/0013-redux-state-reducers-best-practices-initialization-and-transient-state.md:116detected by adr-integrity
✓ On the Gold path — maintain.
Detailed fixes: d20_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether names — types, methods, variables — are clear and consistent.
Method: Seven vocabulary-free rules (N1-N7) mine each naming convention from the repository and flag a name that breaks a convention its structural peers in the same unit follow; production C# and TypeScript, each its own population. Deterministic, no model, no sample. Advisory.
4 naming inconsistencies among 827 declarations measured against a convention their peers follow.
`FfiConverterTypeContextIDComponent` spells `ID` where 232 names in the project spell it `Id` · ×2MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/context_id.swift:712
`PlacesAPI` spells `API` where 35 names in the project spell it `Api`MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Places.swift:26
`generateUuidAndFormatAction` spells `Uuid` where 685 names in the project spell it `UUID`firefox-ios/Client/Experiments/Messaging/GleanPlumbMessageManager.swift:237
✓ On the Gold path — maintain.
Detailed fixes: d21_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether comments are worth it — explaining WHY (valuable) rather than WHAT (redundant).
Method: Every inline C# comment compared word by word with the identifiers, literals and constructs of the code it annotates (taken from the syntax); a comment whose words that code already contains is redundant, as are closing-brace labels and generator template text. Comments giving a reason or a reference are kept; other scripts and languages are not judged. Deterministic, exhaustive, advisory.
10 of 1047 judged comments only repeat the code they sit on (1.0 %). 34 comment(s) in another language or script were not judged.
redundant comment · ×10REDACTED:770
doc comments repeat the namesfirefox-ios/Client/Assets/CC_Script/FieldScanner.sys.mjs:260
What to do
Resolve the 10 redundant comment finding(s) in Comment Value — start with LoginFormState.sys.mjs (3), REDACTED, FormAutofillSection.sys.mjs. — One of this dimension's main actionable groups (10 recommendation-level).
Detailed fixes: d24_recommendation.md · top locations in Appendix A, every location in findings.md.
4 of 8 build units (SwiftPM, Xcode, npm) flagged as possibly oversized/incoherent.
Projects may be oversized for their cohesion
What to do
Resolve the 1 Projects may be oversized for their cohesion finding(s) in Project Cohesion. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d26_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D27 · Navigability8.8 / 10Strong✓ Tool-verified
What it measures: How far you must trace to follow a call — low indirection and co-located slices read easier.
Method: Call indirection (interface hops, cross-namespace calls, slice-locality scaled) over a sampled set of method invocations, size-aware baseline. Sampled; confidence discounted by symbol-resolution gaps. C# also names each pass-through layer (a class whose every public method only forwards its own parameters to one collaborator) as a located finding; the score is not affected.
Coverage: Slice locality from the first namespace segments, SAMPLED (≤400 methods) — not exhaustive.
1 % of calls cross a namespace and 25 % go through an interface, but 100 % of collaborators are co-located — so following a call takes several hops. Baseline: small — navigation cost is tolerated.
What it measures: Real static-analysis (SAST) findings — likely security bugs in the code, any language.
Method: Polyglot static analysis via semgrep across the repo using the pinned, image-baked p/security-audit + p/owasp-top-ten rulesets (no scan-time registry fetch); severity rules (ERROR/WARNING/INFO) map to a full-band severity-weighted score. Exhaustive, deterministic; degrades on parse failure.
Coverage: semgrep pattern rules over all files — exhaustive for the rule set, blind to classes of bug without a rule (clean = no rule matched).
142 finding(s): 0 critical, 12 high, 115 medium, 15 low. semgrep hit a parse error in 10 file(s) — `SampleBrowser/SampleBrowser/Engine/Scripts/MainFrameAtDocumentStart.js` (line 2), `firefox-ios/Client/ContentBlocker/ContentBlocker.swift` (line 422), `firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift` (line 575, line 576, line 578, …), `firefox-ios/Client/Telemetry/TelemetryWrapper.swift` (line 768), `firefox-ios/RustFxA/RustFirefoxAccounts.swift` (line 48), … (+5 more) — so no absence of findings in the named regions is evidence of anything; rows reported elsewhere in those files are real. Fix the syntax error (or exclude the file deliberately) and re-scan to cover them. Separately, one or more rules could not re-parse an embedded snippet in 11 file(s) (e.g. a workflow `run:` block read as shell). Those files WERE scanned and their other rows are unaffected; only those rules' view of those snippets is missing.
REDACTED
REDACTED
REDACTED
REDACTED
REDACTED
+ 10 more group(s) — more in Appendix A; the complete list is findings.md.
What to do
Resolve the 9 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED, REDACTED. — One of this dimension's main actionable groups (9 issue-level).
Resolve the 2 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED, REDACTED. — One of this dimension's main actionable groups (2 issue-level).
Resolve the 1 REDACTED finding(s) in Static Analysis (SAST) — start with REDACTED. — One of this dimension's main actionable groups (1 issue-level).
Detailed fixes: d29_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether any dependency has a known published vulnerability (CVE), direct or transitive, in ANY ecosystem the repository declares — Dart pub, Elixir and Erlang via Hex, Go modules, Java and Kotlin via Maven/Gradle, JavaScript/npm, .NET/NuGet, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift.
Method: Dependency-CVE scan across every ecosystem the repository declares, scored ONCE. Three sources are unioned and deduplicated by advisory identity (rule id + alias closure, CVE<->GHSA) scoped to package+version, keeping the worst severity: `osv-scanner --recursive` over osv.dev for Dart pub, Elixir/Hex (and Erlang, whose `rebar.lock` syft first converts to a CycloneDX SBOM the scanner reads, with rows attributed back to the lock), Go, Java and Kotlin via Maven/Gradle (and Scala, whose sbt build's pinned direct declarations are written into a CycloneDX SBOM the scanner reads, with rows attributed back to the build file), npm, PHP/Composer, Python/PyPI, RubyGems, Rust/Cargo and Swift; `trivy fs --scanners vuln` for npm lockfiles; and `dotnet list package --vulnerable --include-transitive` for NuGet (with per-advisory collapse of the project x target-framework fan-out), plus a DECLARED-dependency arm that resolves a published gem's gemspec against rubygems.org where no Gemfile.lock is committed. `SeverityScore(c,h,m,l, normalizer 8.0)`. NotApplicable only when NO ecosystem is readable; if any applicable ecosystem could not be scanned the findings are REPORTED and the score is withheld. Supersedes the npm and OSV arms, retired 2026-09-05. Advisory since rubric-2026.11.2 (CAI decision 0006): every row is a match against a vulnerability database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
Resolve the 1 Medium CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 warning-level).
Resolve the 1 Low CVE finding(s) in Dependency Vulnerabilities — start with REDACTED. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d30_recommendation.md · top locations in Appendix A, every location in findings.md.
Resolve the 5 High IaC finding(s) in IaC & Container Security — start with REDACTED (5). — One of this dimension's main actionable groups (5 issue-level).
Resolve the 3 Medium IaC finding(s) in IaC & Container Security — start with REDACTED (3). — One of this dimension's main actionable groups (3 warning-level).
Detailed fixes: d31_recommendation.md · top locations in Appendix A, every location in findings.md.
Do you agree with this assessment?
D32 · Data Compliance (PII/GDPR)8.1 / 10Strong✓ Tool-verified
What it measures: Likely personal-data (PII / GDPR) handling concerns — logging or storing data without safeguards.
Method: Heuristic PII/GDPR LEAK scan via semgrep across the repo, using our own ruleset: personal data crossing a boundary it should not — reaching a log/console sink, a URL or query string, or unprotected browser storage. Matches map to severity and a 0-10 wide normalizer. A clean sweep is unscored rather than an unearned 10, and is a statement about the leak paths checked only — this dimension does not inventory the personal data a repository holds (the personal-data map and the C1-C5 compliance cards do that), so it never reports that a repository has no personal-data surface. Reported LOUDLY as a measurement gap if the ruleset is missing from the analyzer image. Exhaustive over the leak paths, advisory-leaning; degrades on parse failure.
2 finding(s): 0 critical, 0 high, 2 medium, 0 low. semgrep could not parse 118 file(s) — `BrowserKit/Sources/ActionExtensionKit/FirefoxURLBuilding.swift`, `BrowserKit/Sources/Common/ReaderMode/ReaderModeState.swift`, `BrowserKit/Sources/Common/Theming/ThemeType.swift`, `BrowserKit/Sources/ComponentLibrary/BottomSheet/NativeBottomSheetViewController.swift`, `BrowserKit/Sources/ComponentLibrary/Buttons/RoundedButtonWithImage.swift`, … (+113 more) — so the PII/GDPR sweep did not cover the unparsed regions of them; rows reported elsewhere in those files are real.
REDACTED
What to do
Resolve the 2 REDACTED finding(s) in Data Compliance (PII/GDPR) — start with REDACTED (2). — One of this dimension's main actionable groups (2 warning-level).
Detailed fixes: d32_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether anyone still has living knowledge of each file, or it has been orphaned — last understood long ago by someone now gone quiet. The sibling of the bus factor: D16 asks who owns it, D34 asks whether anyone still knows it.
Method: File orphaning as total living-knowledge decay below one focused-commit's worth within a year, computed per-file from the D16 decay model. Exhaustive, deterministic over fixed history.
135 of 1115 significant source file(s) are orphaned — their living knowledge has decayed to nothing, so no one currently understands them. The largest is firefox-ios/Client/Frontend/NativeErrorPage/NativeErrorBadCertContentView.swift. Counted over 1115 of the 2156 production source files in this repository: the rest are under the ~2,400-byte size floor this dimension measures over.
Resolve the 1 Orphaned knowledge finding(s) in Knowledge Freshness — start with NativeErrorBadCertContentView.swift. — One of this dimension's main actionable groups (1 issue-level).
Resolve the 134 Orphaned file finding(s) in Knowledge Freshness — start with ReadWriteLock.swift (2), FeatureVariables.swift, GleanPlumbMessageManager.swift. — One of this dimension's main actionable groups (134 recommendation-level).
Resolve the 1 Further orphaned files (smaller) finding(s) in Knowledge Freshness. — One of this dimension's main actionable groups (1 recommendation-level).
Detailed fixes: d34_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether files that change together actually belong together — pairs that repeatedly co-change in git history despite having no explicit code dependency, surfacing the hidden/logical coupling (and boundaries in the wrong place) a static scan can't see.
Method: Pairwise co-occurrence over the per-commit file sets in git history (production source only — tests and generated dropped): Degree-of-Coupling = shared ÷ min individual revisions, reported above noise floors (each file ≥10 revisions, ≥5 shared commits, ≥50% strength); sweeping commits excluded. Deterministic over fixed history.
Coverage: Population: PRODUCTION source files only — test and generated files are dropped before pairing, so a class co-changing with its own test (trivially ~100%) can't drown the real production↔production coupling. Pairs ranked by Degree-of-Coupling. A non-source file is never a coupling PARTICIPANT either: documentation, schemas, config and data files are dropped with the rest, so a code↔docs pair — a command and the reference page that restates it — is not reported however strongly the two co-change; nor is coupling that runs THROUGH a build step or config file.
Resolve the 10 Boundary-crossing change coupling finding(s) in Change Coupling — start with LocationViewState.swift (2), WebCompatReportSheetPreview.swift, WKEngineSession.swift. — One of this dimension's main actionable groups (10 issue-level).
Resolve the 18 Change coupling finding(s) in Change Coupling — start with BookmarksSectionState.swift (2), ContextualHintCopyProvider.swift, AddressToolbarContainerModel.swift. — One of this dimension's main actionable groups (18 warning-level).
Resolve the 4 Change-coupling hub finding(s) in Change Coupling — start with BrowserViewController.swift, TabDisplayModel.swift, HomepageViewController.swift. — One of this dimension's main actionable groups (4 warning-level).
Detailed fixes: d35_recommendation.md · top locations in Appendix A, every location in findings.md.
What it measures: Whether the repository publishes a coordinated-vulnerability-disclosure policy (SECURITY.md or security.txt) with a reporting contact, so finders know how to report a vulnerability. Presence of a policy file with a contact, not whether the policy is adequate or honoured.
Method: Vulnerability-disclosure policy read deterministically from the repo: a SECURITY.md (root/.github/docs) or .well-known/security.txt / security.txt, regex-checked for a reporting contact (email / URL / mailto). Present + contact → 10; present without a contact → 4; NotApplicable when no policy file exists (it may live off-repo). Detects the policy file's presence + contact, not its adequacy.
What it measures: Whether any dependency the repository declares is published as MALICIOUS rather than merely vulnerable — a package that is an attacker's work, in any ecosystem osv-scanner reads. Reported apart from D30 because the answer is binary: there is no safe version to upgrade to, and the fix is to remove the package and rotate every credential it could have read.
Method: The same dependency scan D30 reads, partitioned on the scanner's own classification rather than rescanned: a row is MALICIOUS when its id is in the `MAL-` space (the ossf/malicious-packages feed) OR its `database_specific.cwe_ids` carries `CWE-506` ("Embedded Malicious Code"). Both channels are structural; the summary text is deliberately NOT read, because a malicious-package record whose summary says only "Critical severity vulnerability" is a real shape ([GHSA redacted]) and a text matcher misses it. Scored BINARY: any surviving row is 0, whatever its severity and however many CVEs sit beside it — a hostile dependency is not a quantity. Applicability and degradation are D30's: NotApplicable only when no ecosystem is readable, and an unscannable ecosystem degrades rather than reading clean. Advisory since rubric-2026.11.2 (CAI decision 0006): the malicious-package feed is a database that changes daily, so the reading is shown and never moves a scored dimension, lens or the headline.
What it measures: Whether anyone still ships security patches for the platform this repository RUNS ON — the runtime it pins and the framework majors its own constraints hold it to. Separate from D12 because the question differs: a current Django on an end-of-life Python is perfectly up to date and completely unsupported, and the fix is a migration rather than a version bump. What the repository says it merely SUPPORTS is never charged.
Method: End-of-life PLATFORM read from the repository's own declarations and graded against a FROZEN, dated table of vendor support dates — no network, no feed, no API, so this dimension answers identically inside a closed scan fence. Two subjects: a RUNTIME the project pins (a single or all-end-of-life TargetFramework, a .nvmrc or .python-version, a requires-python CAP) and a FRAMEWORK major a dependency constraint cannot move off (a caret, tilde or exact version; `vue@^2.7.16` pins Vue 2). A FLOOR is deliberately never charged — `requires-python = ">=3.8"` states what a package SUPPORTS, not what it runs on — and a multi-target project is charged only when EVERY target is out of support. Runtime 4.0/product capped 8.0, framework 1.5 capped 4.5. The table is safe to freeze because a statement about support that ended in the past cannot become false: it loses recall as it ages, never precision, and a test asserts every entry predates the freeze date. Disjoint from D31 (a container image's OS layer) and D29 (the toolchain a CI workflow installs). Abstains when the repository declares no platform this pass reads — never scores it clean.
0 end-of-life runtime(s) and 0 end-of-life framework(s), read from 0 platform declaration(s) and 41 dependency declaration(s). This dimension reads what the repository says about ITSELF — a pinned target framework, a version file, a capped requires-python, a Rust toolchain pin, a framework major a constraint cannot move off. A FLOOR is deliberately never charged: `requires-python = ">=3.8"` states what the package SUPPORTS, not what it runs on, and a well-maintained library declares exactly that while running its own CI on a current release. The end-of-life facts are FROZEN and dated, so this dimension needs no network and answers identically inside a closed scan fence; as the table ages it loses recall and never precision, because a statement about support that ended in the past cannot become false. The OS layer of a container image is D31's question and the toolchain a CI workflow installs is D29's; this row is neither.
✓ On the Gold path — maintain.
Detailed fixes: d44_recommendation.md.
Do you agree with this assessment?
Frontend & cross-cutting dimensions
R = React/JS · M = Maturity · P = Readiness.
AC2 · Forms & labels10.0 / 10Exemplary○ Nothing flagged
Other · Accessibility — Whether form controls have a programmatic label (an associated label, aria-label or aria-labelledby), buttons have text, links have an accessible name, a click handler on a plain element names the control it declares, fieldsets have a non-empty legend, known UI-library field components carry a label prop, and a placeholder isn't used as the only label. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: inputs/selects/textareas checked for an associated label[for]/wrapping label/aria-label/aria-labelledby (per document), buttons for accessible text, fieldsets for a legend; placeholder-only labelling flagged. Deterministic, hard fact per control.
Coverage: Population: form controls, buttons, links, fieldsets and known UI-library field components in the PARSED MARKUP files only (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx); components, hidden subtrees and spread/dynamic-attribute elements are skipped, so a control whose label arrives through a spread or a runtime expression is deliberately not judged. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
Do you agree with this assessment?
AC3 · Page structure4.9 / 10Weak✓ Tool-verified
Other · Accessibility — Whether pages declare a language (well-formed BCP-47) and a non-empty title, expose exactly one main landmark and a sane heading order with non-empty headings, keep zoom enabled, title their iframes, give data tables header cells, and avoid meta-refresh. Static markup readiness, not a WCAG conformance claim.
Method: Static markup-model scan: html lang, document <title>, a main landmark and heading order on full documents only, plus zoom-disabling viewports, untitled iframes and meta-refresh anywhere. Deterministic, per structural checkpoint.
Coverage: Population: the PARSED MARKUP documents (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx). The page-level checks — lang, title, single main landmark — fire ONCE PER FULL DOCUMENT (an <html> root) and never on a partial or component fragment, so a repo of fragments is assessed only on the per-element checks (heading order, table headers, iframe titles, meta-refresh, zoom). Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>. (×12) — REDACTED:2, SampleBrowser/SampleBrowser/testPrintPreview.html:2, firefox-ios/Client/Assets/About/Licenses.html:2, …
An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label. — REDACTED:20
The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en"). (×6) — firefox-ios/Client/Assets/CertError.html:5, firefox-ios/Client/Assets/NetError.html:5, firefox-ios/Client/Frontend/Reader/Resources/Reader.html:5, …
user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta. (×7) — firefox-ios/Client/Assets/CertError.html:8, firefox-ios/Client/Assets/NetError.html:8, firefox-ios/Client/Frontend/Reader/Resources/Reader.html:9, …
A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>. (×4) — firefox-ios/Client/Frontend/Reader/Resources/ReaderViewLoading.html:5, firefox-ios/Client/Frontend/UserContent/UserScripts/AddressFormManager/AddressFormManager.html:6, REDACTED:1, …
Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one. — REDACTED:16
What to do
Declare <html lang>, a document <title> and a <main> landmark, keep headings in order, leave zoom enabled, title iframes and drop meta-refresh.
Other · Accessibility — Whether focus outlines aren't removed without a replacement, motion respects prefers-reduced-motion, and literal CSS colour pairs meet contrast — PARTIAL: inline styles, in-repo <style> blocks, in-repo .css files, var() tokens, Tailwind neutral utilities and CSS-in-JS literals are read (hex/rgb/hsl/named), never computed/runtime/external-CDN colour. Static markup readiness, not a WCAG conformance claim.
Method: Static markup/CSS scan: inline outline:none/0, literal inline colour/background contrast against the 4.5:1 AA floor, and <style>-block animation without a prefers-reduced-motion guard. Deterministic but PARTIAL — only inline styles and in-repo CSS literals are visible.
Coverage: Population: styled elements in the PARSED MARKUP files (.html/.htm/.cshtml/.razor/.vue/.svelte/.jsx/.tsx), plus in-repo <style> blocks, in-repo .css files and CSS-in-JS literals. Colour contrast is computed from LITERAL colour pairs only (hex/rgb/hsl/named, including var() tokens and Tailwind neutral utilities) — computed, runtime-themed and external-CDN colour is never resolved, so this is a partial read of contrast by construction. Markup built in script — tagged-template (html`…`) UIs and hyperscript DOM factories — is not read at all.
`button` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — focus-ios/Blockzilla/UIComponents/ErrorPage/errorPage.html:33
`button` sets color: white on background-color: rgb(76, 158, 255) — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. (×2) — firefox-ios/Client/Assets/CertError.css:45, firefox-ios/Client/Assets/NetError.css:51
`#advancedButton` sets color: #777 on background-color: white — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them. — firefox-ios/Client/Assets/CertError.css:68
`label input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible. — firefox-ios/Client/Frontend/UserContent/UserScripts/AddressFormManager/AddressFormManager.css:56
What to do
Keep a visible focus style (don't remove the outline without a replacement), guard animation with prefers-reduced-motion, and raise low-contrast colour pairs to at least 4.5:1.
Other · Architecture — How the codebase splits by code ROLE — domain, application, infrastructure, test, generated. The significance map behind the knowledge/coupling weighting, and a DDD signal in its own right: a thin domain core under fat infrastructure is the anemic-domain smell, quantified. How each file's role is decided, because the split is only as good as that: a generated name or a build-output tree makes it Generated, a test project makes it Test, and otherwise the file's NAMESPACE and PATH words are matched against fixed vocabularies in a fixed ORDER — domain, then infrastructure, then application — so a file whose words hit two layers is counted under the earlier one. A production file matching none of them counts as application, so that share reads 'application or unclassified' rather than a measured application layer. Roles come from naming convention, never from what the code does. On this repository the split was taken from the source tree on disk rather than from a loaded .NET workspace, so a file's role is decided by its PATH segments alone — no declared namespace was available to add to the evidence — and generated output is excluded from the census entirely rather than counted as a generated share.
Method: Roslyn line-count by code ROLE: every source file classified Domain/Application/Infrastructure/Test/Generated by namespace + path convention (the shared CodeRoleClassifier), then significant lines summed per role. Deterministic; the advisory score is the business-logic (domain+application) share of production code.
Coverage: Population: ALL source files, each bucketed into ONE of five roles (Domain/Application/Infrastructure/Test/Generated) by namespace + path convention — a file whose layer isn't named in the convention falls to Application (the neutral default), and the split is line-count, not semantic depth or business value.
Other · Architecture — Whether the project-reference graph is acyclic (cycles block independent build/deploy and signal eroding boundaries).
Method: Project reference cycles via elementary-DFS over real .csproj references, using the engine shared with D5/D7; cyclic versus acyclic. Exhaustive, deterministic.
Other · Architecture — Whether dependencies point inward (Domain ← Application ← Infrastructure/Web) — the clean-architecture dependency rule, checked across the project graph.
Method: Layer violations by name-segment inference (Domain/Core to Application to Infrastructure/Web) over the project-reference graph. Exhaustive over all projects, deterministic.
Do you agree with this assessment?
AX8 · Test isolation10.0 / 10Exemplary✓ Tool-verified
Other · Architecture — Whether production projects stay free of references to test projects — tests may depend on production, never the reverse.
Method: Csproj graph: each production project checked for references to test projects (identified by test-framework presence, not name). Zero violations is clean. Deterministic.
Other · Architecture — Whether read (query) handlers stay side-effect-free — a query that writes persistent state or raises events breaks CQS and makes reads unsafe to retry, cache, or route to a read replica.
Method: Roslyn scan: CQRS handlers classified query-vs-command by interface (IQueryHandler/ICommandHandler/IRequestHandler<TQuery,TResult>) and name convention (*Query/Get*/Find* vs *Command); each query handler's body checked for persistent-state writes (SaveChanges/repository Add-Update) or event publishes by resolved invocation. Deterministic, type-level, exhaustive over the detected handlers.
Coverage: Population: CQRS handlers identified by IQueryHandler/ICommandHandler/IRequestHandler interface + *Query/Get*/Find*/*Command NAME convention; query purity then checked exhaustively within that set — a query handler using neither convention is invisible, and mutation is a resolved persistence/publish CALL, not full dataflow.
Maturity · Maturity — Whether the repository and its projects have a README, and whether it is substantive.
Method: Filesystem scan: README presence, word count, and headings for depth; git history for staleness. Exhaustive across root and project dirs, deterministic.
What to do
Explain in the README how to run the tests. Add a section called Testing to the README in the repository's top folder, saying how to run the test suite.
Maturity · Maturity — Whether the repository is organised deliberately: production code and tests are set apart in a way its ecosystem or the repository itself declares.
Method: Filesystem scan: src/test folder separation and namespace-prefix consistency (majority RootNamespace agreement). Exhaustive across projects, deterministic.
Maturity · Maturity — Whether the project's current-state documentation describes the code that exists.
Method: Every current-state document's checkable claims looked up in the tree (links, versions, and artefact counts an order of magnitude off), plus two README checks: an advertised infrastructure product with no footprint, and a module the CHANGELOG records as removed. Deterministic, no model. Advisory.
Readiness · Readiness — Whether an automated pipeline builds and tests every change.
Method: Filesystem scan: CI workflow files (.github/workflows, .gitlab-ci.yml, etc.) for build and test stages. Exhaustive, deterministic.
Do you agree with this assessment?
P10 · Library API & versioning9.9 / 10Exemplary✓ Tool-verified
Readiness · Readiness — For a library: a deliberate (small) public API surface and explicit semantic versioning so consumers can depend on it safely.
Method: Roslyn scan: public API surface area and semantic-versioning markers (SemVer attributes, changelog entries) for libraries; off .NET, a library is the ecosystem's publication act (an npm package that is not private and names an entry point, a PyPI distribution with a build system, a Rust library crate, a Maven/Gradle module that publishes, a Go module with no package main, a gemspec, a Composer library, a SwiftPM library product, a pub.dev or Hex package), its surface is the share of types the language's code model records as public (Rust, Swift, Java, Kotlin, Go, Dart; not measured where the model records no type visibility or, as in TypeScript, only module-level export), and its version is read from the manifest, a semver CHANGELOG, release tooling or semver git tags. Exhaustive, deterministic.
2 public types in `BrowserKit~WebEngine` are marked as implementation by their own namespace, folder or name: `SchemeHandler` (BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift:19, `Internal`), `WKInternalSchemeHandler` (BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift:29, `Internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift:19
4 public types in `MozillaRustComponents~FocusRustComponentsWrapper` are marked as implementation by their own namespace, folder or name: `GeckoPrefHandlerImpl` (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/nimbus.swift:617, name ends in `Impl`), `MetricsHandlerImpl` (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/nimbus.swift:899, name ends in `Impl`), `RecordedContextImpl` (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/nimbus.swift:2432, name ends in `Impl`), `BackendImpl` (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/viaduct.swift:575, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/nimbus.swift:617
7 public types in `MozillaRustComponents~MozillaRustComponentsWrapper` are marked as implementation by their own namespace, folder or name: `EncryptorDecryptorImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/db_crypto.swift:569, name ends in `Impl`), `KeyManagerImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/db_crypto.swift:804, name ends in `Impl`), `GeckoPrefHandlerImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/nimbus.swift:617, name ends in `Impl`), `MetricsHandlerImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/nimbus.swift:899, name ends in `Impl`), `RecordedContextImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/nimbus.swift:2432, name ends in `Impl`), `RemoteSettingsTelemetryImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/remote_settings.swift:1168, name ends in `Impl`), `BackendImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/viaduct.swift:575, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers. — MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/db_crypto.swift:569
What to do
Hide `BrowserKit~WebEngine` (`SchemeHandler`, `WKInternalSchemeHandler`) (Swift: leave it `internal` (the default) instead of `public`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `MozillaRustComponents~FocusRustComponentsWrapper` (`GeckoPrefHandlerImpl`, `MetricsHandlerImpl`, `RecordedContextImpl`, `BackendImpl`) (Swift: leave it `internal` (the default) instead of `public`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Hide `MozillaRustComponents~MozillaRustComponentsWrapper` (`EncryptorDecryptorImpl`, `KeyManagerImpl`, `GeckoPrefHandlerImpl`, `MetricsHandlerImpl`, `RecordedContextImpl`, `RemoteSettingsTelemetryImpl`, `BackendImpl`) (Swift: leave it `internal` (the default) instead of `public`): its own namespace, folder or name already says it is implementation, and hidden it can change without breaking a consumer.
Do you agree with this assessment?
P2 · Observability8.3 / 10Strong✓ Tool-verified
Readiness · Readiness — Whether the code is diagnosable in production — structured logging, tracing/metrics, health checks.
Only 7/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `SampleBrowser`, `SampleComponentLibraryApp`.
`focus-ios/Blockzilla/FullScreen.js` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — focus-ios/Blockzilla/FullScreen.js:18
`firefox-ios/Client/Assets/CC_Script/FormAutofill.sys.mjs` reports through `console.*` at line 197 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/FormAutofill.sys.mjs:197
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 363 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:363
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 378 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:378
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 405 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:405
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 420 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:420
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 435 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:435
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 449 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:449
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 457 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:457
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 476 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:476
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 481 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:481
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 486 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:486
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 550 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:550
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 573 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:573
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 587 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:587
`firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 612 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:612
`firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:52
`firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:53
`firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 54 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:54
`firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 59 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:59
`firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 60 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:60
`firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 62 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:62
`firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs` reports through `console.*` at line 602 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs:602
`firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:28
`firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js` reports through `console.*` at line 33 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:33
`firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js` reports through `console.*` at line 140 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:140
`firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js` reports through `console.*` at line 209 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:209
`firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js` reports through `console.*` at line 285 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:285
`firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js` reports through `console.*` at line 328 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:328
`firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js` reports through `console.*` at line 332 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:332
`firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js` reports through `console.*` at line 816 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline. — firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:816
What to do
Extend structured logging to the remaining runnable modules so everything you run is diagnosable in production.
Route service-code `console.*` output through the module's structured logger (with named fields), so delivery outcomes and failures reach the log pipeline with a level.
Readiness · Readiness — Whether SAST, secret/dependency scanning and performance benchmarking are wired in (presence, not runtime).
Method: Filesystem scan: SAST configuration, dependency-update automation, secret scanning, and a benchmark harness or benchmark step — in this repository's own ecosystem. Exhaustive, deterministic.
No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 33 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner. — .github/workflows/assign-tech-lead-review.yml:4
`REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`. — REDACTED:15
What to do
Add a SAST step to CI running what this repository's stack ships: CodeQL's Swift pack (Swift/Xcode) — or `semgrep --config=auto`, which runs on any language — so a security regression fails the build instead of landing.
Enable Dependabot/Renovate or a dependency-review gate.
Add gitleaks/trufflehog in CI to block PRs that introduce committed secrets.
Readiness · Readiness — Whether releases are automated and safely reversible (probes, rolling updates, approval gates) — from manifests/pipeline files, not the live environment.
Method: Filesystem scan: deployment manifests/IaC (K8s YAML, Helm, Terraform) for rolling updates, probes, approval gates, migration hooks. Exhaustive, deterministic.
Readiness · Readiness — Whether releases are traceable — a maintained changelog and explicit version stamping.
Method: Filesystem scan: changelog file presence and version tags in csproj or git tags. Exhaustive, deterministic.
No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
What to do
Keep a changelog (e.g. Keep-a-Changelog) recording what shipped in each release.
Readiness · Performance — Whether asynchronous code stays responsive — it avoids sync-over-async blocking (a .NET .Wait()/.GetAwaiter().GetResult(), a time.sleep or blocking HTTP call inside a Python coroutine, a *Sync call inside an async JavaScript function, block_on inside a Rust async fn, runBlocking inside a Kotlin suspend function, block() inside a Reactor publisher) that stalls a thread or event loop and risks deadlock, and, where the code is a reusable library on .NET, awaits with ConfigureAwait(false) so it never captures and stalls its caller's context.
Method: Production-source scan: sync-over-async blocking counted everywhere — .Wait()/.GetAwaiter().GetResult() in .NET; off .NET, read from each language's code model, a blocking call inside an async function (Python, TS/JS, Rust, Kotlin, Swift, Dart) or inside a Java method returning a Reactor Mono/Flux or a Scala method returning a Future or effect — and, for a .NET library with ≥5 awaits, the share of awaits using ConfigureAwait(false). Deterministic, syntax/text detection.
`query_github` is async and calls urllib.request.urlopen — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs. — REDACTED:42
`sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs. — firefox-ios/Client/VPN/VPNGuardian.swift:162
What to do
Python: await the async equivalent (asyncio.sleep, an async HTTP client such as httpx.AsyncClient or aiohttp, asyncio.create_subprocess_exec), or move the blocking call off the loop with `await asyncio.to_thread(...)`; never call asyncio.run inside a coroutine — await the coroutine.
Swift: await instead of blocking — `try await Task.sleep(for:)` for Thread.sleep/sleep, a checked continuation instead of a DispatchSemaphore or DispatchGroup wait, the async Process and URLSession APIs; never park a thread waiting on a Task — the cooperative pool cannot guarantee it progress.
Do you agree with this assessment?
R1 · Type Safety0.0 / 10Critical✓ Tool-verified
React / JS · Code Health — How much of the frontend is typed TypeScript vs untyped JavaScript.
Method: Frontend file inventory: the share of typed TypeScript vs untyped JavaScript across the source tree. Deterministic, exhaustive over frontend files.
0 typed · 94 plain JS — the untyped files are REDACTED, firefox-ios/Client/Assets/CC_Script/AddressMetaDataExtension.sys.mjs, firefox-ios/Client/Assets/CC_Script/AddressMetaDataLoader.sys.mjs, REDACTED, REDACTED, firefox-ios/Client/Assets/CC_Script/AutofillFormFactory.sys.mjs (+88 more).
What to do
Adopt TypeScript for the frontend: add a typecheck step to the build, then either type-check the existing JavaScript in place (`checkJs`/JSDoc types) or convert the highest-traffic modules first — no file is typed today, so this is an adoption, not a clean-up.
React / JS · Code Health — The share of the scored frontend lines inside a near-exact copy-pasted block of substantial extent (the D4 clone algorithm over JS/TS tokens, D-386; each line once, 10 at none and 0 at a quarter of the lines, as D4): a block is reported only where its copies still agree on most of their own identifiers and literals, or were renamed as they were pasted but kept most of their constants, and where the copies carry enough code to stand on their own or the copied extent reaches 30 lines — so a re-implementation sharing neither names nor values, and a small pasted declaration, are both found and deliberately not reported, and a clean R10 is not a claim that nothing was copied.
Method: Near-exact copy-pasted blocks of substantial extent across the frontend (the D4 clone algorithm run over JS/TS tokens). Masking finds the candidates; a block is reported when its copies still agree on most of their own identifiers and literals, or when a renamed copy still agrees on most of its constants, AND the copies carry enough code to stand on their own — or when the copied extent reaches 30 lines. So a re-implementation sharing neither names nor values, and a small pasted declaration, are deliberately not counted. Scored on the share of the scored frontend lines inside a reported copy, on the same curve as D4. Deterministic.
5 of the duplicated blocks reported below have copies in at least two of the sibling directories firefox-ios, focus-ios under the repository root. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on. — REDACTED:8
REDACTED:8 · REDACTED:29 — these 2 files are line-for-line copies of one another — 218 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done. — REDACTED:8
REDACTED:4338 · REDACTED:4408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:4338
REDACTED:2805 · REDACTED:3034 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:2805
firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/Ads.js:11 · focus-ios/Blockzilla/Ads.js:14 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/Ads.js:11
firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/FullscreenHelper.js:5 · focus-ios/Blockzilla/FullScreen.js:22 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. — firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/FullscreenHelper.js:5
firefox-ios/Client/Assets/CC_Script/FormAutofill.sys.mjs:235 · firefox-ios/Client/Assets/CC_Script/FormAutofill.sys.mjs:281 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/FormAutofill.sys.mjs:235
REDACTED:1159 · REDACTED:1280 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:1159
firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:427 · firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:160 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:427
firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:536 · firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:601 — the two spans are one implementation copied and then locally edited — 154 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:536
firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:594 · firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:64 — the two spans are one implementation copied and then locally edited — 157 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:594
REDACTED:2075 · REDACTED:2147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:2075
firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:520 · firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:564 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:520
firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:223 · firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:248 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:223
firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:738 · firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:774 · firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:898 · firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:926 · +2 more site(s) not listed — all 6 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:738
REDACTED:2724 · REDACTED:2756 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:2724
firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/__firefox__.js:8 · firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentStart/__firefox__.js:8 · firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/NightModeAtDocumentStart/__firefox__.js:8 · REDACTED:8 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete. — firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/__firefox__.js:8
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1633 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1740 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1633
firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:869 · firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:922 · firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:1002 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:869
firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:308 · firefox-ios/Client/Assets/CC_Script/HeuristicsRegExp.sys.mjs:666 — the two spans are one implementation copied and then locally edited — 95 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:308
firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:800 · REDACTED:162 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:800
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:481 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:498 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:481
firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js:147 · focus-ios/Blockzilla/Lib/TrackingProtection/Assets/preload.js:28 — the two spans are one implementation copied and then locally edited — 102 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js:147
firefox-ios/Client/Assets/CC_Script/LoginManager.shared.sys.mjs:93 · firefox-ios/Client/Assets/CC_Script/LoginManager.shared.sys.mjs:124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — firefox-ios/Client/Assets/CC_Script/LoginManager.shared.sys.mjs:93
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1672 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1749 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1672
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2620 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2683 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2620
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:239 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:378 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:239
firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/LanguageSampleExtractor.js:48 · firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/Summarizer.js:38 — the two spans are one implementation copied and then locally edited — 55 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one. — firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/LanguageSampleExtractor.js:48
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2556 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2658 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2556
REDACTED:4129 · REDACTED:4154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. — REDACTED:4129
REDACTED:3917 · REDACTED:4038 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:3917
firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:326 · firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:463 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:326
REDACTED:4455 · REDACTED:4495 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — REDACTED:4455
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:261 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:268 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:261
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:283 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:397 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:283
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:847 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:854 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:847
firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js:53 · firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/Summarizer.js:12 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases. — firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js:53
What to do
Act on each finding's own remediation rather than one rule: the move depends on what recurs. Where the copies are executable blocks, give the shared part one home and call it from each site; where they are declarations, a listing, a specialisation already delegating to its base, or one shape repeated per entity, there is no call site and the move is a shared type, a generated set or a factory — sometimes there is nothing to extract.
React / JS · Code Health — Per-function cyclomatic/cognitive complexity from the token-level function scanner (D-386) — real branching, not a regex heuristic.
Method: Per-function cyclomatic/cognitive complexity from a token-level function scanner (real branching, not a regex heuristic), computed over every frontend function. Deterministic.
_getFormFields has cyclomatic complexity 34 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:622
_canonicalizedPropertyValues has cyclomatic complexity 30 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:167
loadBergamot has cyclomatic complexity 28 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:5
_fillForm has cyclomatic complexity 27 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:321
merge has cyclomatic complexity 23 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:6101
findCreditCardSelectOption has cyclomatic complexity 22 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:1002
_parsePhoneFields has cyclomatic complexity 21 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:244
_parseStreetAddressFields has cyclomatic complexity 21 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:370
isValidSection has cyclomatic complexity 21 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs:527
(anonymous) has cyclomatic complexity 20 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1404
findAddressSelectOption has cyclomatic complexity 20 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:882
genericPointerToWireType has cyclomatic complexity 19 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1659
_parseCreditCardNameFields has cyclomatic complexity 18 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:647
adaptFieldMaxLength has cyclomatic complexity 17 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:893
parsePasswordRules has cyclomatic complexity 17 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:621
onFocusIn has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:518
create has cyclomatic complexity 16 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FieldScanner.sys.mjs:93
distance has cyclomatic complexity 16 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/fathom.mjs:770
_parseCreditCardExpiryFields has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:535
isNodeHidden has cyclomatic complexity 16 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:5840
computeFillingValue has cyclomatic complexity 15 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:775
toWireType has cyclomatic complexity 15 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2578
_getFormFields has cyclomatic complexity 15 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:126
isVisible has cyclomatic complexity 15 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/fathom.mjs:496
buildRegionMapIfAvailable has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:685
(anonymous) has cyclomatic complexity 14 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — focus-ios/Blockzilla/MetadataHelper.js:28
identifyCountryCode has cyclomatic complexity 14 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:737
inferFieldInfo has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:979
telTransformer has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:1169
_parseCustomCharacterClass has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:355
_parsePasswordRule has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:466
FormatNumber has cyclomatic complexity 13 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:145
groupFields has cyclomatic complexity 13 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs:218
fillFields has cyclomatic complexity 13 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:452
_parseAddressFields has cyclomatic complexity 13 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:484
ParseNumber has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:388
generateLabelMap has cyclomatic complexity 12 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/LabelUtils.sys.mjs:179
stringToUTF8Array has cyclomatic complexity 12 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:238
#subdivideNodeForContentTranslations has cyclomatic complexity 12 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — REDACTED:2503
(anonymous) has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes. — firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js:31
Do you agree with this assessment?
R3 · Large Files0.5 / 10Critical✓ Tool-verified
React / JS · Code Health — How many source files exceed the large-file threshold.
Method: Components/modules exceeding the large-file threshold, counted exhaustively across the frontend source tree. Deterministic.
REDACTED has 5984 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js has 3326 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1
firefox-ios/Client/Assets/CC_Script/fathom.mjs has 2513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/fathom.mjs:1
firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs has 1383 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:1
firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs has 1320 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:1
REDACTED has 1210 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs has 1141 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:1
firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs has 852 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:1
firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js has 815 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:1
firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs has 689 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs:1
firefox-ios/Client/Assets/CC_Script/HeuristicsRegExp.sys.mjs has 651 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/HeuristicsRegExp.sys.mjs:1
firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs has 641 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:1
firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs has 617 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs:1
firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs has 604 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:1
REDACTED has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
firefox-ios/Client/Assets/CC_Script/CreditCard.sys.mjs has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/CreditCard.sys.mjs:1
REDACTED has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — REDACTED:1
firefox-ios/Client/Assets/CC_Script/AutofillTelemetry.sys.mjs has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module. — firefox-ios/Client/Assets/CC_Script/AutofillTelemetry.sys.mjs:1
What to do
Split each oversized file along the responsibilities already in it, into smaller focused modules in the same package.
React / JS · Readiness — How outdated the npm dependencies are (a maturity signal). JS/npm CVEs are scored separately in D30 (JS/npm Dependency Vulnerabilities).
Method: npm dependency staleness from manifest/registry metadata (a maturity signal; JS/npm CVEs are scored separately in D30, which answers dependency vulnerabilities for every ecosystem). Deterministic.
Do you agree with this assessment?
R6 · Tooling3.4 / 10Weak✓ Tool-verified
React / JS · Readiness — Whether the project wires up test, lint and typecheck — detected from each REDACTED script's COMMAND (eslint / tsc / vitest / jest / playwright), not just its name, and corroborated against CI-workflow invocations so a tool run only in CI still counts.
Method: REDACTED scanned for test/lint/typecheck script wiring. Deterministic presence check.
test ✓ · lint ✗ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
What to do
Add eslint and type checking (adopt TypeScript, or type-check the existing JavaScript with `checkJs`) as REDACTED scripts and run them in CI.
Do you agree with this assessment?
R7 · Dead Code6.2 / 10Adequate✓ Tool-verified
React / JS · Code Health — Files unreachable from every application/tooling/test entry point, and exports nothing imports (module-graph reachability, D-386).
Method: Dead code: files unreachable from every application/tooling/test entry point plus exports nothing imports, via module-graph reachability. Deterministic, exhaustive over the import graph.
Unreachable from the 50 application, 1 tooling and 10 test entry point(s) detected in this repo. Gate removals on `npm run build` — an undetected custom entry would make these reachable.
no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make (×30) — REDACTED, REDACTED, REDACTED, …
no import path from any entry point (50 application, 1 tooling, 10 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentStart/TrackingProtectionStats.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js
no import path from any entry point (50 application, 1 tooling, 10 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderModeStyles.js
no import path from any entry point (50 application, 1 tooling, 10 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/TranslationsEntrypoint.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/LanguageSampleExtractor.js
no import path from any entry point (50 application, 1 tooling, 10 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js, firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/Summarizer.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/JSONLD.js
no import path from any entry point (50 application, 1 tooling, 10 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/NightModeAtDocumentStart/NightModeHelper.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it — firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/NightModeAtDocumentStart/DarkReader.js
What to do
Delete the dead files and unused exports — every line is maintenance cost and rebuild-estimate inflation with zero runtime value.
React / JS · Readiness — npm dependency truthfulness (D-386): unused dependencies, imports not declared anywhere, and type-/test-only packages shipped as production deps.
Method: npm dependency truthfulness: unused dependencies, imports declared nowhere, and type-/test-only packages shipped as production deps — from the manifest + import graph. Deterministic.
React / JS · Architecture — Import cycles in the module graph (D-386) — files that can only be understood and changed together.
Method: Import cycles in the module graph, detected exhaustively over JS/TS imports (the same cycle detection as the .NET coupling dimension). Deterministic.
Other · Security — Whether a hand-rolled public/private IP check can be walked past — a method that unwraps IPv4-mapped IPv6 but returns the opposite verdict for the same host written as IPv4-compatible, 6to4 or NAT64.
Method: Roslyn syntax + semantics: methods that unwrap IPv4-mapped IPv6 and hand-roll IPv4 range carve-outs, checked for whether the IPv6 branch also accounts for the IPv4-compatible, 6to4 and NAT64 embeddings. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether a value handed from a callback to the body that waits on it crosses on something built to be crossed — a `Queue<T>`/`List<T>`/`Dictionary<K,V>` written inside an event handler and read back outside it is mutated by two flows at once, and the semaphore or completion source beside it orders how MANY items exist while leaving the collection's own head, tail and backing array unprotected.
Method: Roslyn syntax: method, accessor, local-function and lambda bodies that declare BOTH a non-thread-safe generic collection (`Queue`/`Stack`/`List`/`Dictionary`/`HashSet`/`Sorted*`/`LinkedList`) and a synchronisation primitive (`SemaphoreSlim`/`TaskCompletionSource`/`ManualResetEvent(Slim)`/`AutoResetEvent`/`CountdownEvent`) as locals, then read for a `+=`-registered lambda that raises that primitive while the body outside every lambda waits on it — and, in that scope, a mutating call on the collection inside the lambda paired with a mention of it outside. Any `lock` in the scope abstains it. On a repository with no .NET source the same handoff is read in Java off the engine’s own token stream (test source sets, vendored and demonstration paths not): an `ArrayList`/`LinkedList`/`ArrayDeque`/`PriorityQueue`/`Hash*`/`LinkedHash*`/`Tree*` local and a `CountDownLatch`/`Semaphore`/`CompletableFuture` local, a lambda or anonymous class that raises the primitive and mutates the collection, and a wait outside it; any `synchronized` or `lock()` abstains the body. Because each of those primitives orders what the callback wrote before raising it, only a touch that provably overlaps the callback is convicted: one after the registration and before the next wait, or one in a loop registered-before, waiting on every pass and not declaring the collection. Deterministic, provable per finding. Advisory.
Do you agree with this assessment?
X28 · Index access outside its own emptiness guard10.0 / 10Exemplary○ Nothing flagged
Other · Code Health — Whether a condition that tests a value for emptiness indexes that same value only where the test holds — an `||` written one parenthesis too far to the left leaves an index access outside the guard beside it, so the empty case the guard exists to anticipate reaches the index and throws.
Method: Roslyn syntax only, no semantic model: the OUTERMOST `&&`/`||` of every boolean condition, read for a symbol the condition tests for emptiness (`string.IsNullOrEmpty`/`IsNullOrWhiteSpace`, a `Length`/`Count` comparison against a literal, `Any()`, a `Length`/`Count` pattern, or a comparison against `""`) and ALSO indexes. Each `symbol[...]` access is placed by a boolean-reachability walk from the access up to the outermost connective: an access is COVERED when some enclosing step has it in the right operand and the left operand, under the truth value that step forces, proves the symbol non-empty — a recursion over `&&`/`||` whose true- and false-directions are asymmetric. A finding needs BOTH an uncovered access and a covered one on the same symbol in the same condition, which is the agreeing twin that separates a misplaced parenthesis from an unrelated length test. Bare index accesses with no emptiness test in the condition are neither counted nor reported; a non-identifier receiver and a lambda nested inside the condition are outside the population. Deterministic, provable per finding. Advisory.
Other · Code Health — Whether exceptions are handled rather than silently swallowed or rethrown with lost stack traces.
Method: Roslyn syntax scan: every catch clause counted; empty catches and bare rethrows flagged. Population is all catch clauses, not estimated. Deterministic, hard fact.
`catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. (×13) — focus-ios/Blockzilla/Utilities/AuthenticationManager.swift:42, firefox-ios/Client/TabManagement/Document/TemporaryDocument.swift:284, firefox-ios/Client/Nimbus/OnboardingFeatureLayer/NimbusOnboardingFeatureLayerProtocol.swift:57, …
`catch _` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter. — focus-ios/Blockzilla/Extensions/URLExtensions.swift:84
An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it. (×25) — firefox-ios/WidgetKit/OpenTabs/SimpleTab.swift:29, firefox-ios/Storage/FileAccessor.swift:109, firefox-ios/Client/Telemetry/TelemetryWrapper.swift:87, …
`.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it. — firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs:533
Other · Code Health — Whether Ruby's type checker checks nil and is not undermined by assertions — a file Sorbet reads at `# typed: true` or above, or a Steep target `check`s under its default or strict diagnostics, is one where a method call on a `T.nilable(String)` / `String?` is an error, and each `T.must`, `#: as !nil` or `# steep:ignore NoMethod` is the author telling the checker a value cannot be nil.
Method: Roslyn compiler-options scan: NullableContextOptions per project; null-forgiving (!) suppression density per 1k syntax nodes. Deterministic, adoption plus suppression penalty.
This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
What to do
Adopt a checker and raise it file by file: with Sorbet, `srb init` (or `bundle exec tapioca init`) commits `sorbet/config`, then move each file's sigil from `# typed: false` to `# typed: true` and on to `strict` as its methods get `sig`s — `spoom bump` does the moving; with Steep, write RBS signatures and `check` the product directories in the `Steepfile` under `D::Ruby.default` or `strict`, not `lenient`. Then pay down the assertions rather than adding to them: each `T.must` is a nil the checker could not rule out — narrow it (`return unless x`, `x&.`, `if (y = x)`), make the attribute non-nilable and set it in `initialize`, or change the method so the nil cannot arrive.
Do you agree with this assessment?
WCAG coverage — what static analysis assessed
Statically assessed 10 of 55 WCAG 2.2 Level A/AA success criteria (18%; ≈20% of the 50 WCAG 2.1 AA criteria for EN 301 549). The other 45 require runtime or manual evaluation. Partial signal only (a clean result is necessary, not sufficient; static analysis fully verifies none). This is accessibility readiness, not a conformance claim — a WCAG conformance claim requires manual evaluation (WCAG-EM 1.0).
The score is the rank-weighted fold of these lenses (worst-heaviest), each including its meta-dimensions; a lens with a Critical contributor is capped at Fair (its band reads "gated by …") and is never the strongest area however high its average.
Unscored — 4 check(s) recorded observations but carry no score
These checks ran and found something, but they do not carry a score — either by design (an advisory check reports evidence rather than grading it) or because they could not be scored here. They are excluded from the score for that reason, not because there was nothing to see.
D11 Test Reliability — 6 observation(s) recorded · This repository declares 6 of its own test(s) unreliable. The built-in reliability runner does not support this repository's ecosystem (.py, .swift), so the suite was not re-run and no reliability score is given — these are the repository's own declarations, not our measurement.
D36 Supply-chain Provenance & Signing — 19 observation(s) recorded · The CI pipeline publishes no artifact — no package publish, container push or release with files to download. Supply-chain provenance, signing and an SBOM describe a PUBLISHED artifact for the people who obtain it, so there is nothing to attest here; a deployment of the service itself publishes nothing for anyone else to verify. Add them to the release pipeline when this repo starts publishing artifacts (a package, a container image, or a release with downloadable files). Build integrity and workflow-token hygiene are reported below: they describe what the CI runs and the token it runs with, neither of which is affected by whether the pipeline ships an artifact.
X10 Duplicated predicate — 40 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
X7 Silent fallback defaults — 5 observation(s) recorded · Advisory — this card reports evidence and never carries a score.
Not evidenced — 2 control(s) we could not find positive evidence for
These checks grade a working control, and the repository shows no evidence of one. That is deliberately not scored as a zero: a repository cannot show an ops runbook, a database TTL or an infrastructure-side audit log, so absence of evidence here is not evidence the control is missing. It is also not a statement that the check is irrelevant to this codebase — the thing it grades applies; we just could not see it. Excluded from the score either way.
C3 Audit Trail — Not assessed: these audit controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks audit controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
P5 DR & Backup — not evidenced — repo shows no backup/RTO/RPO controls; absence of evidence is not evidence of a working control
Not included — 61 check(s) not relevant to this codebase
These checks had nothing to measure here (no tests, no git history, the codebase is small, or the architecture style doesn't apply), so they're omitted above rather than scored low.
AC1 Text alternatives — No image/media element found in the parsed markup — AC1 not applicable here.
AC4 Keyboard semantics — No interactive element found in the parsed markup — AC4 not applicable here.
AC5 ARIA correctness — No ARIA usage found in the parsed markup — AC5 not applicable here.
AX1 Captive dependencies — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX2 Stateful singletons — No container singleton was found, so there is no shared instance for concurrent requests to race on. No function in this Python code is served by a threaded web framework (a Flask, Bottle or FastAPI route, a Django or Pyramid view), so no module is shared between request threads. No class in this Ruby code is a Rails controller, a Sinatra, Grape or Roda app, a Hanami action or a Rack app (an instance `call(env)`), so no request handler shares state between request threads. No Swift request handler (a Vapor, Hummingbird, Kitura, Swifter or Perfect route handler, as a method or a registered closure) is declared, so no state is shared between request threads. TypeScript/JavaScript runs each process's requests on one event loop, so no two requests write a shared object at the same instant (interleaving across an await is a different defect).
AX5 Architecture & structure — not assessed — architecture style/structure is computed from a project graph (projects, types, module namespaces) that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
AX6 Interface segregation — no class or module declares an abstract method
AX7 Slice cohesion — not applicable — not a vertical-slice architecture
AXB2 Runtime readiness — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
AXR1 Runtime accessibility — the dev server (`npm run dev`) kept running but served no page within 2 minutes. Likely cause (not identified): the dev server kept running but no port it opened served a page in the time allowed. Last output: "+ 2 modules / ./firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js 6.08 KiB [built] [code generated] / modules by path ./node_modules/ 473 KiB / modules by path ./node_modules/@mozilla/readability/*.js 92.2 KiB 3 modules / modules by path ./node_modules/page-metadata-parser/*.js 6 KiB 2 modules / ./node_modules/darkreader/darkreader.js 290 KiB [built] [code generated] / ./node_modules/dompurify/dist/purify.cjs.js 83.8 KiB [built] [code generated] / ./node_modules/script-loader/addScript.js 642 bytes [built] [code generated] / webpack 5.109.2 compiled successfully in 542 ms" No runtime evidence was gathered. This is a statement about this run, not a statement about your application: nothing here says the surface is inaccessible, only that it was never rendered.
C1 Data Protection — Not assessed: these personal data controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks personal data controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C2 Access Controls — Not assessed: these authorization controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks authorization controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
C4 Data Retention — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data whose lifetime a retention limit would bound.
C5 Data-Subject Rights — No personal data detected in a persisted data model — no PII-named property (email, firstName, dateOfBirth, phoneNumber, …) or stored credential on a SwiftData @Model, a Core Data, Realm, GRDB or Fluent type, a GRDB or SQLite.swift column, or in a SQL CREATE TABLE or ALTER TABLE — and no database or data-store client (CoreData, SwiftData, GRDB, RealmSwift, SQLite, Firebase, …) imported either, so this repository keeps no personal data for a data subject to erase, export or consent over.
D18 Solution Shape — D18 scores the shape of a .NET solution; this repository has no .NET solution or project files, so the dimension does not apply.
D22 Internal API Consistency — API consistency is measured on C# only; the exposed Swift surface was not measured.
D23 Boundary Type-Coupling — No bounded-context organisation was detected either — neither a context-shaped layout, nor 2+ sibling source directories each declaring an aggregate root, nor 2+ sibling projects each declaring an entity of their own or taking another project's integration events. Declaring this codebase's bounded contexts (≥2) would let cross-boundary type coupling be assessed. Declare them in `.codehealth/config.yaml` at the repository root (create it if absent), mapping each context name to the module-path or namespace prefixes that belong to it — e.g. `architecture:` → `contexts:` → `Billing: ["src/billing", "Acme.Billing"]`, `Catalog: ["src/catalog", "Acme.Catalog"]`.
D25 ADR Conformance — None of 11 binding record(s) states a rule in checkable form (a backticked element with a prohibition, or an `adr-rules` block), so conformance cannot be read from the code. Write the rule as an `adr-rules` block (`forbid:` a symbol, a package or a dependency) to make it checkable.
D28 Secrets (history) — gitleaks killed before it finished — this repository's git history not scanned
D40 Network Egress Confinement — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
D41 Kernel & Syscall Confinement — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
D42 Runtime Threat Enforcement — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
D8 Code Coverage — Coverage not measured — Swift suite
DM1 Domain Modelling — not scored — this repository shows only 1 of the 3 signals this lens looks for (4 value object(s))
ED2 Event/command shape — not scored — deciding whether a command has more than one competing handler requires resolving the call graph, and this analysis resolves a call's owner only where the receiver's type is written down in the source. Reported as guidance rather than measured
ED5 Idempotency — no mutating command handlers or message consumers detected — idempotency check not applicable
ES1 Event Sourcing — not scored — this repository shows none of the 3 signals this lens looks for
GD1 Unfinished & placeholder code — no source files were read — this check reads C#, F#, JavaScript/TypeScript, Dart, Ruby and Scala, and none was read for this repository's product. That is a limit of the analyzer, not a finding about your code.
IC1 Incompleteness & stubs — not analysed — these correctness checks read a source model that was not loaded for this repository, because the repository is written in a language this check does not yet model, or because its projects failed to load. This is a gap in the analyzer, not a finding about this repository
P12 CI test-gate honesty — Reported, not scored — and nothing was matched here. The coverage check applies to any stack, and the automatic-re-run check to any GitHub-Actions workflow, but the checks for excluded tests, skipped tests and sleep-based synchronisation currently recognise only some ecosystems' test-runner idioms, so on a repository built with another stack the zeros below mean 'not checked', not 'clean'.
P7 Outbound HTTP resilience — not applicable — no HTTP server, API framework or worker entry point was found in the JavaScript/TypeScript, Python, Ruby, Swift source, so there is no service whose uptime a failing dependency could take down
P8 Schema migrations — no ORM, schema-migration tool or schema auto-create was found in this repository's dependency manifests or source, so there is no database schema for this check to judge
P9 Domain vs controller coverage — coverage not measured: this check compares the coverage of the analyzer's own test run across the domain and web layers, and that run measured none here — Test coverage (D8) says why
PF1 Benchmark discipline — Not applicable: no benchmark suite was found. This check searched for `Benchmark("…")` in a file importing package-benchmark, or package-benchmark in Package.swift, and for a `*benchmark*` script that this repository's CI runs. Benchmarks are credited as a bonus, so their absence is neither scored nor deducted.
PF2 Allocation hygiene — Not scored: this check counted allocation-aware idioms (Span, pools, stackalloc) per line, which describes what kind of code a repository is rather than whether it has an allocation problem, so it was withdrawn. Nothing here is a finding about your code.
R11 Import Boundaries — No recognizable feature-sliced/layered src layout — boundary rules not applicable.
R4 Test Coverage — 10 test file(s) reach none of 83 production file(s) via imports — exercised outside the JS import graph (integration/bundled), not import-reachable
S1 Web-Security Posture — Not assessed: these web-security controls are read from a source model (declarative annotations, request middleware, entity/column names, guard methods) that was not loaded for this repository — because the repository is written in a language this check does not yet model, or because its projects failed to load. Absence of an idiom this check recognises is NOT evidence that this repository lacks web-security controls: it may implement them entirely in its own ecosystem. This is a gap in the analyzer's language coverage, not a finding about this repository.
SC1 Supply-chain hygiene — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X1 Async correctness — X1 reached only 14% of this repository's production lines — swift (241,980 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X12 Unreachable branch — X12 reached only 14% of this repository's production lines — swift (241,980 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X13 Undrained process stream — X13 reached only 14% of this repository's production lines — swift (241,980 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X15 Unvalidated length from an untrusted reader — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X16 Unfloored truncation loop — X16 reached only 12% of this repository's production lines — swift (241,980 lines), python (4,333 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X17 Uncapped recursion over a caller-supplied document — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X18 Disposal-pattern correctness — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X19 Unrestored process-global state — X19 reached only 14% of this repository's production lines — swift (241,980 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X2 Cancellation propagation — X2 reached only 14% of this repository's production lines — swift (241,980 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X20 Mistyped argument guard — This check asks whether an argument guard reports an EMPTY value as a NULL one, which needs a language that throws a null-specific argument exception — .NET's ArgumentNullException, the JVM's NullPointerException, Dart's ArgumentError.notNull. This repository contains none of those languages: the ones it is written in have a single exception for a bad argument, so there is no pair of exceptions to confuse and nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X21 Side-effecting pattern guard — X21 reached only 14% of this repository's production lines — swift (241,980 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X22 Contradicted release guard — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X23 Unguarded diagnostic materialisation — X23 reached only 14% of this repository's production lines — swift (241,980 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X24 Document value interpolated into markup unescaped — X24 reached only 14% of this repository's production lines — swift (241,980 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X25 Inert configuration knob — not applicable — the code was read and holds no site of this kind, so there is nothing for this check to judge
X27 Collection changed while being enumerated — X27 reached only 2% of this repository's production lines — swift (241,980 lines), javascript (33,525 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X29 Per-element action decided by a fixed element — X29 reached only 12% of this repository's production lines — swift (241,980 lines), python (4,333 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X30 Support guard that admits what it rejects — X30 reached only 14% of this repository's production lines — swift (241,980 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X32 Type resolved by simple name across every loaded assembly — This check is about how a .NET program searches the assemblies loaded into its process for a type, and this repository contains no .NET source, so there is nothing here for it to assess. Not a gap in the analyzer and not a finding about your code.
X4 Structured logging — X4 reached only 14% of this repository's production lines — swift (241,980 lines), objectivec (110 lines), c (84 lines) was left unread. Not scored: a score over a minority of the product would be published as the whole of it.
X6 Hand-rolled structured-format parsing — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
X9 Subsumed condition operand — Advisory — this card reports evidence and never carries a score, so there is nothing missing here.
Appendix A — Findings (grouped)
The findings behind the scores, grouped by severity, then by dimension and kind. The high-severity issues are enumerated in full below; items per group are capped at 25 with any overflow stated explicitly per group, never silently truncated. The complete machine-readable list of every finding (all severities) is the companion findings.md in this report's bundle.
Boundary-crossing change coupling: WebCompatReportSheetPreview.swift ↔ WebCompatReportViewController.swift BrowserKit/Sources/WebCompatReporterKit/Preview/WebCompatReportSheetPreview.swift:1— `BrowserKit/Sources/WebCompatReporterKit/Preview/WebCompatReportSheetPreview.swift` (context BrowserKit) and `firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift` (context firefox-ios) sit in DIFFERENT parts of the tree yet change together 100% of the time (11 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `3a8e546b` Bugfix FXIOS-16487 [WebCompat] Show an error for an invalid URL (#35262); `7d79fd43` Bugfix FXIOS-16484 [WebCompat] Use a checkbox for the Additional Info…; `2022c581` Bugfix FXIOS-16486 [WebCompat] Fix the URL field label and alignment … — run `git show` on any of them.
Boundary-crossing change coupling: WKEngineSession.swift ↔ BrowserViewController.swift BrowserKit/Sources/WebEngine/WKWebview/WKEngineSession.swift:1— `BrowserKit/Sources/WebEngine/WKWebview/WKEngineSession.swift` (context BrowserKit) and `SampleBrowser/SampleBrowser/UI/Browser/BrowserViewController.swift` (context SampleBrowser) sit in DIFFERENT parts of the tree yet change together 89% of the time (16 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `dff3c0e0` FXIOS-8247 [WebEngine] Handle media capture in WebEngine (#24925); `651a6f6f` Add FXIOS-11323 #24641 [WebEngine] Adapt find in page to newest API (…; `9edd3eb8` Refactor FXIOS-11184 [WebEngine] Adjusting Observer functionalities i… — run `git show` on any of them.
Boundary-crossing change coupling: AddressToolbarDelegate.swift ↔ BrowserViewController.swift BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarDelegate.swift:1— `BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarDelegate.swift` (context BrowserKit) and `firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift` (context firefox-ios) sit in DIFFERENT parts of the tree yet change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e7b73956` Bugfix FXIOS-17170 [Google Lens] Hide google lens tooltip once addres…; `e7ae7faf` Add FXIOS-10191 [Unified Search] Bubble up search engine tap event to…; `8adf1cee` Refactor FXIOS-10202 Implement UIDragInteractionDelegate for location… — run `git show` on any of them.
Boundary-crossing change coupling: ToolbarElement.swift ↔ ToolbarActionConfiguration.swift BrowserKit/Sources/ToolbarKit/ToolbarElement.swift:1— `BrowserKit/Sources/ToolbarKit/ToolbarElement.swift` (context BrowserKit) and `firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarActionConfiguration.swift` (context firefox-ios) sit in DIFFERENT parts of the tree yet change together 67% of the time (16 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 16 shared commits counted here, the most recent 3 are `3dd5edcd` Add FXIOS-16060 [Google Lens] Address toolbar entry point context men…; `fb165852` Bugfix FXIOS-15391 [Translations][Accessibility][iPad] PB icon is sel…; `9ea5f9c1` Add [Summarizer] FXIOS-15042 Reader mode with summarizer badge to Add… — run `git show` on any of them.
Boundary-crossing change coupling: LocationViewState.swift ↔ ToolbarAction.swift BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationViewState.swift:1— `BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationViewState.swift` (context BrowserKit) and `firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarAction.swift` (context firefox-ios) sit in DIFFERENT parts of the tree yet change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `3d1cb035` Add FXIOS-16058 [Google Lens] Address toolbar entry point (#34328); `df5de067` Bugfix FXIOS-15043 ⁃ Missing accessibility identifiers for lockIcon s…; `1ee8b920` Bugfix FXIOS-10491 - [Unified Search] The search engine selection bot… — run `git show` on any of them.
Boundary-crossing change coupling: LocationViewState.swift ↔ BrowserViewController.swift BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationViewState.swift:1— `BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationViewState.swift` (context BrowserKit) and `firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift` (context firefox-ios) sit in DIFFERENT parts of the tree yet change together 60% of the time (9 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `df5de067` Bugfix FXIOS-15043 ⁃ Missing accessibility identifiers for lockIcon s…; `ee0968cb` Refactor FXIOS-10471 The insecure lock icon should have a colored sla…; `82163a79` Add FXIOS-10270 - Add visual indication of strict mode for lock icon … — run `git show` on any of them.
Boundary-crossing change coupling: LocationView.swift ↔ RootViewControllerModel.swift BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationView.swift:1— `BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationView.swift` (context BrowserKit) and `SampleBrowser/SampleBrowser/Model/RootViewControllerModel.swift` (context SampleBrowser) sit in DIFFERENT parts of the tree yet change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `a5580832` Add FXIOS-9189 ⁃ Display url in address toolbar in Client (#20556) (at that commit the file was still `BrowserKit/Sources/ToolbarKit/LocationView/LocationView.swift`); `b9a6ba64` Add FXIOS-9152 Display search provider icon in Client (#20487) (at that commit the file was still `BrowserKit/Sources/ToolbarKit/LocationView/LocationView.swift`); `0aebe360` Add FXIOS-8946 - Show lock icon when url is displayed (#20265) (at that commit the file was still `BrowserKit/Sources/ToolbarKit/LocationView.swift`) — run `git show` on any of them.
Boundary-crossing change coupling: ToolbarButton.swift ↔ ToolbarActionConfiguration.swift BrowserKit/Sources/ToolbarKit/ToolbarButton.swift:1— `BrowserKit/Sources/ToolbarKit/ToolbarButton.swift` (context BrowserKit) and `firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarActionConfiguration.swift` (context firefox-ios) sit in DIFFERENT parts of the tree yet change together 54% of the time (13 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `3dd5edcd` Add FXIOS-16060 [Google Lens] Address toolbar entry point context men…; `fb165852` Bugfix FXIOS-15391 [Translations][Accessibility][iPad] PB icon is sel…; `9ea5f9c1` Add [Summarizer] FXIOS-15042 Reader mode with summarizer badge to Add… — run `git show` on any of them.
Boundary-crossing change coupling: WebCompatReportViewModel.swift ↔ WebCompatReporterState.swift BrowserKit/Sources/WebCompatReporterKit/WebCompatReportViewModel.swift:1— `BrowserKit/Sources/WebCompatReporterKit/WebCompatReportViewModel.swift` (context BrowserKit) and `firefox-ios/Client/Frontend/WebCompatReporter/Redux/WebCompatReporterState.swift` (context firefox-ios) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `2c92654e` Add FXIOS-16188 [WebCompat] VoiceOver fixes for the report sheet (#35…; `3a8e546b` Bugfix FXIOS-16487 [WebCompat] Show an error for an invalid URL (#35262); `7d79fd43` Bugfix FXIOS-16484 [WebCompat] Use a checkbox for the Additional Info… — run `git show` on any of them.
Boundary-crossing change coupling: WebCompatReportSheetViewController.swift ↔ WebCompatReporterState.swift BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:1— `BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift` (context BrowserKit) and `firefox-ios/Client/Frontend/WebCompatReporter/Redux/WebCompatReporterState.swift` (context firefox-ios) sit in DIFFERENT parts of the tree yet change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets) — the bounded-context boundary may be in the wrong place, or one context is leaking into the other. This is the behavioural boundary violation a static scan can't see. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `2c92654e` Add FXIOS-16188 [WebCompat] VoiceOver fixes for the report sheet (#35…; `3a8e546b` Bugfix FXIOS-16487 [WebCompat] Show an error for an invalid URL (#35262); `7d79fd43` Bugfix FXIOS-16484 [WebCompat] Use a checkbox for the Additional Info… — run `git show` on any of them.
Viewport restricts zoom firefox-ios/Client/Assets/CertError.html:8— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom firefox-ios/Client/Assets/NetError.html:8— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom firefox-ios/Client/Frontend/Reader/Resources/Reader.html:9— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom firefox-ios/Client/Frontend/Reader/Resources/ReaderViewLoading.html:7— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom firefox-ios/Client/Frontend/UserContent/UserScripts/AddressFormManager/AddressFormManager.html:9— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom firefox-ios/Client/Frontend/UserContent/UserScripts/TranslationsEngine/TranslationsEngine.html:8— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
Viewport restricts zoom focus-ios/Blockzilla/UIComponents/ErrorPage/errorPage.html:8— user-scalable=no/0 or a maximum-scale below 2 stops low-vision users zooming to 200%. Remove the zoom restriction from the viewport meta.
<html> without a lang firefox-ios/Client/Assets/CertError.html:5— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang firefox-ios/Client/Assets/NetError.html:5— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang firefox-ios/Client/Frontend/Reader/Resources/Reader.html:5— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang firefox-ios/Client/Frontend/Reader/Resources/ReaderViewLoading.html:5— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang REDACTED:1— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
<html> without a lang focus-ios/Blockzilla/UIComponents/ErrorPage/errorPage.html:6— The page declares no language, so assistive tech can't pick the right pronunciation. Add lang (e.g. lang="en").
D11 · Test Reliability· Test declared unreliable · ×6
Test declared unreliable: testDontAllowNotifications firefox-ios/firefox-ios-tests/Tests/XCUITests/EngagementNotificationTests.swift:33— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "setUp() fails to remove app intermittently". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: testAllowNotifications firefox-ios/firefox-ios-tests/Tests/XCUITests/EngagementNotificationTests.swift:59— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "setUp() fails to remove app intermittently". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: testLoginFreshInstallMessage firefox-ios/firefox-ios-tests/Tests/XCUITests/LoginsTests.swift:422— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "setUp() fails to remove app intermittently". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: testLoginFreshInstallMessage firefox-ios/firefox-ios-tests/Tests/XCUITests/LoginsTests.swift:425— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "setUp() fails to remove app intermittently". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: testOpenTabsInSearchSuggestions firefox-ios/firefox-ios-tests/Tests/XCUITests/SearchTest.swift:363— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Test fails intermittently for iOS 15". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
Test declared unreliable: testClipboard focus-ios/focus-ios-tests/XCUITest/CopyPasteTest.swift:63— This test is disabled or skipped with a reason naming unreliability — the repository's own words: "Intermittent failures on iOS 15 and 16". A test that is skipped for flakiness is neither passing nor protecting the code it covers; either stabilise it or delete it, but do not leave it disabled indefinitely. (Found by reading the repository's own test source — the suite itself was not re-run, since the reliability runner does not support this ecosystem.)
AC3 · Page structure· Document without a <title> · ×4
Document without a <title> firefox-ios/Client/Frontend/Reader/Resources/ReaderViewLoading.html:5— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> firefox-ios/Client/Frontend/UserContent/UserScripts/AddressFormManager/AddressFormManager.html:6— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> REDACTED:1— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
Document without a <title> focus-ios/Blockzilla/UIComponents/ErrorPage/errorPage.html:6— A page with no <title> gives no name in the tab, history or screen-reader page list. Add a descriptive <title> in <head>.
AC3 · Page structure· <iframe> without a title · ×1
<iframe> without a title REDACTED:20— An iframe with no title (or an empty one) is announced only as "frame". Add a non-empty title describing its content, or an aria-label.
Assertions commented out: testFetchMetadataGivenDidFinishNavigationThenFetchMetadata BrowserKit/Tests/WebEngineTests/WKEngineSessionTests.swift:496— The test body contains commented-out assertion calls and no live one — it runs, verifies nothing, and still passes. Restore the assertions or delete the test; a green test that checks nothing is worse than an absent one.
Orphaned knowledge firefox-ios/Client/Frontend/NativeErrorPage/NativeErrorBadCertContentView.swift:1— No living knowledge remains for this large file — its last meaningful change has decayed away; if it breaks, no one currently understands it. Schedule a read-through / add characterisation tests before it bites.
TodoComment REDACTED:24— # TODO: Download list from Android repo once the mobile list is in the tree. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment focus-ios/Deferred/Deferred.swift:7— // TODO: Replace this with a class var — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment focus-ios/Blockzilla/BrowserViewController.swift:198— // TODO: [FXIOS-8616] Portions of this configuration will eventually be shared also by WebEngine.
TodoComment focus-ios/Blockzilla/WebEngineRefactorFlagManager.swift:11— /// TODO [FXIOS-8655]: currently this is hardcoded; eventually this will be updated to a Nimbus feature flag.
TodoComment focus-ios/Blockzilla/Utilities/AuthenticationManager.swift:33— // TODO: Check what is the best name for cancellation — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment focus-ios/Blockzilla/Utilities/InternalURL.swift:32— // TODO: (reader-mode-custom-scheme) remove isWebServerUrl when updating code. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment focus-ios/Blockzilla/Tracking Protection/TrackingProtectionViewController.swift:359— // TODO: Make sure to reset the toggle — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/BaseTestCase.swift:478— // TODO: Fine better way to update screen graph when necessary — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/LegacyOnboardingTests.swift:83— // TODO: This test needs to be fully migrated to the TAE pattern. — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/LegacyOnboardingTests.swift:216— // TODO: Migrate to TAE — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/LegacyOnboardingTests.swift:258— // TODO: Migrate to TAE — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/ModernKitOnboardingTests.swift:221— // TODO: Migrate to TAE — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/ModernKitOnboardingTests.swift:260— // TODO: Migrate to TAE — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/PageScreens/OnboardingScreen.swift:230— // TODO: Migrate to TAE — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/ModernKitOnboardingTests.swift:62— // TODO: Pre-accept ToS via launch argument instead of accepting inline — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/TodayWidgetTests.swift:14— // TODO FXIOS-12604 These global properties are not concurrency safe
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/registerTabMenuNavigation.swift:37— // Save As PDF (TODO) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/XCUITests/registerTabMenuNavigation.swift:84— // Signed in (TODO) — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/UITests/MenuTests.swift:53— // TODO: add test to open settings from home panels — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/UITests/MenuTests.swift:54— // TODO: add test to open settings from tab tray — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/UITests/MenuTests.swift:69— // TODO: add test to open new tab from home panels — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/UITests/MenuTests.swift:70— // TODO: add test to open new tab from tab tray — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/UITests/MenuTests.swift:92— // TODO: add test to open new private tab from home panels — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/UITests/MenuTests.swift:93— // TODO: add test to open private tab from tab tray — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
TodoComment firefox-ios/firefox-ios-tests/Tests/UITests/MenuTests.swift:107— // TODO: add test to open top sites from tab tray — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
No assertions: test_sendAttestation_succeeds_on200 BrowserKit/Tests/MLPAKitTests/MLPAAppAttestServerTests.swift:55— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testCloseBannerCallback BrowserKit/Tests/MenuKitTests/MenuMainViewTests.swift:59— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testBannerButtonCallbackCalled BrowserKit/Tests/MenuKitTests/MenuMainViewTests.swift:89— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testAnnounceAccessibility_whenOptionalRowIsNotVisible BrowserKit/Tests/MenuKitTests/MenuMainViewTests.swift:103— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testTapHandlerCallback BrowserKit/Tests/MenuKitTests/MenuSiteBadgeTests.swift:22— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test_fetchProxyPass_withTokenMissingSegments_throwsInvalidToken BrowserKit/Tests/VPNKitTests/VPNProxyTokenServiceTests.swift:112— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test_fetchProxyPass_withPayloadMissingExp_throwsInvalidToken BrowserKit/Tests/VPNKitTests/VPNProxyTokenServiceTests.swift:116— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: test_fetchProxyPass_withPayloadNotBase64_throwsInvalidToken BrowserKit/Tests/VPNKitTests/VPNProxyTokenServiceTests.swift:120— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testNoLeaks BrowserKit/Tests/WebEngineTests/WKEngineWebViewTests.swift:28— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEventLastSeenRegression MozillaRustComponents/Tests/MozillaRustComponentsTests/EventStoreTests.swift:81— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testGetTree MozillaRustComponents/Tests/MozillaRustComponentsTests/PlacesTests.swift:191— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testGetBookmark MozillaRustComponents/Tests/MozillaRustComponentsTests/PlacesTests.swift:245— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testAddCustomDomain focus-ios/focus-ios-tests/ClientTests/DomainCompletionTests.swift:21— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testAddCustomDomainWithHttp focus-ios/focus-ios-tests/ClientTests/DomainCompletionTests.swift:25— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testAddCustomDomainWithHttps focus-ios/focus-ios-tests/ClientTests/DomainCompletionTests.swift:29— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testAddCustomDomainWithWWW focus-ios/focus-ios-tests/ClientTests/DomainCompletionTests.swift:33— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testGenerateBackgroundColor_lastPaletteColorIsReachable BrowserKit/Tests/SiteImageViewTests/ImageProcessing/LetterImageGeneratorTests.swift:107— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testConcurrentUpon firefox-ios/ThirdParty/Deferred/DeferredTests/DeferredTests.swift:140— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testMultipleConcurrentReaders firefox-ios/ThirdParty/Deferred/DeferredTests/ReadWriteLockTests.swift:67— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testCompileListsNotInStore_callsCompletionHandlerSuccessfully firefox-ios/firefox-ios-tests/Tests/ClientTests/ContentBlockerTests.swift:42— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testResponseForErrorWebPage_withCertificateErrorWithoutCertErrorQuery_usesFallbackAndDoesNotCrash firefox-ios/firefox-ios-tests/Tests/ClientTests/ErrorPageHandlerTests.swift:33— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testResponseForErrorWebPage_withCertErrorQuery_usesProvidedValue firefox-ios/firefox-ios-tests/Tests/ClientTests/ErrorPageHandlerTests.swift:42— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testResponseForErrorWebPage_withBadDateErrorWithoutCertErrorQuery_usesExpiredFallback firefox-ios/firefox-ios-tests/Tests/ClientTests/ErrorPageHandlerTests.swift:51— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testEnqueuingActionDuringProcessingWhoseDependenciesAreSatisfiedWillBeRunCorrectly firefox-ios/firefox-ios-tests/Tests/ClientTests/EventQueueTests.swift:303— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
No assertions: testFirefoxAccountSignInViewController_simpleCreation_hasNoLeaks firefox-ios/firefox-ios-tests/Tests/ClientTests/FirefoxAccountSignInViewControllerTests.swift:27— This method's body runs code, and no assertion call was recognised in it. Recognised by name: Assert*, *Should*/ShouldBe*, Verify, Expect, Throws, Record, Received/DidNotReceive, MustHaveHappened/MustNotHaveHappened, EnsureSuccessStatusCode and *AndEnsure*, in the test body and in the helpers it calls in the test and test-support code (a helper there that throws when its check fails counts as an assertion) — so verification routed through a callback object whose members hold the assertions, or through a harness in production code that fails by throwing, is not visible to this check and is not counted here. Read it as 'no assertion this check knows how to see', and if that is right, add one.
Low cohesion: BrowserViewController (LCOM4 87) focus-ios/Blockzilla/BrowserViewController.swift:16— BrowserViewController's methods fall into 87 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 87 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NilVariables (LCOM4 23) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:417— NilVariables's methods fall into 23 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 23 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NilVariables (LCOM4 23) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift:417— NilVariables's methods fall into 23 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 23 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: View (LCOM4 21) firefox-ios/WidgetKit/UIView+extension.swift:33— View's methods fall into 21 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 21 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: URL (LCOM4 16) focus-ios/Widgets/Widgets.swift:105— URL's methods fall into 16 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 16 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: String (LCOM4 14) Dangerfile.swift:854— String's methods fall into 14 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 14 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AppDelegate (LCOM4 13) SampleBrowser/SampleBrowser/AppDelegate.swift:9— AppDelegate's methods fall into 13 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 13 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AutocompleteSettingViewController (LCOM4 12) focus-ios/Blockzilla/Settings/Controller/AutocompleteSettingViewController.swift:7— AutocompleteSettingViewController's methods fall into 12 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 12 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: UIView (LCOM4 11) SampleBrowser/SampleBrowser/Extensions/UIView+Extension.swift:7— UIView's methods fall into 11 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 11 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: NimbusDisabled (LCOM4 10) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Nimbus.swift:438— NimbusDisabled's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Tab (LCOM4 10) firefox-ios/Client/TabManagement/Tab.swift:82— Tab's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TabWebView (LCOM4 10) firefox-ios/Client/TabManagement/TabWebView.swift:23— TabWebView's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: BrowserViewController (LCOM4 10) SampleBrowser/SampleBrowser/UI/Browser/BrowserViewController.swift:17— BrowserViewController's methods fall into 10 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 10 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Array (LCOM4 9) BrowserKit/Sources/Shared/DeferredUtils.swift:31— Array's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AccessoryViewProvider (LCOM4 9) firefox-ios/Client/AccessoryViewProvider.swift:13— AccessoryViewProvider's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SiriFavoriteViewController (LCOM4 9) focus-ios/Blockzilla/Siri/SiriFavoriteViewController.swift:9— SiriFavoriteViewController's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: UIViewController (LCOM4 9) SampleBrowser/SampleBrowser/Extensions/UIViewController+Extension.swift:7— UIViewController's methods fall into 9 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 9 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Dictionary (LCOM4 8) BrowserKit/Sources/Common/Extensions/DictionaryExtension.swift:7— Dictionary's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: TopTabsLayoutDelegate (LCOM4 8) firefox-ios/Client/Frontend/Browser/TopTabsLayout.swift:12— TopTabsLayoutDelegate's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: SearchSettingsTableViewController (LCOM4 8) firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:18— SearchSettingsTableViewController's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: AppSettingsTableViewController (LCOM4 8) firefox-ios/Client/Frontend/Settings/Main/AppSettingsTableViewController.swift:60— AppSettingsTableViewController's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: RemoteTabsViewController (LCOM4 8) firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsViewController.swift:18— RemoteTabsViewController's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: Date (LCOM4 8) firefox-ios/Shared/Date+relativeTimeString.swift:7— Date's methods fall into 8 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 8 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: WKEngine (LCOM4 7) BrowserKit/Sources/WebEngine/WKWebview/WKEngine.swift:9— WKEngine's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
Low cohesion: PhotonActionSheet (LCOM4 7) focus-ios/Blockzilla/Menu/Old/PhotonActionSheet.swift:52— PhotonActionSheet's methods fall into 7 groups that share no field and call none of each other, against a bar of more than 3 for this run (LCOM4, configurable — your repository's bar is the one quoted here). Each group is a set of methods reachable from one another through shared fields or direct calls, so 7 groups means the type has that many internally-connected clusters with nothing tying them together. Types whose shape makes a high count expected — and which would otherwise dominate this list — are excluded before this row is raised, so this is a genuine split candidate rather than a metric reading. It is still a shape, not a defect: confirm the groups match responsibilities you can name before splitting.
FixmeComment firefox-ios/firefox-ios-tests/Tests/StorageTests/RustLoginsTests.swift:11— // FIXME: FXIOS-14312 Class is not thread safe
FixmeComment firefox-ios/Storage/MockRustKeychain.swift:8— // FIXME: FXIOS-13988 Make truly thread safe
FixmeComment firefox-ios/Extensions/NotificationService/NotificationService.swift:11— // FIXME: FXIOS-14295 Make NotificationService thread safe
FixmeComment firefox-ios/Extensions/NotificationService/NotificationService.swift:30— // FIXME: FXIOS-14273 Dictionaries are non-Sendable
FixmeComment firefox-ios/Client/Telemetry/TelemetryWrapper.swift:41— // FIXME: FXIOS-13987 Make truly thread safe
FixmeComment firefox-ios/Client/TabManagement/TabManagerImplementation.swift:889— // FIXME FXIOS-10059 TabManagerImplementation's preserveTabs is called with a nil selectedTab
FixmeComment firefox-ios/Client/TabManagement/TabManagerImplementation.swift:1542— // FIXME possibly also related FXIOS-10059 TabManagerImplementation's preserveTabs is called with a nil selectedTab
FixmeComment firefox-ios/Client/Frontend/HostingTableViewCell.swift:34— // FIXME: FXIOS-14153 This doesn't seem like it should be necessary, investigate later
FixmeComment firefox-ios/Client/Frontend/HostingTableViewSectionHeader.swift:35— // FIXME: FXIOS-14153 This doesn't seem like it should be necessary, investigate later
FixmeComment firefox-ios/Client/Frontend/PasswordManagement/BreachAlertsManager.swift:27— /// FIXME: FXIOS-14141 class is not Sendable / thread safe
FixmeComment firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:12— // FIXME: FXIOS-13958 @objcMembers is unsafe with main actor isolation
FixmeComment firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:184— // FIXME: FXIOS-12996 Use Themeable instead of custom theme setting
FixmeComment firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksPanelViewModel.swift:120— // FIXME: FXIOS-15309 This can be improved.
FixmeComment firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:10— // FIXME: FXIOS-14160 Make EditFolderViewModel actually Sendable
FixmeComment firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewModel.swift:10— // FIXME: FXIOS-14160 Make EditFolderViewModel actually Sendable
FixmeComment firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewModel.swift:22— // FIXME: FXIOS-14161 Make EditBookmarkViewModel actually Sendable
FixmeComment firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewModel.swift:18— // FIXME: FXIOS-16473 Make GroupedEditBookmarkViewModel actually Sendable
FixmeComment firefox-ios/Client/Frontend/Home/Homepage/TopSites/DataManagement/TopSiteHistoryManager.swift:16— // FIXME: FXIOS-14053 Can't be `final` and `Sendable` unless tests are rewritten for `TopSiteHistoryManagerStub`
FixmeComment firefox-ios/Client/Frontend/Browser/SearchLoader.swift:17— /// FIXME: FXIOS-14129 SearchLoader is not thread safe
FixmeComment firefox-ios/Client/Frontend/Browser/SearchEngines/SearchEnginesManager.swift:51— /// [FIXME FXIOS-10187 this will change soon ->] Search suggestions should always be sourced from the default search engine
FixmeComment firefox-ios/Client/Frontend/Browser/DownloadHelper/Download.swift:100— // FIXME: FXIOS-14051 Class is not thread safe and Sendable
FixmeComment firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:1035— // FIXME(FXIOS-11543): Before FXIOS-11256 all calendar type requests were forwarded to SFSafariViewController.
FixmeComment firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSettingsViewModel.swift:21— // FIXME: FXIOS-14006 Class is not thread safe
FixmeComment firefox-ios/Client/Coordinators/SettingsCoordinator.swift:82— // FIXME: FXIOS-15967 We should pop to the root of the settings screen before pushing new screens from deeplinks,
TooManyMethods: BrowserViewController focus-ios/Blockzilla/BrowserViewController.swift:16— TooManyMethods — 380 methods, declared across 11 files: Blockzilla/BrowserViewController.swift (142), Extensions/BrowserViewController+WebViewDelegates.swift (70), Views/BrowserViewController.swift (62), Extensions/BrowserViewController+KeyCommands.swift (38), +7 more file(s). The bar is 30 methods; this is 350 over it, 12.67× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BrowserViewController firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:29— TooManyMethods — 209 methods. The bar is 30 methods; this is 179 over it, 6.97× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BrowserCoordinator firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:23— TooManyMethods — 120 methods. The bar is 30 methods; this is 90 over it, 4.00× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: HomepageViewController firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:11— TooManyMethods — 94 methods. The bar is 30 methods; this is 64 over it, 3.13× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TabTrayViewController firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:27— TooManyMethods — 81 methods, declared across 2 files: Views/TabTrayViewController.swift (60), Animation/TabAnimation.swift (21). The bar is 30 methods; this is 51 over it, 2.70× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: NimbusFeatureFlagLayer firefox-ios/Client/Nimbus/NimbusFeatureFlagLayer.swift:13— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TabManagerImplementation firefox-ios/Client/TabManagement/TabManagerImplementation.swift:13— TooManyMethods — 76 methods. The bar is 30 methods; this is 46 over it, 2.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BookmarksViewController firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:13— TooManyMethods — 68 methods. The bar is 30 methods; this is 38 over it, 2.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: URLBar focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:14— TooManyMethods — 67 methods. The bar is 30 methods; this is 37 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TabManagerMiddleware firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift:17— TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TranslationsDocument REDACTED:652— TooManyMethods — 62 methods. The bar is 30 methods; this is 32 over it, 2.07× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Nimbus MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Nimbus.swift:8— TooManyMethods — 57 methods, declared across 5 files: Nimbus/Nimbus.swift (50), Nimbus/NimbusCreate.swift (2), Nimbus/Nimbus.swift (2), Nimbus/NimbusCreate.swift (2), +1 more file(s). The bar is 30 methods; this is 27 over it, 1.90× the bar. That list is where to read them, not a suggestion to split the file: the members belong to the type wherever they are declared, so moving them between files leaves the count unchanged. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SettingsCoordinator firefox-ios/Client/Coordinators/SettingsCoordinator.swift:22— TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SearchSettingsTableViewController firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:18— TooManyMethods — 55 methods. The bar is 30 methods; this is 25 over it, 1.83× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: Tab firefox-ios/Client/TabManagement/Tab.swift:82— TooManyMethods — 54 methods. The bar is 30 methods; this is 24 over it, 1.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: AddressToolbarContainer firefox-ios/Client/Frontend/Browser/Toolbars/AddressToolbarContainer.swift:55— TooManyMethods — 52 methods. The bar is 30 methods; this is 22 over it, 1.73× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RustPlaces firefox-ios/Storage/Rust/RustPlaces.swift:84— TooManyMethods — 50 methods. The bar is 30 methods; this is 20 over it, 1.67× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LocationView BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationView.swift:8— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: RootViewController SampleBrowser/SampleBrowser/UI/RootViewController.swift:10— TooManyMethods — 49 methods. The bar is 30 methods; this is 19 over it, 1.63× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LegacyTabScrollController firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:30— TooManyMethods — 46 methods. The bar is 30 methods; this is 16 over it, 1.53× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: LegacyWebViewController focus-ios/Blockzilla/Modules/WebView/LegacyWebViewController.swift:47— TooManyMethods — 45 methods. The bar is 30 methods; this is 15 over it, 1.50× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: SearchViewController firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:37— TooManyMethods — 44 methods. The bar is 30 methods; this is 14 over it, 1.47× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BrowserAddressToolbar BrowserKit/Sources/ToolbarKit/AddressToolbar/BrowserAddressToolbar.swift:14— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: TrackingProtectionViewController firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift:49— TooManyMethods — 43 methods. The bar is 30 methods; this is 13 over it, 1.43× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
TooManyMethods: BrowserViewController SampleBrowser/SampleBrowser/UI/Browser/BrowserViewController.swift:17— TooManyMethods — 42 methods. The bar is 30 methods; this is 12 over it, 1.40× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
+ 17 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (9 corresponding lines) · ×41
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Extensions/UIViewController+Extension.swift:168— firefox-ios/Client/Extensions/UIViewController+Extension.swift:168-176 | firefox-ios/Client/Extensions/UIViewController+Extension.swift:178-186 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) focus-ios/Blockzilla/Settings/Controller/AddSearchEngineViewController.swift:315— focus-ios/Blockzilla/Settings/Controller/AddSearchEngineViewController.swift:315-323 | focus-ios/Blockzilla/Settings/Controller/AddSearchEngineViewController.swift:325-333 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:117— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:117-125 | firefox-ios/Client/Frontend/Settings/Translation/TranslationPickerSettingsViewController.swift:172-181 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Experiments/Settings/ExperimentsBranchesViewController.swift:39— firefox-ios/Client/Experiments/Settings/ExperimentsBranchesViewController.swift:39-47 | firefox-ios/Client/Experiments/Settings/ExperimentsViewController.swift:86-95 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Storage/Rust/RustPlaces.swift:312— firefox-ios/Storage/Rust/RustPlaces.swift:312-324 | firefox-ios/Storage/Rust/RustPlaces.swift:348-356 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) BrowserKit/Sources/Shared/Deferred/Deferred.swift:108— BrowserKit/Sources/Shared/Deferred/Deferred.swift:108-116 | focus-ios/Deferred/Deferred.swift:87-95 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift:81— BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift:81-89 | firefox-ios/Client/Frontend/Reader/ReaderModeHandlers.swift:61-73 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Telemetry/GleanUsageReporting.swift:168— firefox-ios/Client/Telemetry/GleanUsageReporting.swift:168-176 | focus-ios/Blockzilla/UsageProfileManager.swift:19-27 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/Browser/Zoom/ZoomLevel.swift:55— firefox-ios/Client/Frontend/Browser/Zoom/ZoomLevel.swift:55-63 | firefox-ios/Client/Frontend/Browser/Zoom/ZoomLevel.swift:71-79 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:124— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:124-132 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:124-132 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:3817— firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:3817-3825 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:3827-3841 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Models/AddressToolbarContainerModel.swift:340— firefox-ios/Client/Frontend/Browser/Toolbars/Models/AddressToolbarContainerModel.swift:340-348 | firefox-ios/Client/Frontend/Browser/Toolbars/Models/NavigationToolbarContainerModel.swift:63-71 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsView.swift:72— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsView.swift:72-84 | firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsView.swift:91-99 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:243— firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:243-251 | firefox-ios/Client/Frontend/TrackingProtection/TrackingDetailsHelpers/BlockedTrackersLearnMoreViewController.swift:141-149 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:291— firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:291-299 | firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataSearchResultsViewController.swift:160-168 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetView.swift:43— firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetView.swift:43-51 | focus-ios/Blockzilla/Menu/Old/PhotonActionSheetCell.swift:22-30 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) BrowserKit/Sources/Redux/Store.swift:80— BrowserKit/Sources/Redux/Store.swift:80-88 | BrowserKit/Sources/Redux/Store.swift:91-99 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) SampleBrowser/SampleBrowser/UI/Settings/SettingsDataSource.swift:43— SampleBrowser/SampleBrowser/UI/Settings/SettingsDataSource.swift:43-52 | SampleBrowser/SampleBrowser/UI/Suggestion/SuggestionDataSource.swift:28-36 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseTelemetry.swift:22— firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseTelemetry.swift:22-30 | firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseTelemetry.swift:69-77 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Storage/Rust/RustLogins.swift:708— firefox-ios/Storage/Rust/RustLogins.swift:708-716 | firefox-ios/Storage/Rust/RustLogins.swift:718-726 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:323— firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:323-331 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:649-659 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) SampleComponentLibraryApp/SampleComponentLibraryApp/ContextualHintView/ContextualHintViewViewController.swift:76— SampleComponentLibraryApp/SampleComponentLibraryApp/ContextualHintView/ContextualHintViewViewController.swift:76-84 | firefox-ios/Client/Frontend/ContextualHint/ContextualHintViewController.swift:76-84 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) focus-ios/Blockzilla/Pro Tips/TipViewController.swift:44— focus-ios/Blockzilla/Pro Tips/TipViewController.swift:44-52 | focus-ios/Blockzilla/Pro Tips/TipsPageViewController.swift:32-40 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksCell.swift:118— firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksCell.swift:118-126 | firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/JumpBackInCell.swift:192-200 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (9 corresponding lines) firefox-ios/Client/Frontend/Theme/ThemedTableViewController.swift:41— firefox-ios/Client/Frontend/Theme/ThemedTableViewController.swift:41-49 | firefox-ios/Client/Frontend/Components/ThemedNavigationController.swift:32-40 — These two members are one piece of code written twice and then edited apart: 9 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
FileTooLong: Shared/Strings.swift firefox-ios/Shared/Strings.swift— FileTooLong — 8429 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 7929 over it, 16.86× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Views/BrowserViewController.swift firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift— FileTooLong — 3313 significant lines (blank, comment-only and punctuation-only lines excluded), about 81% of them inside a single declaration: BrowserViewController (29-4292). The bar is 500 significant lines; this is 2813 over it, 6.63× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: CC_Script/bergamot-translator.js firefox-ios/Client/Assets/CC_Script/bergamot-translator.js— FileTooLong — 2554 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 100% of them inside a single declaration: loadBergamot (5-3636). The bar is 1500 significant lines; this is 1054 over it, 1.70× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 2534 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 60% of them inside a single declaration: TranslationsDocument (652-4544). The bar is 500 significant lines; this is 2034 over it, 5.07× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: REDACTED REDACTED— FileTooLong — 2235 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units), about 100% of them inside a single declaration: AddressMetaData (16-2450). The bar is 1500 significant lines; this is 735 over it, 1.49× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Blockzilla/BrowserViewController.swift focus-ios/Blockzilla/BrowserViewController.swift— FileTooLong — 1421 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 921 over it, 2.84× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Telemetry/TelemetryWrapper.swift firefox-ios/Client/Telemetry/TelemetryWrapper.swift— FileTooLong — 1239 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 739 over it, 2.48× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Browser/BrowserCoordinator.swift firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift— FileTooLong — 1222 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: BrowserCoordinator (23-1860). The bar is 500 significant lines; this is 722 over it, 2.44× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: SQL/BrowserSchema.swift firefox-ios/Storage/SQL/BrowserSchema.swift— FileTooLong — 1159 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: BrowserSchema (147-1743). The bar is 500 significant lines; this is 659 over it, 2.32× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Extensions/BrowserViewController+WebViewDelegates.swift firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift— FileTooLong — 1062 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 562 over it, 2.12× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Homepage/HomepageViewController.swift firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift— FileTooLong — 1043 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: HomepageViewController (11-1611). The bar is 500 significant lines; this is 543 over it, 2.09× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: CC_Script/fathom.mjs firefox-ios/Client/Assets/CC_Script/fathom.mjs— FileTooLong — 983 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 483 over it, 1.97× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: TabManagement/TabManagerImplementation.swift firefox-ios/Client/TabManagement/TabManagerImplementation.swift— FileTooLong — 922 significant lines (blank, comment-only and punctuation-only lines excluded), about 97% of them inside a single declaration: TabManagerImplementation (13-1514). The bar is 500 significant lines; this is 422 over it, 1.84× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: URLBar/URLBar.swift focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift— FileTooLong — 872 significant lines (blank, comment-only and punctuation-only lines excluded), about 91% of them inside a single declaration: URLBar (14-1176). The bar is 500 significant lines; this is 372 over it, 1.74× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Views/TabTrayViewController.swift firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift— FileTooLong — 852 significant lines (blank, comment-only and punctuation-only lines excluded), about 98% of them inside a single declaration: TabTrayViewController (27-1265). The bar is 500 significant lines; this is 352 over it, 1.70× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: CC_Script/CreditCardRuleset.sys.mjs firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs— FileTooLong — 841 significant lines (blank, comment-only and punctuation-only lines excluded; the length bar is tripled for a single-responsibility module of 4 or fewer top-level units). The bar is 500 significant lines; this is 341 over it, 1.68× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: ./Dangerfile.swift Dangerfile.swift— FileTooLong — 831 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 331 over it, 1.66× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Settings/SettingsTableViewController.swift firefox-ios/Client/Frontend/Settings/SettingsTableViewController.swift— FileTooLong — 797 significant lines (blank, comment-only and punctuation-only lines excluded). The bar is 500 significant lines; this is 297 over it, 1.59× the bar. To reduce it, split the file along the responsibilities already in it: move each cohesive group of declarations into its own sibling file in the same module or package, so no one file has to be read whole to change one of them.
FileTooLong: Search/SearchViewController.swift firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift— FileTooLong — 772 significant lines (blank, comment-only and punctuation-only lines excluded), about 90% of them inside a single declaration: SearchViewController (37-1039). The bar is 500 significant lines; this is 272 over it, 1.54× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: CC_Script/FormAutofillUtils.sys.mjs firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs— FileTooLong — 771 significant lines (blank, comment-only and punctuation-only lines excluded), about 83% of them inside a single declaration: MAX_FIELD_VALUE_LENGTH (116-1441). The bar is 500 significant lines; this is 271 over it, 1.54× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Application/AccessibilityIdentifiers.swift firefox-ios/Client/Application/AccessibilityIdentifiers.swift— FileTooLong — 738 significant lines (blank, comment-only and punctuation-only lines excluded), about 100% of them inside a single declaration: AccessibilityIdentifiers (15-1040). The bar is 500 significant lines; this is 238 over it, 1.48× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Middleware/TabManagerMiddleware.swift firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift— FileTooLong — 735 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: TabManagerMiddleware (18-1105). The bar is 500 significant lines; this is 235 over it, 1.47× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: CC_Script/FormAutofillHeuristics.sys.mjs firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs— FileTooLong — 656 significant lines (blank, comment-only and punctuation-only lines excluded), about 96% of them inside a single declaration: FormAutofillHeuristics (35-1472). The bar is 500 significant lines; this is 156 over it, 1.31× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Layout/HomepageSectionLayoutProvider.swift firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift— FileTooLong — 648 significant lines (blank, comment-only and punctuation-only lines excluded), about 99% of them inside a single declaration: HomepageSectionLayoutProvider (11-999). The bar is 500 significant lines; this is 148 over it, 1.30× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
FileTooLong: Bookmarks/BookmarksViewController.swift firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift— FileTooLong — 640 significant lines (blank, comment-only and punctuation-only lines excluded), about 77% of them inside a single declaration: BookmarksViewController (13-785). The bar is 500 significant lines; this is 140 over it, 1.28× the bar. Moving the declarations that sit BESIDE it into sibling files will not shorten this file. Extract from INSIDE that declaration instead: lift each cohesive group of its body — the parts that share the same inputs and are named together — into its own unit in a sibling file, and have the original call them.
ClassTooLong: BrowserViewController firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:29— ClassTooLong — 2683 significant lines (blank, comment-only and punctuation-only lines excluded), 209 methods. The bar is 400 significant lines; this is 2283 over it, 6.71× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TranslationsDocument REDACTED:652— ClassTooLong — 1518 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 400 significant lines; this is 1118 over it, 3.80× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BrowserCoordinator firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:23— ClassTooLong — 1206 significant lines (blank, comment-only and punctuation-only lines excluded), 120 methods. The bar is 400 significant lines; this is 806 over it, 3.02× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BrowserSchema firefox-ios/Storage/SQL/BrowserSchema.swift:147— ClassTooLong — 1049 significant lines (blank, comment-only and punctuation-only lines excluded), 15 methods. The bar is 400 significant lines; this is 649 over it, 2.62× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HomepageViewController firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:11— ClassTooLong — 1031 significant lines (blank, comment-only and punctuation-only lines excluded), 94 methods. The bar is 400 significant lines; this is 631 over it, 2.58× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TabManagerImplementation firefox-ios/Client/TabManagement/TabManagerImplementation.swift:13— ClassTooLong — 893 significant lines (blank, comment-only and punctuation-only lines excluded), 76 methods. The bar is 400 significant lines; this is 493 over it, 2.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TabTrayViewController firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:27— ClassTooLong — 836 significant lines (blank, comment-only and punctuation-only lines excluded), 81 methods. The bar is 400 significant lines; this is 436 over it, 2.09× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BrowserViewController focus-ios/Blockzilla/BrowserViewController.swift:16— ClassTooLong — 830 significant lines (blank, comment-only and punctuation-only lines excluded), 380 methods. The bar is 400 significant lines; this is 430 over it, 2.08× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: URLBar focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:14— ClassTooLong — 797 significant lines (blank, comment-only and punctuation-only lines excluded), 67 methods. The bar is 400 significant lines; this is 397 over it, 1.99× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AccessibilityIdentifiers firefox-ios/Client/Application/AccessibilityIdentifiers.swift:15— ClassTooLong — 737 significant lines (blank, comment-only and punctuation-only lines excluded), 0 methods. The bar is 400 significant lines; this is 337 over it, 1.84× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TabManagerMiddleware firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift:17— ClassTooLong — 724 significant lines (blank, comment-only and punctuation-only lines excluded), 62 methods. The bar is 400 significant lines; this is 324 over it, 1.81× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SearchViewController firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:37— ClassTooLong — 697 significant lines (blank, comment-only and punctuation-only lines excluded), 44 methods. The bar is 400 significant lines; this is 297 over it, 1.74× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: HomepageSectionLayoutProvider firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift:10— ClassTooLong — 644 significant lines (blank, comment-only and punctuation-only lines excluded), 26 methods. The bar is 400 significant lines; this is 244 over it, 1.61× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: FormAutofillHandler REDACTED:34— ClassTooLong — 614 significant lines (blank, comment-only and punctuation-only lines excluded), 41 methods. The bar is 400 significant lines; this is 214 over it, 1.54× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: Tab firefox-ios/Client/TabManagement/Tab.swift:82— ClassTooLong — 581 significant lines (blank, comment-only and punctuation-only lines excluded), 54 methods. The bar is 400 significant lines; this is 181 over it, 1.45× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BrowserViewControllerState firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:19— ClassTooLong — 579 significant lines (blank, comment-only and punctuation-only lines excluded), 36 methods. The bar is 400 significant lines; this is 179 over it, 1.45× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TranslationsMiddleware firefox-ios/Client/Frontend/Translations/TranslationsMiddleware.swift:11— ClassTooLong — 562 significant lines (blank, comment-only and punctuation-only lines excluded), 32 methods. The bar is 400 significant lines; this is 162 over it, 1.41× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: LocationView BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationView.swift:8— ClassTooLong — 553 significant lines (blank, comment-only and punctuation-only lines excluded), 49 methods. The bar is 400 significant lines; this is 153 over it, 1.38× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SearchSettingsTableViewController firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:18— ClassTooLong — 534 significant lines (blank, comment-only and punctuation-only lines excluded), 55 methods. The bar is 400 significant lines; this is 134 over it, 1.34× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: MainMenuConfigurationUtility firefox-ios/Client/Frontend/Browser/MainMenu/MainMenuConfigurationUtility.swift:10— ClassTooLong — 524 significant lines (blank, comment-only and punctuation-only lines excluded), 17 methods. The bar is 400 significant lines; this is 124 over it, 1.31× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: TrackingProtectionViewController firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift:49— ClassTooLong — 519 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 119 over it, 1.30× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: AddressToolbarContainer firefox-ios/Client/Frontend/Browser/Toolbars/AddressToolbarContainer.swift:55— ClassTooLong — 508 significant lines (blank, comment-only and punctuation-only lines excluded), 52 methods. The bar is 400 significant lines; this is 108 over it, 1.27× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BookmarksViewController firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:13— ClassTooLong — 491 significant lines (blank, comment-only and punctuation-only lines excluded), 68 methods. The bar is 400 significant lines; this is 91 over it, 1.23× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: BrowserAddressToolbar BrowserKit/Sources/ToolbarKit/AddressToolbar/BrowserAddressToolbar.swift:14— ClassTooLong — 480 significant lines (blank, comment-only and punctuation-only lines excluded), 43 methods. The bar is 400 significant lines; this is 80 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
ClassTooLong: SettingsViewController focus-ios/Blockzilla/Settings/Controller/SettingsViewController.swift:15— ClassTooLong — 479 significant lines (blank, comment-only and punctuation-only lines excluded), 31 methods. The bar is 400 significant lines; this is 79 over it, 1.20× the bar. To reduce it, group the members that share the same data into a smaller type of their own and delegate to it, so no single type carries every responsibility.
Duplicated block (8 lines × 2) BrowserKit/Sources/MenuKit/MenuAccountCell.swift:134— BrowserKit/Sources/MenuKit/MenuAccountCell.swift:134-141 | BrowserKit/Sources/MenuKit/MenuCell.swift:113-120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/MenuKit/MenuAccountCell.swift:134` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:94— BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:94-101 | BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingMultipleChoiceCardView.swift:87-94 — before extracting anything, compare `BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift` and `BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingMultipleChoiceCardView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:118— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:118-125 | firefox-ios/Client/Frontend/Settings/Translation/TranslationPickerSettingsViewController.swift:174-181 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Settings/Translation/TranslationPickerSettingsViewController.swift:174` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift:217— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift:217-224 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusBuilder.swift:220-227 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusBuilder.swift` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusBuilder.swift:233` calls `record` and `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift:230` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:72— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:72-79 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:68-75 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) SampleBrowser/SampleBrowser/UI/Settings/SettingsViewController.swift:50— SampleBrowser/SampleBrowser/UI/Settings/SettingsViewController.swift:50-57 | SampleBrowser/SampleBrowser/UI/Suggestion/SuggestionViewController.swift:42-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `SampleBrowser/SampleBrowser/UI/Settings/SettingsViewController.swift:50` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 2) SampleBrowser/SampleBrowser/UI/Suggestion/SuggestionViewController.swift:38— SampleBrowser/SampleBrowser/UI/Suggestion/SuggestionViewController.swift:38-45 | firefox-ios/Client/Frontend/Library/Downloads/DownloadsPanel.swift:97-104 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEngineSelector.swift:157— firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEngineSelector.swift:157-164 | firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEngineSelector.swift:168-175 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2) firefox-ios/Client/Coordinators/CredentialAutofillCoordinator.swift:310— firefox-ios/Client/Coordinators/CredentialAutofillCoordinator.swift:310-317 | firefox-ios/Client/Coordinators/Library/LibraryCoordinator.swift:215-222 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Coordinators/CredentialAutofillCoordinator.swift:310` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:89— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:89-96 | firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:108-115 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:89` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:87` calls `configureLearnMoreButton` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:106` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:110— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:110-117 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewModel.swift:132-139 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewModel.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:110` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) firefox-ios/Storage/SQL/BrowserSchema.swift:969— firefox-ios/Storage/SQL/BrowserSchema.swift:969-976 | firefox-ios/Storage/SQL/ReadingListSchema.swift:40-47 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Storage/SQL/BrowserSchema.swift:969` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) BrowserKit/Sources/VPNKit/VPNAppAttestServer.swift:81— BrowserKit/Sources/VPNKit/VPNAppAttestServer.swift:81-88 | BrowserKit/Sources/VPNKit/VPNAppAttestServer.swift:100-107 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/VPNKit/VPNAppAttestServer.swift:81` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 2) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:70— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:70-77 | BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift:88-96 — before extracting anything, compare `BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift` and `BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift:32— BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift:32-39 | firefox-ios/Storage/PageMetadata.swift:32-39 — before extracting anything, compare `BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift` and `firefox-ios/Storage/PageMetadata.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (8 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift:61— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift:61-68 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift:63-70 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:386— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:386-393 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift:386-393 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:399— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:399-406 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift:399-406 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:58— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:58-65 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:58-65 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:67— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:67-74 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:67-74 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) SampleBrowser/SampleBrowser/AppDelegate.swift:53— SampleBrowser/SampleBrowser/AppDelegate.swift:53-60 | SampleComponentLibraryApp/SampleComponentLibraryApp/AppDelegate.swift:31-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (8 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:174— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:174-181 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:198-205 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:210— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:210-217 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:235-242 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:333— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:333-340 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:366-373 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 2) firefox-ios/Client/Frontend/Browser/Toolbars/SwipeUpTabPreviewGestureHandler.swift:82— firefox-ios/Client/Frontend/Browser/Toolbars/SwipeUpTabPreviewGestureHandler.swift:82-89 | firefox-ios/Client/Frontend/Browser/Toolbars/TabSwipeGestureHandler.swift:119-126 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
+ 7 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (13 corresponding lines) · ×29
Edited copy of a member (13 corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift:167— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift:167-185 | firefox-ios/Storage/RustKeychain.swift:313-325 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) BrowserKit/Sources/ContentBlockingGenerator/JsonHelper.swift:8— BrowserKit/Sources/ContentBlockingGenerator/JsonHelper.swift:8-20 | BrowserKit/Sources/ContentBlockingGenerator/JsonHelper.swift:22-34 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:139— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:139-152 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:164-176 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputViewModel.swift:155— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputViewModel.swift:155-167 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputViewModel.swift:169-182 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift:576— firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift:576-591 | firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift:593-605 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:526— firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:526-538 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:586-603 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/WKEngineView.swift:64— BrowserKit/Sources/WebEngine/WKWebview/WKEngineView.swift:64-76 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:173-192 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Library/Downloads/DownloadsPanel.swift:91— firefox-ios/Client/Frontend/Library/Downloads/DownloadsPanel.swift:91-108 | focus-ios/Blockzilla/Settings/Controller/AutocompleteSettingViewController.swift:31-43 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Storage/Rust/RustRemoteTabs.swift:191— firefox-ios/Storage/Rust/RustRemoteTabs.swift:191-203 | firefox-ios/Storage/Rust/RustRemoteTabs.swift:235-248 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) BrowserKit/Sources/ToolbarKit/AddressToolbar/BrowserAddressToolbar.swift:639— BrowserKit/Sources/ToolbarKit/AddressToolbar/BrowserAddressToolbar.swift:639-651 | BrowserKit/Sources/ToolbarKit/ToolbarButton.swift:298-313 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:50— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:50-62 | BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift:68-80 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Settings/ClearPrivateDataTableViewController.swift:97— firefox-ios/Client/Frontend/Settings/ClearPrivateDataTableViewController.swift:97-109 | firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataSearchResultsViewController.swift:43-58 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) Dangerfile.swift:977— Dangerfile.swift:977-989 | Dangerfile.swift:991-1012 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/TabManagement/TabManager.swift:173— firefox-ios/Client/TabManagement/TabManager.swift:173-185 | firefox-ios/Client/TabManagement/TabManagerImplementation.swift:360-373 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Coordinators/AddressAutofillCoordinator.swift:29— firefox-ios/Client/Coordinators/AddressAutofillCoordinator.swift:29-41 | firefox-ios/Client/Coordinators/CredentialAutofillCoordinator.swift:26-40 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksFolderCell.swift:18— firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksFolderCell.swift:18-30 | firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksFolderCell.swift:34-46 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Widgets/PrivateModeButton.swift:24— firefox-ios/Client/Frontend/Widgets/PrivateModeButton.swift:24-37 | firefox-ios/Client/Frontend/Browser/PrivateModeButton.swift:24-36 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Autofill/LoginListView.swift:53— firefox-ios/Client/Frontend/Autofill/LoginListView.swift:53-65 | firefox-ios/Client/Frontend/Autofill/LoginAutofillView.swift:51-63 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Share/TitleActivityItemProvider.swift:40— firefox-ios/Client/Frontend/Share/TitleActivityItemProvider.swift:40-53 | firefox-ios/Client/Frontend/Share/URLActivityItemProvider.swift:57-69 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Reader/ReadabilityService.swift:130— firefox-ios/Client/Frontend/Reader/ReadabilityService.swift:130-142 | BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReadabilityOperation.swift:130-142 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) BrowserKit/Sources/LLMKit/ProviderSpecificFields.swift:39— BrowserKit/Sources/LLMKit/ProviderSpecificFields.swift:39-51 | firefox-ios/Client/Frontend/Browser/Toolbars/Redux/TranslationsConfiguration.swift:68-80 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Browser/TopTabDisplayManager.swift:729— firefox-ios/Client/Frontend/Browser/TopTabDisplayManager.swift:729-742 | firefox-ios/Client/Frontend/Browser/TopTabsViewController.swift:342-354 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/SyncedTabCell.swift:98— firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/SyncedTabCell.swift:98-110 | firefox-ios/Client/Frontend/StoriesFeed/StoryCell.swift:54-66 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Support/SendDataSetting.swift:93— firefox-ios/Client/Frontend/Settings/Main/Support/SendDataSetting.swift:93-106 | firefox-ios/Client/Frontend/Settings/Main/Support/StudiesToggleSetting.swift:62-74 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (13 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionBlockedTrackersView.swift:131— firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionBlockedTrackersView.swift:131-143 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionConnectionDetailsView.swift:149-161 — These two members are one piece of code written twice and then edited apart: 13 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (9 lines × 2) BrowserKit/Sources/MenuKit/MenuTableView.swift:43— BrowserKit/Sources/MenuKit/MenuTableView.swift:43-51 | BrowserKit/Sources/UnifiedSearchKit/SearchEngineTableView.swift:40-48 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) BrowserKit/Sources/Shared/InternalURL.swift:41— BrowserKit/Sources/Shared/InternalURL.swift:41-49 | focus-ios/Blockzilla/Utilities/InternalURL.swift:25-34 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) Dangerfile.swift:1063— Dangerfile.swift:1063-1071 | Dangerfile.swift:1073-1081 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `Dangerfile.swift:1063` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (9 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:183— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:183-191 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:207-215 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:219` calls `recordEvent` and `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:195` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (9 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:224— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:224-232 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:249-257 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) SampleComponentLibraryApp/SampleComponentLibraryApp/ContextualHintView/ContextualHintViewViewController.swift:66— SampleComponentLibraryApp/SampleComponentLibraryApp/ContextualHintView/ContextualHintViewViewController.swift:66-74 | firefox-ios/Client/Frontend/ContextualHint/ContextualHintViewController.swift:99-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (9 lines × 2) firefox-ios/Client/Coordinators/LaunchView/LaunchScreenViewController.swift:58— firefox-ios/Client/Coordinators/LaunchView/LaunchScreenViewController.swift:58-66 | firefox-ios/Client/Frontend/Onboarding/Views/PrivacyPolicyViewController.swift:54-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Coordinators/LaunchView/LaunchScreenViewController.swift:58` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) firefox-ios/Client/Frontend/AuthenticationManager/SensitiveViewController.swift:108— firefox-ios/Client/Frontend/AuthenticationManager/SensitiveViewController.swift:108-116 | firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheet.swift:249-257 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/AuthenticationManager/SensitiveViewController.swift:108` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:1025— firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:1025-1033 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:1071-1080 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:1025` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/JumpBackInCell.swift:169— firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/JumpBackInCell.swift:169-177 | firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/SyncedTabCell.swift:294-302 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (9 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:133— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:133-141 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:138-146 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:121— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:121-129 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift:125-133 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) firefox-ios/Client/Utils/GleanHttpUploader.swift:22— firefox-ios/Client/Utils/GleanHttpUploader.swift:22-30 | firefox-ios/Client/Utils/GleanOhttpUploader.swift:51-59 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Utils/GleanHttpUploader.swift:22` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (9 lines × 2) firefox-ios/Storage/Rust/RustRemoteTabs.swift:284— firefox-ios/Storage/Rust/RustRemoteTabs.swift:284-292 | firefox-ios/Storage/Rust/RustRemoteTabs.swift:297-305 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Storage/Rust/RustRemoteTabs.swift:284` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:137— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:137-145 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:172-180 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:137` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) firefox-ios/Storage/Rust/RustLogins.swift:110— firefox-ios/Storage/Rust/RustLogins.swift:110-118 | firefox-ios/Storage/Rust/RustLogins.swift:143-151 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Storage/Rust/RustLogins.swift:110` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:154— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:154-162 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:156-164 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/ArgumentProcessor.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Nimbus.swift:29— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Nimbus.swift:29-37 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Nimbus.swift:30-38 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Nimbus.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Nimbus.swift` as WHOLE FILES: 96% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:34— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:34-42 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:34-42 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:76— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:76-84 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:76-84 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:323— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:323-331 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:356-364 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:96— firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:96-104 | focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift:62-70 — before extracting anything, compare `firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift` and `focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 2) firefox-ios/Client/Frontend/Browser/FindInPageBar.swift:90— firefox-ios/Client/Frontend/Browser/FindInPageBar.swift:90-98 | focus-ios/Blockzilla/Utilities/FindInPageBar.swift:33-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) firefox-ios/Client/Frontend/Browser/Toasts/Toast.swift:193— firefox-ios/Client/Frontend/Browser/Toasts/Toast.swift:193-201 | firefox-ios/Client/Frontend/Reader/View/ReaderModeStyleViewController.swift:389-397 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9 lines × 2) firefox-ios/Client/Frontend/Microsurvey/Prompt/MicrosurveyPromptView.swift:222— firefox-ios/Client/Frontend/Microsurvey/Prompt/MicrosurveyPromptView.swift:222-230 | firefox-ios/Client/Frontend/Microsurvey/Survey/View/MicrosurveyViewController.swift:318-326 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
+ 3 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (6 corresponding lines) · ×27
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:157— firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:157-163 | firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:188-193 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionBlockedTrackersView.swift:145— firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionBlockedTrackersView.swift:145-150 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionConnectionStatusView.swift:119-124 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Browser/TermsOfUse/View/TermsOfUseLinkViewController.swift:164— firefox-ios/Client/Frontend/Browser/TermsOfUse/View/TermsOfUseLinkViewController.swift:164-169 | firefox-ios/Client/Frontend/Onboarding/Views/PrivacyPolicyViewController.swift:76-85 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Extensions/SiriShortcuts.swift:41— firefox-ios/Client/Frontend/Extensions/SiriShortcuts.swift:41-47 | focus-ios/Blockzilla/Siri/SiriShortcuts.swift:94-99 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/UserScriptProvider.swift:12— BrowserKit/Sources/WebEngine/WKWebview/Scripts/UserScriptProvider.swift:12-18 | firefox-ios/Client/Frontend/TabContentsScripts/UserScriptManager.swift:104-109 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) focus-ios/Blockzilla/Pro Tips/TipManager.swift:158— focus-ios/Blockzilla/Pro Tips/TipManager.swift:158-164 | focus-ios/Blockzilla/Tracking Protection/TrackingProtectionViewController.swift:342-347 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/About/VersionSetting.swift:34— firefox-ios/Client/Frontend/Settings/Main/About/VersionSetting.swift:34-39 | firefox-ios/Client/Frontend/Settings/Main/Debug/SentryIDSetting.swift:32-38 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) SampleBrowser/SampleBrowser/UI/RootViewController.swift:78— SampleBrowser/SampleBrowser/UI/RootViewController.swift:78-84 | firefox-ios/Client/Frontend/Browser/QRCodeViewController.swift:342-347 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:236— firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:236-241 | focus-ios/Blockzilla/Search/SearchEngine.swift:181-186 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:135— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:135-141 | firefox-ios/Client/Frontend/Browser/Tabs/Views/EmptyPrivateTabsView.swift:130-135 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsViewController.swift:219— firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsViewController.swift:219-224 | firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:292-297 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Home/PrivateHome/PrivateMessageCardCell.swift:114— firefox-ios/Client/Frontend/Home/PrivateHome/PrivateMessageCardCell.swift:114-119 | firefox-ios/Client/Frontend/PasswordManagement/BreachAlertsDetailView.swift:161-167 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewModel.swift:58— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewModel.swift:58-63 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSettingsViewModel.swift:31-40 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Browser/PrivateModeButton.swift:38— firefox-ios/Client/Frontend/Browser/PrivateModeButton.swift:38-43 | firefox-ios/Client/Frontend/Widgets/PrivateModeButton.swift:39-45 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Storage/SQL/BrowserSchema.swift:186— firefox-ios/Storage/SQL/BrowserSchema.swift:186-191 | firefox-ios/Storage/SQL/ReadingListSchema.swift:83-88 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) BrowserKit/Sources/Common/Utilities/MenuHelper/MenuHelperLoginInterface.swift:38— BrowserKit/Sources/Common/Utilities/MenuHelper/MenuHelperLoginInterface.swift:38-46 | BrowserKit/Sources/QuickAnswersKit/UI/QuickAnswersViewConfiguration.swift:22-27 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Policy/HTTPSchemePolicyDecider.swift:19— BrowserKit/Sources/WebEngine/WKWebview/Policy/HTTPSchemePolicyDecider.swift:19-24 | BrowserKit/Sources/WebEngine/WKWebview/Policy/LocalRequestPolicyDecider.swift:18-23 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Sync15/RustSyncTelemetryPing.swift:195— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Sync15/RustSyncTelemetryPing.swift:195-200 | focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift:22-27 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Translations/SchemeHandler/TranslationsSchemeHandler.swift:122— firefox-ios/Client/Frontend/Translations/SchemeHandler/TranslationsSchemeHandler.swift:122-127 | firefox-ios/Client/Frontend/Translations/TinyRouter/TinyRouterError.swift:35-40 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) BrowserKit/Sources/Shared/URLSession/URLSessionProtocol.swift:57— BrowserKit/Sources/Shared/URLSession/URLSessionProtocol.swift:57-62 | BrowserKit/Sources/TestKit/MockURLSession.swift:67-72 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) BrowserKit/Sources/MenuKit/MenuTableView.swift:120— BrowserKit/Sources/MenuKit/MenuTableView.swift:120-125 | BrowserKit/Sources/UnifiedSearchKit/SearchEngineTableView.swift:100-105 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:310— firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:310-315 | firefox-ios/Client/Frontend/Browser/TabScrollController/TabScrollHandler.swift:297-302 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Settings/CustomSearchViewController.swift:318— firefox-ios/Client/Frontend/Settings/CustomSearchViewController.swift:318-323 | firefox-ios/Client/Frontend/Settings/SettingsTableViewController.swift:652-657 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) BrowserKit/Sources/Common/Utilities/AppInfo.swift:29— BrowserKit/Sources/Common/Utilities/AppInfo.swift:29-34 | focus-ios/Shared/AppInfo.swift:53-58 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (6 corresponding lines) firefox-ios/Client/Frontend/Browser/SearchEngines/Views/SearchEngineSelectionViewController.swift:164— firefox-ios/Client/Frontend/Browser/SearchEngines/Views/SearchEngineSelectionViewController.swift:164-169 | firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift:433-438 — These two members are one piece of code written twice and then edited apart: 6 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Repeated repair: BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:196— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift changed 8 times in last 90 days and 8 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is WebCompatReportSheetViewController.makeDataSource at line 196), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17207 Tapping the X button in the Report Broken Site URL field closes the keyboard instead of clearing the field (#36264)”; “Add FXIOS-16188 [WebCompat] VoiceOver fixes for the report sheet (#35345)”; “Bugfix FXIOS-16641 Update selector pill and segmented control for TabTray (#35427)”; “Bugfix FXIOS-16650 Nova [Report broken site] - Preview button is blue no matter the theme (#35386)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:563— firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift changed 13 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 10 (its worst body is TabTrayViewController.applyTheme at line 563), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17247 [iPhone Duo] Align tab tray segmented control with vertical bar items in folded Duo (#36369)”; “Bugfix FXIOS-17112 [iPhone Duo] Tab Tray panel switcher bad layout. (#36084)”; “Bugfix FXIOS-16978 [Nova] Sync Tabs button text not visible in light mode (#35911)”; “Bugfix FXIOS-16640 Sync and save data button an sync icon are not purple (#35472)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:537— firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift changed 11 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is BookmarksViewController.tableView at line 537), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17154 [iPhone Duo] Bad UI styling in library panels. (#36170)”; “Bugfix FXIOS-16971 Use Localized Desktop Folder Names in Navigation Title (#35931)”; “Refactor NO_TICKET Fix ~40 nested weak self closure warnings in Xcode 27.2 beta (#35811)”; “Bugfix FXIOS-15396 [Bookmarks] Keep a searched bookmark in its own folder when edited (#35413)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/TabManagement/TabWebView.swift firefox-ios/Client/TabManagement/TabWebView.swift:140— firefox-ios/Client/TabManagement/TabWebView.swift changed 8 times in last 90 days and 7 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is TabWebView.updateVerticalBarInsets at line 140), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-16172 [iOS 27] Remove main screen references from Firefox Client (#36428)”; “Bugfix FXIOS-17226 [iPhone Duo] Keep web view layout viewport stable during tab swipe in folded Duo (#36315)”; “Bugfix FXIOS-17203 [iPhone Duo] Vertical bar background color in night mode. (#36280)”; “Bugfix FXIOS-17176 [iPhone Duo] Fix iPhone Duo safe-area insets and page background coloring (#36231)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/TabManagement/TabWebView.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift:311— firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift changed 6 times in last 90 days and 6 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is WebCompatReportViewController.title at line 311), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17214 - [Memory Leaks] - WebCompatReportCoordinator Memory Leak (#36301)”; “Add FXIOS-16188 [WebCompat] VoiceOver fixes for the report sheet (#35345)”; “Bugfix FXIOS-16495 [WebCompat] Announce the details field as optional (#35322)”; “Bugfix FXIOS-16487 [WebCompat] Show an error for an invalid URL (#35262)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/Browser/MainMenu/Views/MainMenuViewController.swift firefox-ios/Client/Frontend/Browser/MainMenu/Views/MainMenuViewController.swift:540— firefox-ios/Client/Frontend/Browser/MainMenu/Views/MainMenuViewController.swift changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is MainMenuViewController.updateSiteProtectionsHeaderWith at line 540), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-16172 [iOS 27] Remove main screen references from Firefox Client (#36428)”; “Bugfix FXIOS-17117 [iPhone Duo] Use native navigation bar close button for Duo in collapsed mode. (#36098)”; “Revert NO_TICKET "Refactor FXIOS-13097 [Swift 6 Migration] [Tech Debt] Adopt isolated deinits now that we are on Swift 6.2 - Sept 2026 Attempt (#35537)" (#35564)”; “Bugfix FXIOS-16649 [Nova] SIte Menu background is lighter than in Figma (#35359)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Browser/MainMenu/Views/MainMenuViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: BrowserKit/Sources/Common/Theming/NovaPrivateTheme.swift BrowserKit/Sources/Common/Theming/NovaPrivateTheme.swift:10— BrowserKit/Sources/Common/Theming/NovaPrivateTheme.swift changed 9 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is NovaPrivateTheme.colors at line 10), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17106 [Nova] Settings Menu Buggy and App Crashing (#36117)”; “Bugfix FXIOS-16982 Update Nova Glass Selected Fill Colors for Dark and Private Themes (#35967)”; “Bugfix FXIOS-16583 [Nova] Improve top address bar contrast over wallpapers (#35620)”; “Bugfix FXIOS-16641 Update selector pill and segmented control for TabTray (#35427)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- BrowserKit/Sources/Common/Theming/NovaPrivateTheme.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/TabManagement/Tab.swift firefox-ios/Client/TabManagement/Tab.swift:222— firefox-ios/Client/TabManagement/Tab.swift changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 13 (its worst body is Tab.displayTitle at line 222), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17259 - Bugzilla 2085629 (#36498)”; “Bugfix FXIOS-16172 [iOS 27] Remove main screen references from Firefox Client (#36428)”; “Bugfix FXIOS-17203 [iPhone Duo] Vertical bar background color in night mode. (#36280)”; “Bugfix FXIOS-17176 [iPhone Duo] Fix iPhone Duo safe-area insets and page background coloring (#36231)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/TabManagement/Tab.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift:270— firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 14 (its worst body is TrackingProtectionViewController.newState at line 270), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17206 [iPhone Duo] ETP layout optimization. (#36277)”; “Bugfix FXIOS-16607 Use Failing Site Data for Tracking Protection and Main Menu on Error Pages (#35901)”; “BugFix FXIOS-16949 TrackingProtectionViewController Memory Leak (#35844)”; “Revert NO_TICKET "Refactor FXIOS-13097 [Swift 6 Migration] [Tech Debt] Adopt isolated deinits now that we are on Swift 6.2 - Sept 2026 Attempt (#35537)" (#35564)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: BrowserKit/Sources/Common/Theming/NovaDarkTheme.swift BrowserKit/Sources/Common/Theming/NovaDarkTheme.swift:10— BrowserKit/Sources/Common/Theming/NovaDarkTheme.swift changed 8 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is NovaDarkTheme.colors at line 10), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17106 [Nova] Settings Menu Buggy and App Crashing (#36117)”; “Bugfix FXIOS-16982 Update Nova Glass Selected Fill Colors for Dark and Private Themes (#35967)”; “Bugfix FXIOS-16583 [Nova] Improve top address bar contrast over wallpapers (#35620)”; “Bugfix FXIOS-16641 Update selector pill and segmented control for TabTray (#35427)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- BrowserKit/Sources/Common/Theming/NovaDarkTheme.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/Theme/ThemedTableViewCells/ThemedTableViewCell.swift firefox-ios/Client/Frontend/Theme/ThemedTableViewCells/ThemedTableViewCell.swift:26— firefox-ios/Client/Frontend/Theme/ThemedTableViewCells/ThemedTableViewCell.swift changed 6 times in last 90 days and 5 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is ThemedTableViewCell.systemLayoutSizeFitting at line 26), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17242 - Settings that have a switch should have the detail text size set to caption1 (#36356)”; “Bugfix FXIOS-17240 - Intermittent bold text display in settings menu (#36348)”; “Bugfix FXIOS-17151 - Close Private Tabs row subtitle text resizes/fluctuates when backgrounding app (#36163)”; “Bugfix FXIOS-17088 Fix Regressed UITests Related to Settings Accessibility Tree (#36074)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Theme/ThemedTableViewCells/ThemedTableViewCell.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Application/SceneDelegate.swift firefox-ios/Client/Application/SceneDelegate.swift:198— firefox-ios/Client/Application/SceneDelegate.swift changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is SceneDelegate.handle at line 198), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17338 - [Tab Loss] - Revert Pending Deeplink PR (#36534)”; “Refactor NO_TICKET Fix ~40 nested weak self closure warnings in Xcode 27.2 beta (#35811)”; “Bugfix FXIOS-29121 [Widgets] Prevent previous session flash on copied link (#35562)”; “Bugfix FXIOS-16747 [Nimbus] Bugzilla 2057743 (#35503)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Application/SceneDelegate.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/Browser/BrowserViewController/BrowserViewControllerLayoutManager.swift firefox-ios/Client/Frontend/Browser/BrowserViewController/BrowserViewControllerLayoutManager.swift:95— firefox-ios/Client/Frontend/Browser/BrowserViewController/BrowserViewControllerLayoutManager.swift changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is BrowserViewControllerLayoutManager.updateHeaderBarLayout at line 95), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17320 [iPhone Duo] Top address bar too close to the status bar on regular iPhones (#36508)”; “Bugfix FXIOS-14811 Fix Find in Page on iOS 15 (Legacy Find in Page) (#36449)”; “Bugfix FXIOS-17239 [iPhone Duo] Unfolded toolbar items not aligned with the status bar (#36358)”; “Bugfix FXIOS-16974 [iPhone Duo] Tab Strip data not refreshing. (#36132)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Browser/BrowserViewController/BrowserViewControllerLayoutManager.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: BrowserKit/Sources/Common/Theming/NovaLightTheme.swift BrowserKit/Sources/Common/Theming/NovaLightTheme.swift:10— BrowserKit/Sources/Common/Theming/NovaLightTheme.swift changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is NovaLightTheme.colors at line 10), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17106 [Nova] Settings Menu Buggy and App Crashing (#36117)”; “Bugfix FXIOS-16583 [Nova] Improve top address bar contrast over wallpapers (#35620)”; “Bugfix FXIOS-16641 Update selector pill and segmented control for TabTray (#35427)”; “Bugfix FXIOS-16571 [Nova] Toast message background is too light (#35252)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- BrowserKit/Sources/Common/Theming/NovaLightTheme.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/WebCompatReporter/Redux/WebCompatReporterState.swift firefox-ios/Client/Frontend/WebCompatReporter/Redux/WebCompatReporterState.swift:149— firefox-ios/Client/Frontend/WebCompatReporter/Redux/WebCompatReporterState.swift changed 6 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 9 (its worst body is WebCompatReporterState.reduceViewAction at line 149), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Add FXIOS-16188 [WebCompat] VoiceOver fixes for the report sheet (#35345)”; “Bugfix FXIOS-16487 [WebCompat] Show an error for an invalid URL (#35262)”; “Bugfix FXIOS-16484 [WebCompat] Use a checkbox for the Additional Info option (#35201)”; “Bugfix FXIOS-16486 [WebCompat] Fix the URL field label and alignment (#35221)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/WebCompatReporter/Redux/WebCompatReporterState.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarUXConfiguration.swift BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarUXConfiguration.swift:60— BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarUXConfiguration.swift changed 5 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is AddressToolbarUXConfiguration.locationContainerBackgroundColor at line 60), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-16847 [Toolbar] Weird display of the toolbar in light mode on iOS older than 26 (#35722)”; “Bugfix FXIOS-16583 [Nova] Improve top address bar contrast over wallpapers (#35620)”; “Bugfix FXIOS-16691 [Toolbar] Keep the minimized address bar off an opaque band (#35439)”; “Bugfix FXIOS-16570 [Nova] The background is lighter with addressbar on top (#35284)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarUXConfiguration.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: BrowserKit/Sources/WebCompatReporterKit/WebCompatReportViewModel.swift BrowserKit/Sources/WebCompatReporterKit/WebCompatReportViewModel.swift:97— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportViewModel.swift changed 4 times in last 90 days and 4 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 1 (its worst body is WebCompatReportViewModel.init at line 97), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Add FXIOS-16188 [WebCompat] VoiceOver fixes for the report sheet (#35345)”; “Bugfix FXIOS-16487 [WebCompat] Show an error for an invalid URL (#35262)”; “Bugfix FXIOS-16484 [WebCompat] Use a checkbox for the Additional Info option (#35201)”; “Bugfix FXIOS-16486 [WebCompat] Fix the URL field label and alignment (#35221)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- BrowserKit/Sources/WebCompatReporterKit/WebCompatReportViewModel.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:69— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is ExperimentRemoteTabsEmptyView.configure at line 69), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-16707 [Synced Tabs] Show empty state when no synced tabs are available (#35623)”; “Bugfix FXIOS-16983 Fix Cloud Icon Color in Tab Sync Page (#35928)”; “Bugfix FXIOS-16640 Sync and save data button an sync icon are not purple (#35472)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerModuleCell.swift firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerModuleCell.swift:94— firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerModuleCell.swift changed 5 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 2 (its worst body is TrackerBlockerModuleCell.configure at line 94), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-16842 [Homepage] Fix tracker blocker pill height in dynamic text size (#35707)”; “Bugfix FXIOS-16833 [Homepage] fix bold for You're Protected (#35710)”; “Bugfix FXIOS-16843 [Homepage] Fix dynamic font issue for tracker blocker pill (#35708)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerModuleCell.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/RustFxA/RustFirefoxAccounts.swift firefox-ios/RustFxA/RustFirefoxAccounts.swift:190— firefox-ios/RustFxA/RustFirefoxAccounts.swift changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is RustFirefoxAccounts.createAccountManager at line 190), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-16965 - [Sync] - Sync fails to work until the app is reinstalled (#36360)”; “Bugfix FXIOS-16850 - Main menu shows stale signed-in account after force-killing the app during sign-out (#35670)”; “Bugfix FXIOS-15545 - [Regression] - Mozilla account username is displayed after disconnect (#34840)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/RustFxA/RustFirefoxAccounts.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewController.swift firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewController.swift:357— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewController.swift changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 5 (its worst body is CreditCardBottomSheetViewController.tableView at line 357), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Refactor Bug 2078141 [CreditCard Autofill] Handle A-S autofill moving… (#35908)”; “Bugfix FXIOS-15166 [Credit Card Autofill] Fix saved card sheet initial height (#33430)”; “Refactor NO-TICKET - Revert log level to warning for CC failed decryption (#35321)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/NativeErrorPage/NativeErrorRegularContentView.swift firefox-ios/Client/Frontend/NativeErrorPage/NativeErrorRegularContentView.swift:209— firefox-ios/Client/Frontend/NativeErrorPage/NativeErrorRegularContentView.swift changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 6 (its worst body is NativeErrorRegularContentView.configureWaybackButton at line 209), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-16765 Fix Repeated VO Readout in Wayback Footer (#35630)”; “Bugfix FXIOS-16763 Change Wayback Error Card Icon to Custom Icon (#35629)”; “Bugfix FXIOS-16586 Fix invisible Wayback button upon refresh from NIC error page if we connect (#35214)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/NativeErrorPage/NativeErrorRegularContentView.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/Settings/Main/Support/SendDataSetting.swift firefox-ios/Client/Frontend/Settings/Main/Support/SendDataSetting.swift:58— firefox-ios/Client/Frontend/Settings/Main/Support/SendDataSetting.swift changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 7 (its worst body is SendDataSetting.onConfigureCell at line 58), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17088 Fix Regressed UITests Related to Settings Accessibility Tree (#36074)”; “Bugfix FXIOS-16735 Fix VO for Switch Buttons in Settings (#35666)”; “Bugfix FXIOS-16737 Stop the daily usage ping from following the technical data opt-out (#35515)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Settings/Main/Support/SendDataSetting.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: firefox-ios/Client/Frontend/PasswordGenerator/PasswordGeneratorViewController.swift firefox-ios/Client/Frontend/PasswordGenerator/PasswordGeneratorViewController.swift:22— firefox-ios/Client/Frontend/PasswordGenerator/PasswordGeneratorViewController.swift changed 4 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 4 (its worst body is PasswordGeneratorViewController.getContainerHorizontalPadding at line 22), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Refactor NO_TICKET Fix failing Robo builds running on old Xcode 26.2 (#36004)”; “Refactor NO_TICKET Fix ~40 nested weak self closure warnings in Xcode 27.2 beta (#35811)”; “Revert NO_TICKET "Refactor FXIOS-13097 [Swift 6 Migration] [Tech Debt] Adopt isolated deinits now that we are on Swift 6.2 - Sept 2026 Attempt (#35537)" (#35564)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/PasswordGenerator/PasswordGeneratorViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Repeated repair: BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationTextField.swift BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationTextField.swift:256— BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationTextField.swift changed 3 times in last 90 days and 3 of those changes were fix/bug commits, so repair is the majority of this file's churn. Its max cyclomatic complexity is 8 (its worst body is LocationTextField.updateRightView at line 256), AT OR UNDER the 15 threshold, so this is deliberately not filed as a churn × complexity hotspot — the difficulty here is in the behaviour the file has to get right, not in its control flow, and refactoring it for complexity would be the wrong move. The repairs counted were: “Bugfix FXIOS-17170 [Google Lens] Hide google lens tooltip once address bar button disappears (#36251)”; “Bugfix FXIOS-16693 - [Toolbar] Autocomplete re-inserts a stale suggestion (#35456)”; “Bugfix FXIOS-16694 [Autocomplete] Always append suggestions at the end of the query (#35407)”. Each one is a case this code did not handle. Before the next change lands here, check that every one of them is pinned by a test that fails without its fix; where the same area keeps coming back, the durable fix is usually at the interface that keeps being misused rather than at the line that was last corrected. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationTextField.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Swallowed exception (empty catch) firefox-ios/WidgetKit/OpenTabs/SimpleTab.swift:29— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Storage/FileAccessor.swift:109— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Telemetry/TelemetryWrapper.swift:87— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/TabManagement/Tab+ChangeUserAgent.swift:87— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Helpers/UserActivityHandler.swift:160— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/JSONLD.js:17— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentEnd/MetadataHelper.js:34— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/WebCompatPageContext.js:27— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:605— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Frontend/Settings/Main/Debug/DeleteExportedDataSetting.swift:27— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Frontend/Settings/Main/Debug/ExportBrowserDataSetting.swift:30— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Frontend/Settings/Main/Debug/ResetTipsSetting.swift:50— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Frontend/Reader/ReaderModeHandlers.swift:115— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Frontend/Browser/QRCodeViewController.swift:303— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Frontend/Browser/QRCodeViewController.swift:311— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Frontend/Browser/QRCodeViewController.swift:325— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/ContentBlocker/ContentBlocker+Safelist.swift:80— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js:48— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Assets/CC_Script/AutofillTelemetry.sys.mjs:60— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Assets/CC_Script/FieldScanner.sys.mjs:162— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Assets/CC_Script/FormAutofillChild.ios.sys.mjs:44— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Assets/CC_Script/TranslationsUtils.mjs:94— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2918— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) REDACTED:5200— An empty catch block silently discards the error — failures vanish with no log and no rethrow. Log it, handle it, or don't catch it.
Swallowed exception (empty catch) firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs:533— `.catch(() => {})` handles the rejection by doing nothing — the failure is discarded with no log and no rethrow, and the chain carries on as if the work succeeded. Log it through whatever this codebase already uses to report problems, hand it to a caller that can (`next(error)`, a returned rejection), or don't catch it.
+ 1 more in this group — see findings.md.
D4 · Code Duplication· Edited copy of a member (12 corresponding lines) · ×25
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:238— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:238-249 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:213-225 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:68— BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:68-79 | BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingMultipleChoiceCardView.swift:74-85 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+ToolBarActionMenuDelegate.swift:311— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+ToolBarActionMenuDelegate.swift:311-322 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+ToolBarActionMenuDelegate.swift:324-336 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Storage/Rust/RustRemoteTabs.swift:281— firefox-ios/Storage/Rust/RustRemoteTabs.swift:281-292 | firefox-ios/Storage/Rust/RustRemoteTabs.swift:294-305 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Settings/SettingsContentViewController.swift:79— firefox-ios/Client/Frontend/Settings/SettingsContentViewController.swift:79-96 | focus-ios/Blockzilla/Settings/Controller/SettingsContentViewController.swift:96-107 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) BrowserKit/Sources/Common/Utilities/AppInfo.swift:48— BrowserKit/Sources/Common/Utilities/AppInfo.swift:48-59 | focus-ios/Shared/AppInfo.swift:19-30 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:173— firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:173-184 | focus-ios/Blockzilla/UIComponents/GradientProgressBar.swift:164-175 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) BrowserKit/Sources/Shared/Functions.swift:73— BrowserKit/Sources/Shared/Functions.swift:73-85 | BrowserKit/Sources/Shared/Functions.swift:171-182 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/VPN/VPNMiddleware.swift:114— firefox-ios/Client/VPN/VPNMiddleware.swift:114-125 | firefox-ios/Client/VPN/VPNMiddleware.swift:127-138 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Settings/AdvancedAccountSettingViewController.swift:138— firefox-ios/Client/Frontend/Settings/AdvancedAccountSettingViewController.swift:138-154 | firefox-ios/Client/Frontend/Settings/SettingsTableViewController.swift:1146-1157 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/CertificatesViewController.swift:115— firefox-ios/Client/Frontend/TrackingProtection/CertificatesViewController.swift:115-126 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionDetailsViewController.swift:149-160 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) BrowserKit/Sources/SiteImageView/ImageProcessing/ImageHandler.swift:57— BrowserKit/Sources/SiteImageView/ImageProcessing/ImageHandler.swift:57-72 | BrowserKit/Sources/SiteImageView/ImageProcessing/ImageHandler.swift:74-85 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) BrowserKit/Sources/Shared/InternalURL.swift:61— BrowserKit/Sources/Shared/InternalURL.swift:61-72 | BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalURL.swift:71-82 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) BrowserKit/Sources/TestKit/MockLogger.swift:27— BrowserKit/Sources/TestKit/MockLogger.swift:27-41 | firefox-ios/Client/Frontend/Autofill/LoginListViewModel.swift:79-90 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2112— firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2112-2124 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2132-2143 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) BrowserKit/Sources/LLMKit/LiteLLMClient.swift:36— BrowserKit/Sources/LLMKit/LiteLLMClient.swift:36-47 | BrowserKit/Sources/LLMKit/LiteLLMClient.swift:53-64 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Nimbus.swift:360— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Nimbus.swift:360-371 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Nimbus.swift:362-373 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/NotificationCard/NotificationCardView.swift:43— firefox-ios/Client/Frontend/Home/Homepage/NotificationCard/NotificationCardView.swift:43-54 | firefox-ios/Client/Frontend/Onboarding/OnboardingCardView.swift:32-45 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Settings/ClearPrivateDataTableViewController.swift:202— firefox-ios/Client/Frontend/Settings/ClearPrivateDataTableViewController.swift:202-213 | firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataSearchResultsViewController.swift:60-71 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Application/BackgroundFirefoxSuggestIngestUtility.swift:38— firefox-ios/Client/Application/BackgroundFirefoxSuggestIngestUtility.swift:38-54 | firefox-ios/Client/Application/RemoteSettings/Application Services/ASTranslationModelsFetcher.swift:214-225 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Library/RecentlyClosedTabsPanel.swift:43— firefox-ios/Client/Frontend/Library/RecentlyClosedTabsPanel.swift:43-54 | firefox-ios/Client/Frontend/Settings/SettingsViewController.swift:29-40 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Privacy/NotificationsSetting.swift:21— firefox-ios/Client/Frontend/Settings/Main/Privacy/NotificationsSetting.swift:21-32 | firefox-ios/Client/Frontend/Settings/Main/Privacy/AddressAutofillSetting.swift:38-49 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift:246— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift:246-258 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusBuilder.swift:250-261 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Providers/Profile.swift:343— firefox-ios/Providers/Profile.swift:343-359 | firefox-ios/Providers/Profile.swift:361-372 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (12 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:84— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:84-95 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift:86-99 — These two members are one piece of code written twice and then edited apart: 12 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (11 lines × 2) BrowserKit/Sources/MenuKit/MenuTableViewHelper.swift:74— BrowserKit/Sources/MenuKit/MenuTableViewHelper.swift:74-84 | BrowserKit/Sources/MenuKit/MenuTableViewHelper.swift:104-114 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/MenuKit/MenuTableViewHelper.swift:74` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:52— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:52-62 | BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift:70-80 — before extracting anything, compare `BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift` and `BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:52` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Utils.swift:86— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Utils.swift:86-96 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Utils.swift:86-96 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Utils.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Utils.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:139— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:139-149 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:164-174 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:139` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:150` calls `startObservingContentScroll` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:175` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (11 lines × 2) SampleComponentLibraryApp/SampleComponentLibraryApp/CollapsibleCardView/CollapsibleCardViewViewController.swift:58— SampleComponentLibraryApp/SampleComponentLibraryApp/CollapsibleCardView/CollapsibleCardViewViewController.swift:58-68 | SampleComponentLibraryApp/SampleComponentLibraryApp/ShadowCardView/ShadowCardViewViewController.swift:54-64 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:257— firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:257-267 | focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift:169-179 — before extracting anything, compare `firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift` and `focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Autofill/Address/AddressCellView.swift:104— firefox-ios/Client/Frontend/Autofill/Address/AddressCellView.swift:104-114 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardItemRow.swift:57-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/Address/AddressCellView.swift:104` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewController.swift:439— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewController.swift:439-449 | firefox-ios/Client/Frontend/Onboarding/Views/PrivacyPreferencesViewController.swift:323-333 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewController.swift:439` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2349— firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2349-2359 | firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift:1022-1032 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:790— firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:790-800 | firefox-ios/Client/Frontend/Browser/TabScrollController/TabScrollHandler.swift:404-414 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:62— firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:62-72 | firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTraySelectorView.swift:148-158 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:62` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:417— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:417-427 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabCell.swift:361-371 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/TabCell.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:70— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:70-80 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:75-85 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:70` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `viewModel` to `EditBookmarkViewModel` in one and `GroupedEditBookmarkViewModel` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:226— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:226-236 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:232-242 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:66— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:66-76 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift:68-78 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:66` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `viewModel` to `EditFolderViewModel` in one and `GroupedEditFolderViewModel` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Settings/Clearables.swift:162— firefox-ios/Client/Frontend/Settings/Clearables.swift:162-172 | firefox-ios/Client/Frontend/Settings/Clearables.swift:202-212 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetViewModel.swift:82— firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetViewModel.swift:82-92 | firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetViewModel.swift:94-104 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 2) firefox-ios/Storage/SQL/BrowserSchema.swift:1634— firefox-ios/Storage/SQL/BrowserSchema.swift:1634-1644 | firefox-ios/Storage/SQL/BrowserSchema.swift:1646-1656 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (11 lines × 2) focus-ios/Blockzilla/Extensions/URLExtensions.swift:132— focus-ios/Blockzilla/Extensions/URLExtensions.swift:132-142 | focus-ios/Blockzilla/Extensions/URLExtensions.swift:148-158 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `focus-ios/Blockzilla/Extensions/URLExtensions.swift:132` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (11 lines × 2) focus-ios/Blockzilla/SearchSuggestions/OverlayView.swift:339— focus-ios/Blockzilla/SearchSuggestions/OverlayView.swift:339-349 | focus-ios/Blockzilla/SearchSuggestions/OverlayView.swift:421-431 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `focus-ios/Blockzilla/SearchSuggestions/OverlayView.swift:339` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift:69— BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift:69-79 | firefox-ios/Storage/PageMetadata.swift:69-79 — before extracting anything, compare `BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift` and `firefox-ios/Storage/PageMetadata.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift:69` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11 lines × 2) BrowserKit/Sources/Common/Utilities/DispatchQueueHelper.swift:10— BrowserKit/Sources/Common/Utilities/DispatchQueueHelper.swift:10-20 | BrowserKit/Sources/Common/Utilities/DispatchQueueInterface.swift:38-48 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksCell.swift:129— firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksCell.swift:129-139 | firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSiteCell.swift:305-315 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksSectionState.swift:75— firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksSectionState.swift:75-85 | firefox-ios/Client/Frontend/Home/Homepage/Merino/MerinoState.swift:101-111 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `state` to `BookmarksSectionState` in one and `MerinoState` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (11 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewModel.swift:83— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewModel.swift:83-93 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewModel.swift:84-94 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:68— BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:68-74 | BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingMultipleChoiceCardView.swift:74-80 — before extracting anything, compare `BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift` and `BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingMultipleChoiceCardView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:68` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKUserScriptManager.swift:35— BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKUserScriptManager.swift:35-41 | BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKUserScriptManager.swift:59-65 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKUserScriptManager.swift:35` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) SampleComponentLibraryApp/SampleComponentLibraryApp/FadeScrollViewComponent/FadeScrollViewViewController.swift:57— SampleComponentLibraryApp/SampleComponentLibraryApp/FadeScrollViewComponent/FadeScrollViewViewController.swift:57-63 | firefox-ios/RustFxA/FirefoxAccountSignInViewController.swift:222-228 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `SampleComponentLibraryApp/SampleComponentLibraryApp/FadeScrollViewComponent/FadeScrollViewViewController.swift:57` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `firefox-ios/RustFxA/FirefoxAccountSignInViewController.swift:230` calls `constraint` and `SampleComponentLibraryApp/SampleComponentLibraryApp/FadeScrollViewComponent/FadeScrollViewViewController.swift:65` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:208— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:208-214 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:226-232 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Browser/TabPrintPageRenderer.swift:44— firefox-ios/Client/Frontend/Browser/TabPrintPageRenderer.swift:44-50 | firefox-ios/Client/Frontend/Browser/TabPrintPageRenderer.swift:61-67 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift:1052— firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift:1052-1058 | firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift:1071-1077 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Translations/TranslationsMiddleware.swift:224— firefox-ios/Client/Frontend/Translations/TranslationsMiddleware.swift:224-230 | firefox-ios/Client/Frontend/Translations/TranslationsMiddleware.swift:321-327 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Translations/TranslationsMiddleware.swift:224` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) firefox-ios/Client/Experiments/Settings/Views/ExperimentsTableView.swift:8— firefox-ios/Client/Experiments/Settings/Views/ExperimentsTableView.swift:8-23 | firefox-ios/Client/Frontend/Theme/ThemedTableViewCells/ThemedSubtitleTableViewCell.swift:9-15 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Experiments/Settings/Views/ExperimentsTableView.swift:8` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (7 lines × 2) BrowserKit/Sources/ComponentLibrary/Headers/HeaderView.swift:248— BrowserKit/Sources/ComponentLibrary/Headers/HeaderView.swift:248-254 | BrowserKit/Sources/ComponentLibrary/Headers/NavigationHeaderView.swift:125-131 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:21— BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:21-27 | focus-ios/Deferred/ReadWriteLock.swift:17-23 — before extracting anything, compare `BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift` and `focus-ios/Deferred/ReadWriteLock.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:366— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:366-372 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift:366-372 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Utils.swift:73— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Utils.swift:73-79 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Utils.swift:73-79 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Utils.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Utils.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) SampleBrowser/SampleBrowser/UI/Components/NavigationToolbarContainer.swift:37— SampleBrowser/SampleBrowser/UI/Components/NavigationToolbarContainer.swift:37-45 | firefox-ios/Client/Extensions/UIWindow+Extension.swift:18-24 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:104— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:104-110 | firefox-ios/Client/Frontend/Settings/AppearanceSettings/DarkModeToggleView.swift:68-74 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:104` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Browser/FindInPageBar.swift:80— firefox-ios/Client/Frontend/Browser/FindInPageBar.swift:80-86 | focus-ios/Blockzilla/Utilities/FindInPageBar.swift:23-29 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:162— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:162-168 | firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsEmptyView.swift:151-157 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:116— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:116-122 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:121-127 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:97— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:97-103 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift:101-107 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:105— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:105-111 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift:109-115 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 58 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Library/Reader/ReaderPanel.swift:344— firefox-ios/Client/Frontend/Library/Reader/ReaderPanel.swift:344-350 | firefox-ios/Client/Frontend/Library/RecentlyClosedTabsPanel.swift:113-119 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/Settings/BrowsingSettingsViewController.swift:43— firefox-ios/Client/Frontend/Settings/BrowsingSettingsViewController.swift:43-49 | firefox-ios/Client/Frontend/Settings/Main/AppSettingsTableViewController.swift:346-352 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:254— firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:254-262 | firefox-ios/Client/Frontend/Translations/AutoTranslatePromptView.swift:146-152 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (7 lines × 2) firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:138— firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:138-150 | focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift:104-110 — before extracting anything, compare `firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift` and `focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (7 lines × 2) firefox-ios/Client/Telemetry/SystemCameraTelemetry.swift:25— firefox-ios/Client/Telemetry/SystemCameraTelemetry.swift:25-31 | firefox-ios/Client/Telemetry/SystemPhotoPickerTelemetry.swift:24-30 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Note first that the copies are not typed on the same thing: the declarations holding them bind `reason` to `CameraReason` in one and `PhotoPickerReason` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (7 lines × 2) firefox-ios/Storage/Rust/RustLogins.swift:241— firefox-ios/Storage/Rust/RustLogins.swift:241-247 | firefox-ios/Storage/Rust/RustRemoteTabs.swift:28-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/TabPeekViewController.swift:79— firefox-ios/Client/Frontend/Browser/Tabs/Views/TabPeekViewController.swift:79-84 | firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:536-541 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Tabs/Views/TabPeekViewController.swift:79` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1070— firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1070-1075 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:337-342 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1070` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1076` calls `sectionIdentifier` and `firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:343` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 2) firefox-ios/Storage/Rust/RustLogins.swift:31— firefox-ios/Storage/Rust/RustLogins.swift:31-36 | firefox-ios/Storage/RustKeychain.swift:360-369 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Storage/Rust/RustLogins.swift:31` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (6 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/HardcodedNimbusFeatures.swift:35— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/HardcodedNimbusFeatures.swift:35-40 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/HardcodedNimbusFeatures.swift:35-40 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/HardcodedNimbusFeatures.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/HardcodedNimbusFeatures.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) firefox-ios/Client/Telemetry/GleanUsageReporting.swift:54— firefox-ios/Client/Telemetry/GleanUsageReporting.swift:54-59 | focus-ios/Blockzilla/GleanUsageReportingMetricsService.swift:54-59 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:50— BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:50-55 | focus-ios/Deferred/ReadWriteLock.swift:46-51 — before extracting anything, compare `BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift` and `focus-ios/Deferred/ReadWriteLock.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:57— BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:57-62 | focus-ios/Deferred/ReadWriteLock.swift:53-58 — before extracting anything, compare `BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift` and `focus-ios/Deferred/ReadWriteLock.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/SearchEngineView/DropDownSearchEngineView.swift:86— BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/SearchEngineView/DropDownSearchEngineView.swift:86-91 | BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/SearchEngineView/PlainSearchEngineView.swift:70-75 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift:103— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift:103-108 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift:105-110 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (6 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift:113— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift:113-118 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift:115-120 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (6 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:408— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:408-413 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift:408-413 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:182— firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:182-187 | focus-ios/Blockzilla/Search/SearchEngine.swift:134-139 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/EmptyPrivateTabsView.swift:137— firefox-ios/Client/Frontend/Browser/Tabs/Views/EmptyPrivateTabsView.swift:137-142 | firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:143-148 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1432— firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1432-1437 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:398-403 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:967— firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:967-972 | firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel+Search.swift:10-16 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:305— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:305-310 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:236-241 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) BrowserKit/Sources/ComponentLibrary/Buttons/LinkButton.swift:74— BrowserKit/Sources/ComponentLibrary/Buttons/LinkButton.swift:74-79 | firefox-ios/Client/Frontend/Reader/View/ReaderModeFontTypeButton.swift:49-54 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) BrowserKit/Sources/Shared/InternalURL.swift:103— BrowserKit/Sources/Shared/InternalURL.swift:103-108 | BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalURL.swift:104-110 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 2) BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatCategoryMenuCell.swift:114— BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatCategoryMenuCell.swift:114-119 | BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatPreviewBulletListCell.swift:118-123 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:207— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:207-212 | firefox-ios/Client/Frontend/Home/Homepage/SearchBar/SearchBarCell.swift:104-109 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/NativeErrorPage/NativeErrorPageViewController.swift:271— firefox-ios/Client/Frontend/NativeErrorPage/NativeErrorPageViewController.swift:271-276 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift:318-323 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/Settings/NewTabContentSettingsViewController.swift:14— firefox-ios/Client/Frontend/Settings/NewTabContentSettingsViewController.swift:14-19 | firefox-ios/Client/Frontend/Settings/SiriSettingsViewController.swift:14-19 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (6 lines × 2) firefox-ios/WidgetKit/OpenTabs/TabProvider.swift:57— firefox-ios/WidgetKit/OpenTabs/TabProvider.swift:57-62 | firefox-ios/WidgetKit/TopSites/TopSitesProvider.swift:55-60 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `completion` to `@Sendable @escaping (Timeline<OpenTabsEntry>) -> Void` in one and `@Sendable @escaping (Timeline<TopSitesEntry>) -> Void` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (6 lines × 2) focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/OnboardingSearchWidgetView.swift:55— focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/OnboardingSearchWidgetView.swift:55-60 | focus-ios/Widgets/SearchWidgetView.swift:55-60 — before extracting anything, compare `focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/OnboardingSearchWidgetView.swift` and `focus-ios/Widgets/SearchWidgetView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 2) firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerSheetViewController.swift:225— firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerSheetViewController.swift:225-230 | firefox-ios/Client/Frontend/Onboarding/Views/PrivacyPreferencesViewController.swift:133-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) BrowserKit/Sources/MenuKit/MenuAccountCell.swift:124— BrowserKit/Sources/MenuKit/MenuAccountCell.swift:124-129 | BrowserKit/Sources/MenuKit/MenuCell.swift:106-110 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/MenuKit/MenuAccountCell.swift:124` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) firefox-ios/Client/Frontend/Library/Downloads/DownloadsPanel.swift:283— firefox-ios/Client/Frontend/Library/Downloads/DownloadsPanel.swift:283-288 | firefox-ios/Client/Frontend/Library/Reader/ReaderPanel.swift:305-309 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Downloads/DownloadsPanel.swift:283` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:371— firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:371-376 | firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataSearchResultsViewController.swift:181-185 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:371` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) firefox-ios/Client/TabManagement/TabManagerImplementation.swift:525— firefox-ios/Client/TabManagement/TabManagerImplementation.swift:525-531 | firefox-ios/Client/TabManagement/TabManagerImplementation.swift:603-607 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/TabManagement/TabManagerImplementation.swift:525` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) BrowserKit/Sources/Common/Extensions/URLExtension.swift:411— BrowserKit/Sources/Common/Extensions/URLExtension.swift:411-415 | focus-ios/Blockzilla/Extensions/URLExtensions.swift:15-19 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) BrowserKit/Sources/OnboardingKit/Views/Shared/AnimatedGradientRenderer.swift:121— BrowserKit/Sources/OnboardingKit/Views/Shared/AnimatedGradientRenderer.swift:121-128 | BrowserKit/Sources/OnboardingKit/Views/Shared/ImageBackgroundView.swift:14-18 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) BrowserKit/Sources/SummarizeKit/UI/AnimationController.swift:100— BrowserKit/Sources/SummarizeKit/UI/AnimationController.swift:100-104 | BrowserKit/Sources/SummarizeKit/UI/SummarizeController.swift:383-387 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:211— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:211-215 | BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift:284-289 — before extracting anything, compare `BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift` and `BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift:94— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift:94-98 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift:96-100 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (5 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:374— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:374-378 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift:374-378 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:380— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:380-384 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift:380-384 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift` as WHOLE FILES: this scan already matched 6 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusApi.swift:244— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusApi.swift:244-248 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusApi.swift:249-253 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusApi.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusApi.swift` as WHOLE FILES: 98% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:299— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:299-303 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:322-326 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) firefox-ios/Client/Frontend/Reader/SchemeHandler/ReaderModeSchemeHandler.swift:117— firefox-ios/Client/Frontend/Reader/SchemeHandler/ReaderModeSchemeHandler.swift:117-121 | firefox-ios/Client/Frontend/Translations/SchemeHandler/TranslationsSchemeHandler.swift:103-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) firefox-ios/Client/Frontend/Settings/Main/Support/SendDataSetting.swift:108— firefox-ios/Client/Frontend/Settings/Main/Support/SendDataSetting.swift:108-112 | firefox-ios/Client/Frontend/Settings/Main/Support/StudiesToggleSetting.swift:76-80 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/OnboardingSearchWidgetView.swift:12— focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/OnboardingSearchWidgetView.swift:12-16 | focus-ios/Widgets/SearchWidgetView.swift:12-16 — before extracting anything, compare `focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/OnboardingSearchWidgetView.swift` and `focus-ios/Widgets/SearchWidgetView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 2) BrowserKit/Sources/MenuKit/MenuPaddedLabel.swift:14— BrowserKit/Sources/MenuKit/MenuPaddedLabel.swift:14-20 | focus-ios/Blockzilla/UIComponents/InsetButton.swift:19-23 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 2) SampleBrowser/SampleBrowser/UI/Settings/SettingsCell.swift:12— SampleBrowser/SampleBrowser/UI/Settings/SettingsCell.swift:12-16 | firefox-ios/Client/Frontend/PasswordManagement/Cells/LoginDetailTableViewCell.swift:97-102 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) firefox-ios/Client/Coordinators/PasswordManagerCoordinator.swift:42— firefox-ios/Client/Coordinators/PasswordManagerCoordinator.swift:42-46 | firefox-ios/Client/Frontend/Browser/MainMenu/MainMenuCoordinator.swift:59-67 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (5 lines × 2) firefox-ios/Client/Frontend/Home/UnifiedAds/UnifiedAdsUserDataRemover.swift:29— firefox-ios/Client/Frontend/Home/UnifiedAds/UnifiedAdsUserDataRemover.swift:29-33 | firefox-ios/Client/Utils/GleanHttpUploader.swift:14-18 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Note first that the copies are not typed on the same thing: the declarations holding them bind `session` to `URLSessionProtocol = NetworkUtils.defaultURLSession()` in one and `URLSessionProtocol = NetworkUtils.defaultGleanPingURLSession()` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (5 lines × 2) firefox-ios/Client/Frontend/Settings/Main/Debug/MerinoTestDataSetting.swift:22— firefox-ios/Client/Frontend/Settings/Main/Debug/MerinoTestDataSetting.swift:22-26 | firefox-ios/Client/Frontend/Settings/Main/Debug/MockBreachAlertsSetting.swift:22-26 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (5 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:159— firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:159-163 | firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:189-193 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:143— firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:143-147 | focus-ios/Blockzilla/UIComponents/GradientProgressBar.swift:134-138 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:143` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 2) firefox-ios/Client/Telemetry/TelemetryWrapper.swift:1141— firefox-ios/Client/Telemetry/TelemetryWrapper.swift:1141-1145 | firefox-ios/Client/Telemetry/TelemetryWrapper.swift:1157-1161 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Telemetry/TelemetryWrapper.swift:1141` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
D4 · Code Duplication· Edited copy of a member (7 corresponding lines) · ×23
Edited copy of a member (7 corresponding lines) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:251— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:251-257 | BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:326-333 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:244— firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:244-250 | focus-ios/Blockzilla/Search/SearchEngine.swift:105-111 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) BrowserKit/Sources/Common/Extensions/ColorExtension.swift:9— BrowserKit/Sources/Common/Extensions/ColorExtension.swift:9-15 | focus-ios/BlockzillaPackage/Sources/DesignSystem/UIColor+AppColors.swift:58-64 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserPrompts.swift:122— firefox-ios/Client/Frontend/Browser/BrowserPrompts.swift:122-128 | firefox-ios/Client/Frontend/Browser/BrowserPrompts.swift:170-176 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:154— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:154-160 | firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsEmptyView.swift:143-149 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:880— firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:880-890 | firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsViewController.swift:274-280 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseTelemetry.swift:32— firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseTelemetry.swift:32-38 | firefox-ios/Client/Frontend/Onboarding/Models/TermsOfServiceTelemetry.swift:46-54 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Debug/InstallationDetailsSetting.swift:14— firefox-ios/Client/Frontend/Settings/Main/Debug/InstallationDetailsSetting.swift:14-22 | firefox-ios/Client/Frontend/Settings/Main/Debug/ResetInstallationHistorySetting.swift:18-24 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:251— firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:251-258 | firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:498-504 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/DefaultBrowserOnboardingView.swift:128— focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/DefaultBrowserOnboardingView.swift:128-134 | focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/ShowMeHowOnboardingView.swift:86-93 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Browser/Toasts/DownloadToast.swift:236— firefox-ios/Client/Frontend/Browser/Toasts/DownloadToast.swift:236-244 | firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift:110-116 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:400— firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:400-410 | firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataSearchResultsViewController.swift:204-210 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardItemRow.swift:146— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardItemRow.swift:146-153 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSettingsEmptyView.swift:96-102 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) focus-ios/BlockzillaPackage/Sources/Onboarding/Handler/OnboardingEventsHandlerV1.swift:21— focus-ios/BlockzillaPackage/Sources/Onboarding/Handler/OnboardingEventsHandlerV1.swift:21-29 | focus-ios/BlockzillaPackage/Sources/Onboarding/Handler/OnboardingEventsHandlerV2.swift:38-44 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) BrowserKit/Sources/SiteImageView/FaviconImageView.swift:34— BrowserKit/Sources/SiteImageView/FaviconImageView.swift:34-41 | BrowserKit/Sources/SiteImageView/HeroImageView.swift:50-56 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersHelpers/BlockedTrackersFooterView.swift:22— firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersHelpers/BlockedTrackersFooterView.swift:22-28 | firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersHelpers/BlockedTrackersHeaderView.swift:19-25 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Browser/SearchEngines/SearchEnginesManager.swift:309— firefox-ios/Client/Frontend/Browser/SearchEngines/SearchEnginesManager.swift:309-315 | focus-ios/Blockzilla/Search/SearchEngineManager.swift:195-201 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:29— BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:29-35 | focus-ios/Deferred/ReadWriteLock.swift:25-31 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/TabDisplayPanelViewController.swift:398— firefox-ios/Client/Frontend/Browser/Tabs/Views/TabDisplayPanelViewController.swift:398-404 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabDisplayView.swift:306-314 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) BrowserKit/Sources/ComponentLibrary/Buttons/PrimaryRoundedButton.swift:34— BrowserKit/Sources/ComponentLibrary/Buttons/PrimaryRoundedButton.swift:34-42 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionButton.swift:35-41 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:180— firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:180-186 | firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsViewController.swift:197-203 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) SampleBrowser/SampleBrowser/AppDelegate.swift:32— SampleBrowser/SampleBrowser/AppDelegate.swift:32-41 | SampleComponentLibraryApp/SampleComponentLibraryApp/AppDelegate.swift:14-20 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (7 corresponding lines) firefox-ios/Client/Frontend/FeltPrivacy/PrivateModeAction.swift:14— firefox-ios/Client/Frontend/FeltPrivacy/PrivateModeAction.swift:14-20 | firefox-ios/Client/Frontend/QuickAnswers/QuickAnswersAction.swift:13-20 — These two members are one piece of code written twice and then edited apart: 7 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (15 corresponding lines) · ×22
Edited copy of a member (15 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReadabilityResult.swift:36— BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReadabilityResult.swift:36-50 | BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReadabilityResult.swift:53-75 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift:65— BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift:65-79 | firefox-ios/Storage/PageMetadata.swift:65-79 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Reader/SchemeHandler/ReaderFileRoute.swift:17— firefox-ios/Client/Frontend/Reader/SchemeHandler/ReaderFileRoute.swift:17-45 | firefox-ios/Client/Frontend/Translations/SchemeHandler/StaticFileRoute.swift:8-22 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift:319— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift:319-333 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardTableViewModel.swift:22-40 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:108— BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:108-122 | firefox-ios/Client/Application/WebServer.swift:146-162 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingButton.swift:103— BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingButton.swift:103-117 | BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingButton.swift:126-140 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/WebContextMenuActionsProvider.swift:63— firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/WebContextMenuActionsProvider.swift:63-77 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/WebContextMenuActionsProvider.swift:79-100 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) focus-ios/Blockzilla/Extensions/URLExtensions.swift:128— focus-ios/Blockzilla/Extensions/URLExtensions.swift:128-142 | focus-ios/Blockzilla/Extensions/URLExtensions.swift:144-158 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:920— firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:920-934 | firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:943-964 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1334— firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1334-1348 | firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1350-1366 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Browser/TabPrintPageRenderer.swift:43— firefox-ios/Client/Frontend/Browser/TabPrintPageRenderer.swift:43-58 | firefox-ios/Client/Frontend/Browser/TabPrintPageRenderer.swift:60-74 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsViewController.swift:80— firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsViewController.swift:80-97 | firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:146-160 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Action/RemoteTabsPanelAction.swift:21— firefox-ios/Client/Frontend/Browser/Tabs/Action/RemoteTabsPanelAction.swift:21-35 | firefox-ios/Client/Frontend/Settings/Translation/TranslationSettingsAction.swift:44-58 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:100— firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:100-115 | firefox-ios/Client/Frontend/TrackingProtection/TrackingDetailsHelpers/BlockedTrackersLearnMoreViewController.swift:65-79 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1105— firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1105-1119 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:277-293 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1546— firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1546-1560 | firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1562-1577 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Privacy/AutofillCreditCardSettings.swift:20— firefox-ios/Client/Frontend/Settings/Main/Privacy/AutofillCreditCardSettings.swift:20-34 | firefox-ios/Client/Frontend/Settings/Main/Privacy/AutofillRelayMaskSetting.swift:18-32 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Components/StatusBarOverlay.swift:88— firefox-ios/Client/Frontend/Components/StatusBarOverlay.swift:88-104 | firefox-ios/Client/Frontend/Components/StatusBarOverlay.swift:106-120 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewModel.swift:18— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewModel.swift:18-34 | BrowserKit/Sources/WebEngine/WKWebview/Scripts/AdsTelemetryContentScript.swift:19-33 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1113— firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1113-1127 | firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1129-1143 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Account/AccountStatusSetting.swift:16— firefox-ios/Client/Frontend/Settings/Main/Account/AccountStatusSetting.swift:16-30 | firefox-ios/Client/Frontend/Settings/Main/Account/SyncNowSetting.swift:24-38 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (15 corresponding lines) firefox-ios/Client/TabManagement/Document/TemporaryDocument.swift:63— firefox-ios/Client/TabManagement/Document/TemporaryDocument.swift:63-81 | firefox-ios/Client/TabManagement/Document/TemporaryDocument.swift:301-315 — These two members are one piece of code written twice and then edited apart: 15 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (8 corresponding lines) · ×22
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Frontend/Browser/DownloadHelper/DownloadHelper.swift:16— firefox-ios/Client/Frontend/Browser/DownloadHelper/DownloadHelper.swift:16-23 | firefox-ios/Client/Frontend/TabContentsScripts/DownloadContentScript.swift:37-48 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Coordinators/Router/RouteBuilder.swift:176— firefox-ios/Client/Coordinators/Router/RouteBuilder.swift:176-183 | firefox-ios/Client/Coordinators/Router/RouteBuilder.swift:185-193 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Frontend/Onboarding/OnboardingCardView.swift:192— firefox-ios/Client/Frontend/Onboarding/OnboardingCardView.swift:192-201 | firefox-ios/Client/Frontend/Onboarding/OnboardingCardView.swift:203-210 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Application/RemoteSettings/Application Services/ASAIRemoteConfig.swift:67— firefox-ios/Client/Application/RemoteSettings/Application Services/ASAIRemoteConfig.swift:67-74 | firefox-ios/Client/VPN/VPNServerManager.swift:108-115 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:193— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:193-200 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:217-225 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:317— firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:317-324 | firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:326-334 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Debug/FeatureFlags/FeatureFlagsBoolSetting.swift:8— firefox-ios/Client/Frontend/Settings/Main/Debug/FeatureFlags/FeatureFlagsBoolSetting.swift:8-15 | firefox-ios/Client/Frontend/Settings/SettingsTableViewController.swift:420-431 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Frontend/Reader/ReaderMode.swift:83— firefox-ios/Client/Frontend/Reader/ReaderMode.swift:83-91 | BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReaderModeContentScript.swift:54-61 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Application/AppDelegate+SyncSentTabs.swift:30— firefox-ios/Client/Application/AppDelegate+SyncSentTabs.swift:30-40 | firefox-ios/Client/Utils/BackgroundTabLoader.swift:63-70 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) BrowserKit/Sources/ComponentLibrary/CollapsibleCardView.swift:66— BrowserKit/Sources/ComponentLibrary/CollapsibleCardView.swift:66-73 | firefox-ios/Client/Frontend/Components/ExpandButtonState.swift:12-21 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/WKEngineWebView.swift:338— BrowserKit/Sources/WebEngine/WKWebview/WKEngineWebView.swift:338-346 | firefox-ios/Client/TabManagement/TabWebView.swift:178-185 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:81— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:81-89 | BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift:101-108 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/WKEngineWebView.swift:348— BrowserKit/Sources/WebEngine/WKWebview/WKEngineWebView.swift:348-356 | firefox-ios/Client/TabManagement/TabWebView.swift:187-194 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Frontend/Settings/AutoFillPasswordSettingsViewController.swift:13— firefox-ios/Client/Frontend/Settings/AutoFillPasswordSettingsViewController.swift:13-20 | firefox-ios/Client/Frontend/Settings/BrowsingSettingsViewController.swift:25-32 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:974— firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:974-981 | firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel+Search.swift:18-28 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Frontend/PasswordManagement/DevicePasscodeRequiredViewController.swift:98— firefox-ios/Client/Frontend/PasswordManagement/DevicePasscodeRequiredViewController.swift:98-105 | firefox-ios/Client/Frontend/PasswordManagement/PasswordManagerOnboardingViewController.swift:184-192 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) focus-ios/Blockzilla/Modules/WebView/LegacyWebViewController.swift:320— focus-ios/Blockzilla/Modules/WebView/LegacyWebViewController.swift:320-327 | focus-ios/BlockzillaPackage/Sources/UIHelpers/ImageLoader.swift:57-64 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Coordinators/Router/Route.swift:90— firefox-ios/Client/Coordinators/Router/Route.swift:90-98 | firefox-ios/Client/Frontend/Library/LibraryPanelHelper.swift:93-100 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift:102— firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift:102-109 | firefox-ios/Client/Frontend/Settings/Translation/TranslationPickerSettingsViewController.swift:140-147 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatLearnMoreFooterView.swift:74— BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatLearnMoreFooterView.swift:74-82 | firefox-ios/Client/Frontend/Home/Homepage/PrivacyNotice/PrivacyNoticeCell.swift:137-144 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksCell.swift:38— firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksCell.swift:38-45 | firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/JumpBackInCell.swift:65-72 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (8 corresponding lines) firefox-ios/Client/Extensions/UITraitCollection+Extension.swift:15— firefox-ios/Client/Extensions/UITraitCollection+Extension.swift:15-22 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:275-282 — These two members are one piece of code written twice and then edited apart: 8 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (18 corresponding lines) · ×21
Edited copy of a member (18 corresponding lines) BrowserKit/Sources/MenuKit/MenuAccountCell.swift:122— BrowserKit/Sources/MenuKit/MenuAccountCell.swift:122-141 | BrowserKit/Sources/MenuKit/MenuCell.swift:103-120 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:128— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:128-145 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:156-180 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) focus-ios/Blockzilla/BrowserViewController.swift:1311— focus-ios/Blockzilla/BrowserViewController.swift:1311-1328 | focus-ios/Blockzilla/BrowserViewController.swift:1635-1652 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkDiffableDataSource.swift:24— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkDiffableDataSource.swift:24-41 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkDiffableDataSource.swift:25-42 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:671— firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:671-695 | firefox-ios/Client/Frontend/Library/Reader/ReaderPanel.swift:499-516 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) focus-ios/Blockzilla/Siri/SiriShortcuts.swift:60— focus-ios/Blockzilla/Siri/SiriShortcuts.swift:60-77 | focus-ios/Blockzilla/Siri/SiriShortcuts.swift:101-120 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Translations/SchemeHandler/ModelsBufferRoute.swift:18— firefox-ios/Client/Frontend/Translations/SchemeHandler/ModelsBufferRoute.swift:18-35 | firefox-ios/Client/Frontend/Translations/SchemeHandler/ModelsRoute.swift:15-35 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:285— firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:285-304 | focus-ios/Blockzilla/Search/SearchEngine.swift:140-157 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift:1051— firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift:1051-1068 | firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift:1070-1087 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Browser/TermsOfUse/View/TermsOfUseLinkViewController.swift:110— firefox-ios/Client/Frontend/Browser/TermsOfUse/View/TermsOfUseLinkViewController.swift:110-127 | firefox-ios/Client/Frontend/Browser/Toolbars/AddressToolbarContainer.swift:799-816 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Home/UnifiedAds/UnifiedAdsCallbackTelemetry.swift:40— firefox-ios/Client/Frontend/Home/UnifiedAds/UnifiedAdsCallbackTelemetry.swift:40-57 | firefox-ios/Client/Frontend/Home/UnifiedAds/UnifiedAdsCallbackTelemetry.swift:60-77 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:305— firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:305-322 | firefox-ios/Client/Coordinators/TabTray/RemoteTabsCoordinator.swift:34-51 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Storage/Rust/RustLogins.swift:40— firefox-ios/Storage/Rust/RustLogins.swift:40-63 | firefox-ios/Storage/Rust/RustLogins.swift:122-139 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:469— firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:469-486 | firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:488-505 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) focus-ios/Blockzilla/Settings/Controller/SettingsContentViewController.swift:21— focus-ios/Blockzilla/Settings/Controller/SettingsContentViewController.swift:21-38 | focus-ios/Blockzilla/Settings/Controller/SettingsContentViewController.swift:42-60 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/CertificatesHelpers/CertificatesFetcher.swift:91— firefox-ios/Client/Frontend/TrackingProtection/CertificatesHelpers/CertificatesFetcher.swift:91-108 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift:201-219 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/ContentBlocker/ContentBlocker.swift:352— firefox-ios/Client/ContentBlocker/ContentBlocker.swift:352-370 | focus-ios/Blockzilla/Utilities/LocalContentBlocker.swift:93-110 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSitesSectionState.swift:112— firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSitesSectionState.swift:112-129 | firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSitesSectionState.swift:131-148 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/General/QuickAnswersSetting.swift:31— firefox-ios/Client/Frontend/Settings/Main/General/QuickAnswersSetting.swift:31-48 | firefox-ios/Client/Frontend/Settings/Main/Privacy/VPNSetting.swift:37-55 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) BrowserKit/Sources/SiteImageView/HeroImageViewModel.swift:28— BrowserKit/Sources/SiteImageView/HeroImageViewModel.swift:28-45 | firefox-ios/Client/Frontend/Home/HomepageHeroImageViewModel.swift:18-36 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (18 corresponding lines) BrowserKit/Sources/ComponentLibrary/Buttons/PrimaryRoundedButton.swift:85— BrowserKit/Sources/ComponentLibrary/Buttons/PrimaryRoundedButton.swift:85-108 | BrowserKit/Sources/ComponentLibrary/Buttons/SecondaryRoundedButton.swift:91-108 — These two members are one piece of code written twice and then edited apart: 18 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (14 corresponding lines) · ×21
Edited copy of a member (14 corresponding lines) firefox-ios/CredentialProvider/Cells/EmptyPlaceholderCell.swift:25— firefox-ios/CredentialProvider/Cells/EmptyPlaceholderCell.swift:25-38 | firefox-ios/CredentialProvider/Cells/NoSearchResultCell.swift:24-37 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/AuthenticationManager/SensitiveViewController.swift:103— firefox-ios/Client/Frontend/AuthenticationManager/SensitiveViewController.swift:103-116 | firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheet.swift:243-257 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:274— firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:274-289 | firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataSearchResultsViewController.swift:145-158 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/WebContextMenuActionsProvider.swift:33— firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/WebContextMenuActionsProvider.swift:33-46 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/WebContextMenuActionsProvider.swift:48-61 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Coordinators/Launch/LaunchCoordinator.swift:151— firefox-ios/Client/Coordinators/Launch/LaunchCoordinator.swift:151-165 | firefox-ios/Client/Frontend/Onboarding/Views/PrivacyPreferencesViewController.swift:245-258 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/Browser/SearchLoader.swift:183— firefox-ios/Client/Frontend/Browser/SearchLoader.swift:183-196 | focus-ios/Blockzilla/Lib/DomainCompletion/DomainCompletion.swift:153-170 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Storage/Rust/RustRemoteTabs.swift:74— firefox-ios/Storage/Rust/RustRemoteTabs.swift:74-87 | firefox-ios/Storage/Rust/RustRemoteTabs.swift:89-117 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) BrowserKit/Sources/Common/Theming/NovaFaviconColorSet.swift:65— BrowserKit/Sources/Common/Theming/NovaFaviconColorSet.swift:65-78 | BrowserKit/Sources/Common/Theming/StandardFaviconColorSet.swift:65-78 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardItemRow.swift:114— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardItemRow.swift:114-129 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardItemRow.swift:131-144 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Policy/HTTPSchemePolicyDecider.swift:33— BrowserKit/Sources/WebEngine/WKWebview/Policy/HTTPSchemePolicyDecider.swift:33-46 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:1655-1669 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Storage/Rust/RustAutofill.swift:247— firefox-ios/Storage/Rust/RustAutofill.swift:247-260 | firefox-ios/Storage/Rust/RustAutofill.swift:268-281 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) SampleComponentLibraryApp/SampleComponentLibraryApp/RootViewController.swift:45— SampleComponentLibraryApp/SampleComponentLibraryApp/RootViewController.swift:45-58 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardTableViewController.swift:106-121 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/Browser/BackForwardListViewController.swift:80— firefox-ios/Client/Frontend/Browser/BackForwardListViewController.swift:80-94 | firefox-ios/Client/Frontend/Browser/TopTabsViewController.swift:117-130 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/InternalSchemeHandler/AboutHomeHandler.swift:9— firefox-ios/Client/Frontend/InternalSchemeHandler/AboutHomeHandler.swift:9-22 | firefox-ios/Client/Frontend/InternalSchemeHandler/ErrorPageHelper.swift:206-220 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:404— firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:404-419 | firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:442-455 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewModel.swift:67— firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewModel.swift:67-80 | firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewModel.swift:82-95 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/General/HomeSetting.swift:27— firefox-ios/Client/Frontend/Settings/Main/General/HomeSetting.swift:27-40 | firefox-ios/Client/Frontend/Settings/Main/General/NewTabPageSetting.swift:27-40 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarUXConfiguration.swift:18— BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarUXConfiguration.swift:18-31 | BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarUXConfiguration.swift:33-47 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) BrowserKit/Sources/Shared/Deferred/Deferred.swift:73— BrowserKit/Sources/Shared/Deferred/Deferred.swift:73-88 | focus-ios/Deferred/Deferred.swift:70-83 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) firefox-ios/Client/TabManagement/TabManagerImplementation.swift:1324— firefox-ios/Client/TabManagement/TabManagerImplementation.swift:1324-1337 | firefox-ios/Client/TabManagement/TabManagerImplementation.swift:1339-1352 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (14 corresponding lines) taskcluster/ffios_taskgraph/transforms/github_release.py:11— taskcluster/ffios_taskgraph/transforms/github_release.py:11-28 | taskcluster/ffios_taskgraph/transforms/mark_as_shipped.py:12-25 — These two members are one piece of code written twice and then edited apart: 14 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (11 corresponding lines) · ×20
Edited copy of a member (11 corresponding lines) firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:89— firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:89-104 | focus-ios/Blockzilla/UIComponents/GradientProgressBar.swift:89-99 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKUserScriptManager.swift:72— BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKUserScriptManager.swift:72-82 | BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKUserScriptManager.swift:96-108 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Providers/Profile.swift:193— firefox-ios/Providers/Profile.swift:193-203 | firefox-ios/Providers/Profile.swift:205-217 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Client/Frontend/Onboarding/Models/OnboardingTelemetryUtility.swift:33— firefox-ios/Client/Frontend/Onboarding/Models/OnboardingTelemetryUtility.swift:33-44 | firefox-ios/Client/Frontend/Onboarding/Models/OnboardingTelemetryUtility.swift:96-106 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) BrowserKit/Sources/Shared/Deferred/Deferred.swift:61— BrowserKit/Sources/Shared/Deferred/Deferred.swift:61-71 | focus-ios/Deferred/Deferred.swift:56-66 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:87— firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:87-99 | firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTraySelectorView.swift:264-274 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:387— firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:387-399 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:401-411 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) BrowserKit/Sources/UnifiedSearchKit/SearchEngineTableView.swift:39— BrowserKit/Sources/UnifiedSearchKit/SearchEngineTableView.swift:39-49 | firefox-ios/CredentialProvider/CredentialListViewController.swift:140-151 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Storage/Rust/RustAutofill.swift:650— firefox-ios/Storage/Rust/RustAutofill.swift:650-660 | firefox-ios/Storage/Rust/RustLogins.swift:794-804 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Models/AddressToolbarContainerModel.swift:350— firefox-ios/Client/Frontend/Browser/Toolbars/Models/AddressToolbarContainerModel.swift:350-361 | firefox-ios/Client/Frontend/Browser/Toolbars/Models/NavigationToolbarContainerModel.swift:73-83 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Extensions/ShareTo/InitialViewController.swift:119— firefox-ios/Extensions/ShareTo/InitialViewController.swift:119-129 | focus-ios/OpenInFocus/ActionViewController.swift:136-148 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/WidgetKit/OpenTabs/OpenTabsWidget.swift:86— firefox-ios/WidgetKit/OpenTabs/OpenTabsWidget.swift:86-101 | firefox-ios/WidgetKit/OpenTabs/OpenTabsWidget.swift:133-143 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetViewModel.swift:52— firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetViewModel.swift:52-62 | firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetViewModel.swift:64-75 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/WebContextMenuActionsProvider.swift:128— firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/WebContextMenuActionsProvider.swift:128-139 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/WebContextMenuActionsProvider.swift:269-279 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) BrowserKit/Sources/ComponentLibrary/ActionButtonViewModel.swift:21— BrowserKit/Sources/ComponentLibrary/ActionButtonViewModel.swift:21-31 | BrowserKit/Sources/ComponentLibrary/Buttons/ChipButtonViewModel.swift:22-34 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Storage/Sites/Site.swift:105— firefox-ios/Storage/Sites/Site.swift:105-117 | firefox-ios/Storage/Sites/Site.swift:120-130 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Client/Frontend/Settings/AppearanceSettings/StylingViewModifiers.swift:30— firefox-ios/Client/Frontend/Settings/AppearanceSettings/StylingViewModifiers.swift:30-40 | firefox-ios/Client/Frontend/Settings/AppearanceSettings/StylingViewModifiers.swift:84-97 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) focus-ios/Blockzilla/UIComponents/AutocompleteTextField.swift:160— focus-ios/Blockzilla/UIComponents/AutocompleteTextField.swift:160-170 | BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationTextField.swift:284-296 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/JumpBackInAction.swift:14— firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/JumpBackInAction.swift:14-24 | firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerModuleAction.swift:14-24 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (11 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionConnectionStatusView.swift:107— firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionConnectionStatusView.swift:107-117 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionToggleView.swift:134-144 — These two members are one piece of code written twice and then edited apart: 11 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (5 corresponding lines) · ×19
Edited copy of a member (5 corresponding lines) firefox-ios/Storage/SQL/BrowserDB.swift:94— firefox-ios/Storage/SQL/BrowserDB.swift:94-98 | firefox-ios/Storage/SQL/BrowserDB.swift:100-108 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) firefox-ios/Client/Telemetry/HomepageTelemetry.swift:87— firefox-ios/Client/Telemetry/HomepageTelemetry.swift:87-97 | firefox-ios/Client/Telemetry/HomepageTelemetry.swift:114-118 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:80— firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:80-84 | firefox-ios/Client/TabManagement/TabManagerDelegate.swift:61-66 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:365— firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:365-369 | firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataSearchResultsViewController.swift:103-107 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:225— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:225-229 | firefox-ios/Client/Frontend/Settings/Translation/TranslationPickerSettingsViewController.swift:433-437 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/About/LicenseAndAcknowledgementsSetting.swift:30— firefox-ios/Client/Frontend/Settings/Main/About/LicenseAndAcknowledgementsSetting.swift:30-34 | firefox-ios/Client/Frontend/Settings/Main/About/YourRightsSetting.swift:29-34 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/About/AppStoreReviewSetting.swift:9— firefox-ios/Client/Frontend/Settings/Main/About/AppStoreReviewSetting.swift:9-13 | firefox-ios/Client/Frontend/Settings/Main/Account/ConnectSetting.swift:18-22 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersHelpers/BlockedTrackerCell.swift:94— firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersHelpers/BlockedTrackerCell.swift:94-99 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionConnectionStatusView.swift:135-139 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) BrowserKit/Sources/Shared/Deferred/LockProtected.swift:31— BrowserKit/Sources/Shared/Deferred/LockProtected.swift:31-35 | focus-ios/Deferred/LockProtected.swift:26-30 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:539— firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:539-544 | firefox-ios/Client/Frontend/Browser/TabScrollController/TabScrollHandler.swift:332-336 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) BrowserKit/Sources/Shared/Deferred/LockProtected.swift:25— BrowserKit/Sources/Shared/Deferred/LockProtected.swift:25-29 | focus-ios/Deferred/LockProtected.swift:20-24 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) firefox-ios/Client/Frontend/Settings/FirefoxSuggestSettingsViewController.swift:13— firefox-ios/Client/Frontend/Settings/FirefoxSuggestSettingsViewController.swift:13-17 | firefox-ios/Client/Frontend/Settings/Main/Debug/FeatureFlags/FeatureFlagsDebugViewController.swift:11-15 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReaderModeContentScript.swift:48— BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReaderModeContentScript.swift:48-52 | firefox-ios/Client/Frontend/Reader/ReaderMode.swift:76-81 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) focus-ios/Blockzilla/Menu/Protocol/MenuItemProvider.swift:99— focus-ios/Blockzilla/Menu/Protocol/MenuItemProvider.swift:99-103 | focus-ios/Blockzilla/Menu/Protocol/WebMenuAction.swift:15-19 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) focus-ios/Blockzilla/Settings/Controller/SettingsViewController.swift:254— focus-ios/Blockzilla/Settings/Controller/SettingsViewController.swift:254-260 | focus-ios/Blockzilla/Theme/ThemeViewController.swift:75-79 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) focus-ios/Blockzilla/Menu/Protocol/MenuItemProvider.swift:111— focus-ios/Blockzilla/Menu/Protocol/MenuItemProvider.swift:111-115 | focus-ios/Blockzilla/Menu/Protocol/WebMenuAction.swift:27-31 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/SearchBar/SearchBarCell.swift:85— firefox-ios/Client/Frontend/Home/Homepage/SearchBar/SearchBarCell.swift:85-92 | firefox-ios/Client/Frontend/StoriesFeed/StoryCell.swift:72-76 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) firefox-ios/Client/Frontend/Settings/SettingsContentViewController.swift:227— firefox-ios/Client/Frontend/Settings/SettingsContentViewController.swift:227-231 | focus-ios/Blockzilla/Settings/Controller/SettingsContentViewController.swift:172-176 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (5 corresponding lines) BrowserKit/Sources/QuickAnswersKit/UI/QuickAnswersSourceView.swift:261— BrowserKit/Sources/QuickAnswersKit/UI/QuickAnswersSourceView.swift:261-265 | BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:65-69 — These two members are one piece of code written twice and then edited apart: 5 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Change coupling: ContextualHintCopyProvider.swift ↔ ContextualHintEligibilityUtility.swift firefox-ios/Client/Frontend/ContextualHint/ContextualHintCopyProvider.swift:1— `firefox-ios/Client/Frontend/ContextualHint/ContextualHintCopyProvider.swift` and `firefox-ios/Client/Frontend/ContextualHint/ContextualHintEligibilityUtility.swift` change together 90% of the time (9 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `1a08ef87` Add FXIOS-16888 Remove Translation Contextual Hint (#35774); `f828a9ae` Refactor FXIOS-15635 [Toolbar] Remove toolbar update CFR and feature …; `6c594914` Add FXIOS-13624 [Relay] Email mask contextual hint (#30822) — run `git show` on any of them.
Change coupling: AddressToolbarContainerModel.swift ↔ NavigationToolbarContainerModel.swift firefox-ios/Client/Frontend/Browser/Toolbars/Models/AddressToolbarContainerModel.swift:1— `firefox-ios/Client/Frontend/Browser/Toolbars/Models/AddressToolbarContainerModel.swift` and `firefox-ios/Client/Frontend/Browser/Toolbars/Models/NavigationToolbarContainerModel.swift` change together 82% of the time (18 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 18 shared commits counted here, the most recent 3 are `c449bb45` Bugfix FXIOS-17209 [iPhone Duo] Long press on Tabs button in regular …; `0e7606da` Refactor FXIOS-13944 [Swift 6] Isolate new state and subsequently a l…; `ccbd3230` Refactor FXIOS-13953 [Swift 6 migration] Toolbar dispatch legacy (#30… — run `git show` on any of them.
Change coupling: AddressToolbarDelegate.swift ↔ LocationView.swift BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarDelegate.swift:1— `BrowserKit/Sources/ToolbarKit/AddressToolbar/AddressToolbarDelegate.swift` and `BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationView.swift` change together 82% of the time (9 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `e7b73956` Bugfix FXIOS-17170 [Google Lens] Hide google lens tooltip once addres…; `195fdfbb` Bugfix FXIOS-10229 After a user starts typing on the address bar, the…; `8adf1cee` Refactor FXIOS-10202 Implement UIDragInteractionDelegate for location… — run `git show` on any of them.
Change coupling: FeatureFlagsDebugViewController.swift ↔ NimbusFeatureFlagLayer.swift firefox-ios/Client/Frontend/Settings/Main/Debug/FeatureFlags/FeatureFlagsDebugViewController.swift:1— `firefox-ios/Client/Frontend/Settings/Main/Debug/FeatureFlags/FeatureFlagsDebugViewController.swift` and `firefox-ios/Client/Nimbus/NimbusFeatureFlagLayer.swift` change together 75% of the time (101 of the 135 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 101 shared commits counted here, the most recent 3 are `87dfc013` Add FXIOS-17066 [Tab Groups] Disabled feature flag (#36062); `0c5ffef5` Add FXIOS-17175 [ReiOS] Feature flag (#36193); `b22f6eff` Add FXIOS-17199 [Quick Answers] Follow-up conversation history (#36244) — run `git show` on any of them.
Change coupling: LocationTextField.swift ↔ LocationViewDelegate.swift BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationTextField.swift:1— `BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationTextField.swift` and `BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationViewDelegate.swift` change together 73% of the time (8 of the 11 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `e7b73956` Bugfix FXIOS-17170 [Google Lens] Hide google lens tooltip once addres…; `df582d22` Add FXIOS-16300 [Google Lens] Tooltip (#35060); `a89517f9` Bugfix FXIOS-13233 #28786 [Swift 6 Migration] Fix warnings under tool… — run `git show` on any of them.
Change coupling: OnboardingBasicCardView.swift ↔ OnboardingSegmentedControl.swift BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:1— `BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift` and `BrowserKit/Sources/OnboardingKit/Views/Shared/OnboardingSegmentedControl.swift` change together 64% of the time (9 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `af83b999` Add FXIOS-13873 Bring ThemeableView inside common (#30110) (at that commit the files were still `BrowserKit/Sources/OnboardingKit/Views/Compact/OnboardingBasicCardViewCompact.swift` and `BrowserKit/Sources/OnboardingKit/Views/Helper/OnboardingSegmentedControl.swift`); `ed7e927e` Refactor [Onboarding] Layout and scroll issue. (#30051) (at that commit the files were still `BrowserKit/Sources/OnboardingKit/Views/Compact/OnboardingBasicCardViewCompact.swift` and `BrowserKit/Sources/OnboardingKit/Views/Helper/OnboardingSegmentedControl.swift`); `fbf2c942` Bugfix FXIOS-13712 [iOS 26] [New first run onboarding] Fix accessibil… (at that commit the files were still `BrowserKit/Sources/OnboardingKit/Views/Compact/OnboardingBasicCardViewCompact.swift` and `BrowserKit/Sources/OnboardingKit/Views/Helper/OnboardingSegmentedControl.swift`) — run `git show` on any of them.
Change coupling: BrowserViewController+ToolBarActionMenuDelegate.swift ↔ ContextualHintCopyProvider.swift firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+ToolBarActionMenuDelegate.swift:1— `firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+ToolBarActionMenuDelegate.swift` and `firefox-ios/Client/Frontend/ContextualHint/ContextualHintCopyProvider.swift` change together 60% of the time (6 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `1a08ef87` Add FXIOS-16888 Remove Translation Contextual Hint (#35774); `f828a9ae` Refactor FXIOS-15635 [Toolbar] Remove toolbar update CFR and feature …; `ca4413d1` Add FXIOS-13966 [Translations] initial CFR for translation icon (#30397) (at that commit the file was still `firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+TabToolbarDelegate.swift`) — run `git show` on any of them.
Change coupling: NavigationToolbarContainerModel.swift ↔ ToolbarMiddleware.swift firefox-ios/Client/Frontend/Browser/Toolbars/Models/NavigationToolbarContainerModel.swift:1— `firefox-ios/Client/Frontend/Browser/Toolbars/Models/NavigationToolbarContainerModel.swift` and `firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarMiddleware.swift` change together 59% of the time (13 of the 22 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `140ffdc0` [Add] FXIOS-12063 [Toolbars] Toolbar Translucency (#26514); `086918aa` Bugfix FXIOS-9836 [Toolbar redesign] Tab tray context menu is not ava…; `89cad7e4` Add FXIOS-9713 Data clearance CFR for toolbar refactor (#21622) — run `git show` on any of them.
Change coupling: AddressBarState.swift ↔ NavigationBarState.swift firefox-ios/Client/Frontend/Browser/Toolbars/Redux/AddressBarState.swift:1— `firefox-ios/Client/Frontend/Browser/Toolbars/Redux/AddressBarState.swift` and `firefox-ios/Client/Frontend/Browser/Toolbars/Redux/NavigationBarState.swift` change together 58% of the time (11 of the 19 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 11 shared commits counted here, the most recent 3 are `08f36f6d` Refactor [ToolbarAction refactor] FXIOS-16630 action states for navig…; `72355db2` Bugfix FXIOS-16430 [Nova] Update Private Mode homepage icons (#35278); `aaf39885` Revert NO-TICKET 150.2/150.3 CopyWithUpdates Changes (#33475) — run `git show` on any of them.
Change coupling: MainMenuMiddleware.swift ↔ MainMenuState.swift firefox-ios/Client/Frontend/Browser/MainMenu/Redux/MainMenuMiddleware.swift:1— `firefox-ios/Client/Frontend/Browser/MainMenu/Redux/MainMenuMiddleware.swift` and `firefox-ios/Client/Frontend/Browser/MainMenu/Redux/MainMenuState.swift` change together 54% of the time (13 of the 24 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 13 shared commits counted here, the most recent 3 are `f817b76b` Add FXIOS-15161 #32641 [Translations Phase 2] Add Translate Page to …; `57edb6e0` Add [Summarizer] FXIOS-15076 Reader View item to Main menu (#32474); `9bae6825` Bugfix FXIOS-13404 ⁃ On slow network connections, the app menu takes … — run `git show` on any of them.
Change coupling: HomepageDiffableDataSource.swift ↔ HomepageSectionLayoutProvider.swift firefox-ios/Client/Frontend/Home/Homepage/HomepageDiffableDataSource.swift:1— `firefox-ios/Client/Frontend/Home/Homepage/HomepageDiffableDataSource.swift` and `firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift` change together 53% of the time (39 of the 73 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 39 shared commits counted here, the most recent 3 are `02e9f15c` Add FXIOS-16830 [Onboarding] Create notifications homescreen popup (#…; `4872b1ff` Refactor FXIOS-16139 [Redux Passthrough] update homepagestate (#35314); `9aef14c1` Refactor FXIOS-16139 [Redux Passthrough] shouldShowPrivacyNotice (#35… — run `git show` on any of them.
Change coupling: BookmarksSectionState.swift ↔ HomePageSettingViewController.swift firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksSectionState.swift:1— `firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksSectionState.swift` and `firefox-ios/Client/Frontend/Settings/HomepageSettings/HomePageSettingViewController.swift` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `fc186544` Refactor FXIOS-15508 [FeatureFlags] Update feature flag user settings…; `24bd7607` Refactor FXIOS-15504 [FeatureFlags] migrate homepageBookmarksSectionD…; `95f9e8e6` Add FXIOS-14678 [Homepage Redesign] Feature flag for toggling bookmar… — run `git show` on any of them.
Change coupling: BookmarksSectionState.swift ↔ JumpBackInSectionState.swift firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksSectionState.swift:1— `firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksSectionState.swift` and `firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/JumpBackInSectionState.swift` change together 53% of the time (8 of the 15 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 8 shared commits counted here, the most recent 3 are `ebd22c97` Refactor FXIOS-14968 [Homepage] Move section header configuration out…; `be3c94aa` Refactor FXIOS-15901 [Technical Debt] [Redux] Migrate Redux header st…; `fc186544` Refactor FXIOS-15508 [FeatureFlags] Update feature flag user settings… — run `git show` on any of them.
Change coupling: BrowserNavigationHandler.swift ↔ NavigationBrowserAction.swift firefox-ios/Client/Coordinators/Browser/BrowserNavigationHandler.swift:1— `firefox-ios/Client/Coordinators/Browser/BrowserNavigationHandler.swift` and `firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/NavigationBrowserAction.swift` change together 50% of the time (9 of the 18 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 9 shared commits counted here, the most recent 3 are `be6451eb` Add [Quick Answers] FXIOS-14861 Homepage quick answers button (#33231); `3e0a361b` Add FXIOS-14595 [New Error Pages] Certificate modal implementation (#…; `9faa9ec0` Add FXIOS-14435 [Terms of Use] Display links from Privacy Notice moda… — run `git show` on any of them.
Change coupling: PasswordGeneratorMiddleware.swift ↔ PasswordGeneratorViewController.swift firefox-ios/Client/Frontend/PasswordGenerator/PasswordGeneratorMiddleware.swift:1— `firefox-ios/Client/Frontend/PasswordGenerator/PasswordGeneratorMiddleware.swift` and `firefox-ios/Client/Frontend/PasswordGenerator/PasswordGeneratorViewController.swift` change together 50% of the time (7 of the 14 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 7 shared commits counted here, the most recent 3 are `dae53d5b` Refactor FXIOS-14456 #31308 ⁃ Fix test failing on XCode 26.2 to enabl…; `4d19dac2` Bugfix FXIOS-10560 - Password Generator: Keyboard Closing After Acces…; `957f853e` Refactor 10279 - Password Generator: Tie Stored passwords to iframe o… — run `git show` on any of them.
Change coupling: WebCompatReportViewModel.swift ↔ WebCompatReporterUX.swift BrowserKit/Sources/WebCompatReporterKit/WebCompatReportViewModel.swift:1— `BrowserKit/Sources/WebCompatReporterKit/WebCompatReportViewModel.swift` and `BrowserKit/Sources/WebCompatReporterKit/WebCompatReporterUX.swift` change together 50% of the time (6 of the 12 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 6 shared commits counted here, the most recent 3 are `3a8e546b` Bugfix FXIOS-16487 [WebCompat] Show an error for an invalid URL (#35262); `7d79fd43` Bugfix FXIOS-16484 [WebCompat] Use a checkbox for the Additional Info…; `cac6df98` Add FXIOS-16182 [WebCompat] Additional details field (#34862) — run `git show` on any of them.
Change coupling: OnboardingTelemetryUtility.swift ↔ TelemetryWrapper.swift firefox-ios/Client/Frontend/Onboarding/Models/OnboardingTelemetryUtility.swift:1— `firefox-ios/Client/Frontend/Onboarding/Models/OnboardingTelemetryUtility.swift` and `firefox-ios/Client/Telemetry/TelemetryWrapper.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in different directories, but in this ecosystem the namespace is declared in the FILE, not by the folder — so the two may well share one namespace and reference each other with no import for this pass to see. Read the pair before acting: if one derives from or overrides the other, the dependency is explicit in the type declaration and the co-change is definitional; if one registers itself into the other through a hook or an initialiser, the missing dependency is DELIBERATE and the thing to add is a comment saying so; if they simply belong together, co-locate them; if none of these holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `2edfad85` Remove FXIOS-16366 [Wallpapers] Remove unused Wallpaper v1 code (#34984); `7cdca45f` Add FXIOS-14577 Add a custom onboarding ping to better track user aba…; `7b2de5f8` Add FXIOS-14493 #31366 [Onboarding] No telemetry recorded when the u… — run `git show` on any of them.
Change coupling: TermsOfUseCoordinator.swift ↔ TermsOfUseMiddleware.swift firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseCoordinator.swift:1— `firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseCoordinator.swift` and `firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseMiddleware.swift` change together 50% of the time (5 of the 10 commits that touched whichever of the two files changed less often, counting a file under its earlier names as well, and counted over this repository's 10,000 most recent commits rather than its whole history — a repo-wide or module-wide sweep is evidence about the sweep rather than about any pair inside it and is left out of BOTH sides of this ratio, while a dependency bump, a formatter/rename sweep, or a commit whose edit to one of the two files was a tool directive such as //go:generate or whitespace only is left out of the shared count ONLY, so the two sides are not taken over identical commit sets). They sit in the same directory, and in this ecosystem sibling files there normally share one namespace/package — so a direct reference between them needs no import and this pass cannot see whether one exists. Read the pair before acting: if one file only DECLARES what the other consumes (a constants/types file beside its user), the co-change is definitional and the question is whether the split earns its keep; if they duplicate structure, extract the common part into a shared function or type they both call; if neither holds, the coupling is hidden and worth breaking. You can check this without leaving the row: of the 5 shared commits counted here, the most recent 3 are `25673ec5` Add FXIOS-12947 Add missing unit tests for ToU feature (#31180); `b3f932ef` Add FXIOS-13604 Configure the number of ToU bottom sheet reminders us…; `8593a080` Refactor FXIOS-13120 [Terms of Use] - Trigger ToU bottom sheet after … — run `git show` on any of them.
D4 · Code Duplication· Edited copy of a member (10 corresponding lines) · ×18
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEnginePrefsMigrator.swift:65— firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEnginePrefsMigrator.swift:65-75 | firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEnginePrefsMigrator.swift:77-86 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Telemetry/GleanUsageReporting.swift:51— firefox-ios/Client/Telemetry/GleanUsageReporting.swift:51-64 | focus-ios/Blockzilla/GleanUsageReportingMetricsService.swift:51-60 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:116— firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:116-125 | firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTraySelectorView.swift:221-230 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:143— firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:143-152 | focus-ios/Blockzilla/UIComponents/GradientProgressBar.swift:134-143 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:361— focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:361-374 | focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:376-385 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Telemetry/TabLossTelemetry.swift:36— firefox-ios/Client/Telemetry/TabLossTelemetry.swift:36-45 | firefox-ios/Client/Telemetry/TabLossTelemetry.swift:47-56 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Coordinators/LaunchView/LaunchScreenViewController.swift:52— firefox-ios/Client/Coordinators/LaunchView/LaunchScreenViewController.swift:52-66 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2289-2298 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) BrowserKit/Sources/OnboardingKit/Views/TermsOfUse/TermsOfUseView.swift:86— BrowserKit/Sources/OnboardingKit/Views/TermsOfUse/TermsOfUseView.swift:86-95 | BrowserKit/Sources/OnboardingKit/Views/TermsOfUse/TermsOfUseView.swift:172-182 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:283— firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:283-294 | firefox-ios/Client/Frontend/Settings/Translation/TranslationLanguagePickerViewController.swift:96-105 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Redux/BrowserActionsBuilder.swift:94— firefox-ios/Client/Frontend/Browser/Toolbars/Redux/BrowserActionsBuilder.swift:94-103 | firefox-ios/Client/Frontend/Browser/Toolbars/Redux/NavigationActionsBuilder.swift:108-117 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/FolderTreeCell.swift:75— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/FolderTreeCell.swift:75-84 | firefox-ios/Client/Frontend/Widgets/OneLineTableViewCell.swift:124-135 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/Browser/TopTabDisplayManager.swift:762— firefox-ios/Client/Frontend/Browser/TopTabDisplayManager.swift:762-771 | firefox-ios/WidgetKit/OpenTabs/SimpleTab.swift:34-43 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/Browser/Zoom/ZoomPageManager.swift:39— firefox-ios/Client/Frontend/Browser/Zoom/ZoomPageManager.swift:39-48 | firefox-ios/Client/Frontend/Browser/Zoom/ZoomPageManager.swift:50-59 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/Onboarding/Protocols/OnboardingService.swift:235— firefox-ios/Client/Frontend/Onboarding/Protocols/OnboardingService.swift:235-252 | firefox-ios/Client/Frontend/Onboarding/Protocols/OnboardingService.swift:267-276 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Nimbus.swift:53— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Nimbus.swift:53-63 | MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Nimbus.swift:52-61 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/PasswordGenerator/View/PasswordGeneratorPasswordFieldView.swift:58— firefox-ios/Client/Frontend/PasswordGenerator/View/PasswordGeneratorPasswordFieldView.swift:58-69 | firefox-ios/Client/Frontend/PasswordGenerator/View/PasswordGeneratorHeaderView.swift:47-56 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/Settings/QuickAnswers/QuickAnswersSettingsViewController.swift:83— firefox-ios/Client/Frontend/Settings/QuickAnswers/QuickAnswersSettingsViewController.swift:83-92 | firefox-ios/Client/Frontend/Settings/RelayMaskSettingsViewController.swift:82-92 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (10 corresponding lines) firefox-ios/Client/Frontend/Settings/TPAccessoryInfo.swift:150— firefox-ios/Client/Frontend/Settings/TPAccessoryInfo.swift:150-159 | firefox-ios/Client/Frontend/Theme/ThemedTableViewController.swift:62-71 — These two members are one piece of code written twice and then edited apart: 10 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (4 corresponding lines) · ×18
Edited copy of a member (4 corresponding lines) firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:133— firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:133-141 | focus-ios/Blockzilla/UIComponents/GradientProgressBar.swift:129-132 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) firefox-ios/WidgetKit/SearchQuickLinksMedium/SearchQuickLinks.swift:20— firefox-ios/WidgetKit/SearchQuickLinksMedium/SearchQuickLinks.swift:20-24 | focus-ios/Widgets/Widgets.swift:15-18 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Debug/MerinoTestDataSetting.swift:11— firefox-ios/Client/Frontend/Settings/Main/Debug/MerinoTestDataSetting.swift:11-14 | firefox-ios/Client/Frontend/Settings/Main/Debug/MockBreachAlertsSetting.swift:11-14 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:373— firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:373-376 | firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:841-844 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) firefox-ios/Client/Frontend/Settings/SettingsTableViewController.swift:37— firefox-ios/Client/Frontend/Settings/SettingsTableViewController.swift:37-40 | firefox-ios/Client/Frontend/Theme/ThemedTableViewController.swift:31-34 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/HardcodedNimbusFeatures.swift:30— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/HardcodedNimbusFeatures.swift:30-33 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/HardcodedNimbusFeatures.swift:30-33 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) BrowserKit/Sources/Shared/Deferred/Deferred.swift:22— BrowserKit/Sources/Shared/Deferred/Deferred.swift:22-25 | focus-ios/Deferred/Deferred.swift:17-20 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:51— BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:51-54 | firefox-ios/Client/Application/WebServer.swift:48-51 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) SampleComponentLibraryApp/SampleComponentLibraryApp/ContextualHintView/ContextualHintViewViewController.swift:91— SampleComponentLibraryApp/SampleComponentLibraryApp/ContextualHintView/ContextualHintViewViewController.swift:91-94 | firefox-ios/Client/Frontend/ContextualHint/ContextualHintViewController.swift:222-225 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) firefox-ios/WidgetKit/SearchQuickLinksMedium/SearchQuickLinks.swift:15— firefox-ios/WidgetKit/SearchQuickLinksMedium/SearchQuickLinks.swift:15-18 | focus-ios/Widgets/Widgets.swift:10-13 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:310— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:310-313 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift:310-313 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/TabDisplayPanelViewController.swift:232— firefox-ios/Client/Frontend/Browser/Tabs/Views/TabDisplayPanelViewController.swift:232-235 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:506-509 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) SampleBrowser/SampleBrowser/UI/Settings/SettingsViewController.swift:25— SampleBrowser/SampleBrowser/UI/Settings/SettingsViewController.swift:25-28 | SampleBrowser/SampleBrowser/UI/Suggestion/SuggestionViewController.swift:16-19 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) SampleBrowser/SampleBrowser/UI/Suggestion/SuggestionCellViewModel.swift:16— SampleBrowser/SampleBrowser/UI/Suggestion/SuggestionCellViewModel.swift:16-19 | SampleComponentLibraryApp/SampleComponentLibraryApp/Component/ComponentCell.swift:19-22 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSiteCell.swift:119— firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSiteCell.swift:119-122 | firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetView.swift:143-146 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetView.swift:138— firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetView.swift:138-141 | focus-ios/Blockzilla/SearchSuggestions/OverlayView.swift:501-504 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/General/HomeSetting.swift:20— firefox-ios/Client/Frontend/Settings/Main/General/HomeSetting.swift:20-23 | firefox-ios/Client/Frontend/Settings/Main/General/NewTabPageSetting.swift:20-23 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (4 corresponding lines) firefox-ios/Client/Frontend/Autofill/Address/Edit/EditAddressViewController.swift:253— firefox-ios/Client/Frontend/Autofill/Address/Edit/EditAddressViewController.swift:253-257 | firefox-ios/Client/Frontend/PasswordManagement/PasswordManagerListViewController.swift:495-498 — These two members are one piece of code written twice and then edited apart: 4 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (10 lines × 2) BrowserKit/Sources/SummarizeKit/UI/InfoViewFormatter.swift:33— BrowserKit/Sources/SummarizeKit/UI/InfoViewFormatter.swift:33-42 | BrowserKit/Sources/SummarizeKit/UI/SummaryFormatter.swift:64-73 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/SummarizeKit/UI/InfoViewFormatter.swift:33` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (10 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:23— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:23-32 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:23-32 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:99— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:99-108 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:99-108 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Sysctl.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:114— firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:114-123 | focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift:76-85 — before extracting anything, compare `firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift` and `focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 43 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift:87` calls `NSRegularExpression` and `firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:125` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) firefox-ios/Client/Frontend/Browser/PrivateModeButton.swift:9— firefox-ios/Client/Frontend/Browser/PrivateModeButton.swift:9-18 | firefox-ios/Client/Frontend/Widgets/PrivateModeButton.swift:9-18 — `firefox-ios/Client/Frontend/Browser/PrivateModeButton.swift` and `firefox-ios/Client/Frontend/Widgets/PrivateModeButton.swift` are one unit implemented once per sibling directory, so they are most likely parallel implementations of one contract rather than a copy of each other — this scan matched 1 separate duplicated blocks between them, totalling at least 10 lines. If both are selected at run time, neither can be retired in favour of the other, and the lines that DIFFER between them are the reason both exist. The move that pays here is to hoist the identical part into a shared location the whole family can reach and give what differs a parameter or a seam, so a change lands once instead of once per sibling; extracting one helper per block leaves every sibling to drift on its own.
Duplicated block (10 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/FolderTreeCell.swift:95— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/FolderTreeCell.swift:95-104 | firefox-ios/Client/Frontend/Widgets/OneLineTableViewCell.swift:153-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/FolderTreeCell.swift:95` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) firefox-ios/Client/Frontend/TabContentsScripts/LoginsHelper.swift:289— firefox-ios/Client/Frontend/TabContentsScripts/LoginsHelper.swift:289-298 | firefox-ios/Client/Frontend/TabContentsScripts/LoginsHelper.swift:333-342 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/TabContentsScripts/LoginsHelper.swift:289` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:434— focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:434-443 | focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:954-963 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:434` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (10 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:169— BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:169-178 | firefox-ios/Client/Application/WebServerUtil.swift:98-107 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:116— firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:116-125 | firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift:99-108 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift` and `firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:116` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:115` calls `setupPaddedButton` and `firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift:98` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 2) BrowserKit/Sources/ComponentLibrary/Buttons/CloseButton.swift:93— BrowserKit/Sources/ComponentLibrary/Buttons/CloseButton.swift:93-102 | BrowserKit/Sources/ComponentLibrary/ContextualHintView/ContextualHintView.swift:194-203 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (10 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/TabDisplayView.swift:96— firefox-ios/Client/Frontend/Browser/Tabs/Views/TabDisplayView.swift:96-105 | firefox-ios/Client/Frontend/Browser/TopTabDisplayManager.swift:116-125 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/JumpBackInCell.swift:180— firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/JumpBackInCell.swift:180-189 | firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/SyncedTabCell.swift:321-331 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:150— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:150-159 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:155-164 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 2) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewModel.swift:37— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewModel.swift:37-46 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSettingsViewModel.swift:43-52 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10 lines × 2) firefox-ios/Client/Frontend/Browser/ClipboardBarDisplayHandler.swift:80— firefox-ios/Client/Frontend/Browser/ClipboardBarDisplayHandler.swift:80-89 | firefox-ios/Client/Frontend/Browser/OpenWithSettingsViewController.swift:169-178 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (10 lines × 2) firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksSectionState.swift:61— firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksSectionState.swift:61-73 | firefox-ios/Client/Frontend/Home/Homepage/MessageCard/MessageCardState.swift:53-62 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
D4 · Code Duplication· Edited copy of a member (3 corresponding lines) · ×15
Edited copy of a member (3 corresponding lines) BrowserKit/Sources/Shared/Deferred/Deferred.swift:118— BrowserKit/Sources/Shared/Deferred/Deferred.swift:118-120 | focus-ios/Deferred/Deferred.swift:97-99 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) BrowserKit/Sources/Shared/Deferred/Deferred.swift:134— BrowserKit/Sources/Shared/Deferred/Deferred.swift:134-136 | focus-ios/Deferred/Deferred.swift:117-119 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:118— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:118-120 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:118-120 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:112— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:112-114 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:112-114 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) BrowserKit/Sources/Shared/Deferred/Deferred.swift:126— BrowserKit/Sources/Shared/Deferred/Deferred.swift:126-128 | focus-ios/Deferred/Deferred.swift:107-109 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift:34— BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift:34-36 | firefox-ios/Client/Frontend/InternalSchemeHandler/InternalSchemeHandler.swift:24-26 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:182— BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:182-184 | firefox-ios/Client/Application/WebServer.swift:166-168 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) firefox-ios/Client/TabManagement/TabManager.swift:165— firefox-ios/Client/TabManagement/TabManager.swift:165-167 | firefox-ios/Client/TabManagement/TabManagerImplementation.swift:1041-1048 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) BrowserKit/Sources/Shared/Deferred/Deferred.swift:130— BrowserKit/Sources/Shared/Deferred/Deferred.swift:130-132 | focus-ios/Deferred/Deferred.swift:111-113 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) firefox-ios/Client/Frontend/Settings/SiriSettingsViewController.swift:62— firefox-ios/Client/Frontend/Settings/SiriSettingsViewController.swift:62-68 | focus-ios/Blockzilla/Settings/Controller/SettingsViewController.swift:679-681 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:242— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureVariables.swift:242-244 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift:242-244 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) BrowserKit/Sources/Shared/Extensions/WKWebViewExtensions.swift:14— BrowserKit/Sources/Shared/Extensions/WKWebViewExtensions.swift:14-16 | BrowserKit/Sources/WebEngine/WKWebview/WKEngineWebView.swift:99-104 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Debug/PrivacyNoticeUpdate.swift:17— firefox-ios/Client/Frontend/Settings/Main/Debug/PrivacyNoticeUpdate.swift:17-19 | firefox-ios/Client/Frontend/Settings/Main/Debug/ResetTipsSetting.swift:34-37 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) firefox-ios/Client/Telemetry/SearchTelemetry.swift:188— firefox-ios/Client/Telemetry/SearchTelemetry.swift:188-190 | focus-ios/Blockzilla/Utilities/SearchInContentTelemetry.swift:33-35 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (3 corresponding lines) firefox-ios/Client/Telemetry/SearchTelemetry.swift:193— firefox-ios/Client/Telemetry/SearchTelemetry.swift:193-195 | focus-ios/Blockzilla/Utilities/SearchInContentTelemetry.swift:38-40 — These two members are one piece of code written twice and then edited apart: 3 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (17 corresponding lines) · ×14
Edited copy of a member (17 corresponding lines) BrowserKit/Sources/VPNKit/VPNAppAttestServer.swift:67— BrowserKit/Sources/VPNKit/VPNAppAttestServer.swift:67-88 | BrowserKit/Sources/VPNKit/VPNAppAttestServer.swift:91-107 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Client/Coordinators/CredentialAutofillCoordinator.swift:305— firefox-ios/Client/Coordinators/CredentialAutofillCoordinator.swift:305-321 | firefox-ios/Client/Coordinators/Library/LibraryCoordinator.swift:208-226 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:206— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:206-222 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:224-240 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserPrompts.swift:99— firefox-ios/Client/Frontend/Browser/BrowserPrompts.swift:99-115 | firefox-ios/Client/Frontend/Browser/BrowserPrompts.swift:139-163 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:924— firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:924-941 | firefox-ios/Client/Frontend/Library/LibraryViewController/LibraryViewController.swift:255-271 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) SampleBrowser/SampleBrowser/UI/Settings/SettingsViewController.swift:44— SampleBrowser/SampleBrowser/UI/Settings/SettingsViewController.swift:44-61 | SampleBrowser/SampleBrowser/UI/Suggestion/SuggestionViewController.swift:36-52 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Client/Telemetry/SponsoredTileTelemetry.swift:31— firefox-ios/Client/Telemetry/SponsoredTileTelemetry.swift:31-47 | firefox-ios/Client/Telemetry/SponsoredTileTelemetry.swift:53-69 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:215— firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:215-234 | focus-ios/Blockzilla/Search/SearchEngine.swift:163-179 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingCardView.swift:18— BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingCardView.swift:18-34 | BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingMultipleChoiceCardView.swift:24-44 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Client/Frontend/Settings/CustomSearchViewController.swift:258— firefox-ios/Client/Frontend/Settings/CustomSearchViewController.swift:258-274 | firefox-ios/Client/Frontend/Settings/SettingsTableViewController.swift:570-586 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Client/Application/BackgroundFirefoxSuggestIngestUtility.swift:71— firefox-ios/Client/Application/BackgroundFirefoxSuggestIngestUtility.swift:71-87 | firefox-ios/Client/Frontend/Settings/FirefoxSuggestSettingsViewController.swift:68-85 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Client/Frontend/Browser/ClipboardBarDisplayHandler.swift:60— firefox-ios/Client/Frontend/Browser/ClipboardBarDisplayHandler.swift:60-76 | firefox-ios/Client/Frontend/Browser/LegacyClipboardBarDisplayHandlerDelegate.swift:102-119 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Client/TabManagement/Document/TemporaryDocument.swift:128— firefox-ios/Client/TabManagement/Document/TemporaryDocument.swift:128-146 | firefox-ios/Client/TabManagement/Document/TemporaryDocument.swift:148-164 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (17 corresponding lines) firefox-ios/Storage/Rust/RustPlaces.swift:490— firefox-ios/Storage/Rust/RustPlaces.swift:490-506 | firefox-ios/Storage/Rust/RustPlaces.swift:509-526 — These two members are one piece of code written twice and then edited apart: 17 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Swallowed exception (caught, then discarded) focus-ios/Blockzilla/Utilities/AuthenticationManager.swift:42— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) focus-ios/Blockzilla/Extensions/URLExtensions.swift:84— `catch _` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/TabManagement/Document/TemporaryDocument.swift:284— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/Nimbus/OnboardingFeatureLayer/NimbusOnboardingFeatureLayerProtocol.swift:57— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/Frontend/TrackingProtection/CertificatesHelpers/CertificatesModel.swift:38— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/Frontend/Settings/NotificationsSettingsViewController.swift:122— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/Frontend/Settings/VPN/VPNLocationsView.swift:114— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/Frontend/Library/Downloads/DownloadFileFetcher.swift:36— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSitesManager.swift:156— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/Frontend/Browser/OpenInHelper/OpenPassBookHelper.swift:105— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/Frontend/Browser/DownloadHelper/DownloadLiveActivityWrapper.swift:51— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/Experiments/Messaging/GleanPlumbMessageManager.swift:141— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) firefox-ios/Client/Application/RemoteSettings/Application Services/ASAIRemoteConfig.swift:62— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Swallowed exception (caught, then discarded) SampleBrowser/SampleBrowser/Engine/EngineProvider.swift:20— `catch` takes every exception and records none of it — the body neither logs it, rethrows it, nor even names it, so the failure is discarded as completely as by an empty catch and only the substituted value survives. Log it through whatever this codebase already uses to report problems, narrow the catch to the exception this call can actually raise, or say in a comment on the catch why the failure genuinely cannot matter.
Duplicated block (14 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/Internal/WKAboutHomeHandler.swift:11— BrowserKit/Sources/WebEngine/WKWebview/Internal/WKAboutHomeHandler.swift:11-24 | BrowserKit/Sources/WebEngine/WKWebview/Internal/WKErrorPageHandler.swift:10-23 — before extracting anything, compare `BrowserKit/Sources/WebEngine/WKWebview/Internal/WKAboutHomeHandler.swift` and `BrowserKit/Sources/WebEngine/WKWebview/Internal/WKErrorPageHandler.swift` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift:76— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift:76-89 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift:78-91 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/FeatureHolder.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 39 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (14 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Utils.swift:29— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Utils.swift:29-42 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Utils.swift:29-42 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Utils.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Utils.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (14 lines × 2) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift:320— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift:320-333 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardTableViewModel.swift:27-40 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardTableViewModel.swift:27` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (14 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift:358— firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift:358-371 | firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift:396-409 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift:358` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:154— firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:154-167 | firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift:118-131 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift` and `firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1439— firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1439-1452 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:405-418 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:312— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:312-325 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:336-349 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:79— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:79-92 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewModel.swift:101-114 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewModel.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (14 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/BookmarksSaver.swift:129— firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/BookmarksSaver.swift:129-142 | firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/BookmarksSaver.swift:168-181 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/BookmarksSaver.swift:129` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) firefox-ios/Client/Frontend/Microsurvey/Survey/View/MicrosurveyTableHeaderView.swift:50— firefox-ios/Client/Frontend/Microsurvey/Survey/View/MicrosurveyTableHeaderView.swift:50-63 | firefox-ios/Client/Frontend/Microsurvey/Survey/View/MicrosurveyTableViewCell.swift:116-129 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Microsurvey/Survey/View/MicrosurveyTableHeaderView.swift:50` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14 lines × 2) firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:196— firefox-ios/Client/Frontend/Browser/SearchEngines/OpenSearchEngine.swift:196-209 | focus-ios/Blockzilla/Search/SearchEngine.swift:116-129 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (14 lines × 2) firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:802— firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:802-815 | firefox-ios/Client/Frontend/Browser/TabScrollController/TabScrollHandler.swift:260-273 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
AC3 · Page structure· Page without a main landmark · ×12
Page without a main landmark REDACTED:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark SampleBrowser/SampleBrowser/testPrintPreview.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark firefox-ios/Client/Assets/About/Licenses.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark firefox-ios/Client/Assets/CertError.html:5— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark firefox-ios/Client/Assets/Debug/testPopUp.html:2— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark firefox-ios/Client/Assets/NetError.html:5— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark firefox-ios/Client/Frontend/Reader/Resources/Reader.html:5— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark firefox-ios/Client/Frontend/Reader/Resources/ReaderViewLoading.html:5— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark firefox-ios/Client/Frontend/UserContent/UserScripts/AddressFormManager/AddressFormManager.html:6— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:6— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark REDACTED:1— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Page without a main landmark focus-ios/Blockzilla/UIComponents/ErrorPage/errorPage.html:6— No <main> (or role="main") means no "skip to content" target and a weaker landmark map. Wrap the primary content in <main>.
Duplicated block (12 lines × 2) BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:125— BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:125-136 | BrowserKit/Sources/VPNKit/KeychainVPNTokenStore.swift:90-101 — before extracting anything, compare `BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift` and `BrowserKit/Sources/VPNKit/KeychainVPNTokenStore.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (12 lines × 2) BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingButton.swift:103— BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingButton.swift:103-114 | BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingButton.swift:126-137 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingButton.swift:103` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingCardView.swift:19— BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingCardView.swift:19-30 | BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingMultipleChoiceCardView.swift:25-36 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingCardView.swift:19` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (12 lines × 2) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:233— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:233-244 | BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift:306-317 — before extracting anything, compare `BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift` and `BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:227` calls `itemIdentifier`, `webCompatReportPreviewDidTapTechnicalData` and `BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift:301` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (12 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:292— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:292-303 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabCell.swift:191-202 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/TabCell.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:260— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:260-271 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:283-294 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (12 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:94— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:94-105 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewModel.swift:116-127 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewModel.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 34 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:94` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift:128— firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift:128-139 | firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/GroupedFolderHierarchyFetcher.swift:209-220 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (12 lines × 2) firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetView.swift:353— firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetView.swift:353-365 | focus-ios/Blockzilla/Menu/Old/PhotonActionSheetCell.swift:122-133 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetView.swift:353` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) firefox-ios/Storage/Rust/RustAutofill.swift:583— firefox-ios/Storage/Rust/RustAutofill.swift:583-594 | firefox-ios/Storage/Rust/RustLogins.swift:260-271 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Storage/Rust/RustAutofill.swift:583` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12 lines × 2) SampleBrowser/SampleBrowser/Dependency/DependencyHelper.swift:9— SampleBrowser/SampleBrowser/Dependency/DependencyHelper.swift:9-20 | SampleComponentLibraryApp/SampleComponentLibraryApp/Dependency/DependencyHelper.swift:9-20 — before extracting anything, compare `SampleBrowser/SampleBrowser/Dependency/DependencyHelper.swift` and `SampleComponentLibraryApp/SampleComponentLibraryApp/Dependency/DependencyHelper.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
D4 · Code Duplication· Edited copy of a member (22 corresponding lines) · ×10
Edited copy of a member (22 corresponding lines) focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:432— focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:432-455 | focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:952-973 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift:174— BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift:174-197 | firefox-ios/Client/Frontend/Reader/ReaderModeHandlers.swift:147-168 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksPanelViewModel.swift:303— firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksPanelViewModel.swift:303-324 | firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksPanelViewModel.swift:339-360 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) firefox-ios/Client/Frontend/InternalSchemeHandler/ErrorPageHelper.swift:69— firefox-ios/Client/Frontend/InternalSchemeHandler/ErrorPageHelper.swift:69-90 | firefox-ios/Client/Frontend/NativeErrorPage/CertificateHelper.swift:22-46 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:43— BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:43-66 | BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingMultipleChoiceCardView.swift:51-72 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) firefox-ios/Storage/Rust/RustLogins.swift:250— firefox-ios/Storage/Rust/RustLogins.swift:250-279 | firefox-ios/Storage/Rust/RustPlaces.swift:111-132 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:118— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:118-139 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabCell.swift:82-104 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:1609— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:1609-1630 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:1632-1653 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) firefox-ios/Client/Frontend/Microsurvey/Survey/View/MicrosurveyViewController.swift:128— firefox-ios/Client/Frontend/Microsurvey/Survey/View/MicrosurveyViewController.swift:128-149 | firefox-ios/Client/Frontend/Onboarding/Views/PrivacyPreferencesViewController.swift:64-89 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (22 corresponding lines) firefox-ios/Client/Utils/CuratedRecommendationCacheUtility.swift:81— firefox-ios/Client/Utils/CuratedRecommendationCacheUtility.swift:81-102 | firefox-ios/Client/Utils/CuratedRecommendationCacheUtility.swift:104-125 — These two members are one piece of code written twice and then edited apart: 22 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (20 corresponding lines) · ×10
Edited copy of a member (20 corresponding lines) firefox-ios/Client/TabManagement/Tab.swift:1098— firefox-ios/Client/TabManagement/Tab.swift:1098-1117 | firefox-ios/Client/TabManagement/TabWebView.swift:305-324 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift:153— BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift:153-172 | firefox-ios/Client/Frontend/Reader/ReaderModeHandlers.swift:123-145 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:596— firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:596-617 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:619-638 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) BrowserKit/Sources/ActionExtensionKit/ActionShareItem.swift:31— BrowserKit/Sources/ActionExtensionKit/ActionShareItem.swift:31-50 | BrowserKit/Sources/ActionExtensionKit/ActionShareItem.swift:52-71 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) firefox-ios/Client/Frontend/Reader/View/ReaderModeStyleViewController.swift:257— firefox-ios/Client/Frontend/Reader/View/ReaderModeStyleViewController.swift:257-276 | firefox-ios/Client/Frontend/Reader/View/ReaderModeStyleViewController.swift:278-299 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) focus-ios/Blockzilla/BrowserViewController.swift:1908— focus-ios/Blockzilla/BrowserViewController.swift:1908-1929 | focus-ios/Blockzilla/BrowserViewController.swift:1932-1951 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:106— firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:106-125 | focus-ios/Blockzilla/UIComponents/GradientProgressBar.swift:101-121 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) BrowserKit/Sources/SummarizeKit/Backend/AppleIntelligence/FoundationModelsSummarizer.swift:63— BrowserKit/Sources/SummarizeKit/Backend/AppleIntelligence/FoundationModelsSummarizer.swift:63-85 | BrowserKit/Sources/SummarizeKit/Backend/LLM/LiteLLMSummarizer.swift:41-60 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:108— firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:108-127 | focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift:74-94 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (20 corresponding lines) BrowserKit/Sources/WebCompatReporterKit/Preview/WebCompatReportSheetPreview.swift:102— BrowserKit/Sources/WebCompatReporterKit/Preview/WebCompatReportSheetPreview.swift:102-122 | BrowserKit/Sources/WebCompatReporterKit/Preview/WebCompatReportSheetPreview.swift:125-144 — These two members are one piece of code written twice and then edited apart: 20 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (16 corresponding lines) · ×10
Edited copy of a member (16 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:244— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:244-261 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift:371-386 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) firefox-ios/Client/Frontend/Library/Reader/ReaderPanel.swift:520— firefox-ios/Client/Frontend/Library/Reader/ReaderPanel.swift:520-535 | firefox-ios/Client/Frontend/Widgets/SiteTableViewController.swift:215-233 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) BrowserKit/Sources/Common/Utilities/TextStyling.swift:58— BrowserKit/Sources/Common/Utilities/TextStyling.swift:58-73 | BrowserKit/Sources/Common/Utilities/TextStyling.swift:90-105 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) firefox-ios/Storage/Rust/RustLogins.swift:586— firefox-ios/Storage/Rust/RustLogins.swift:586-601 | firefox-ios/Storage/Rust/RustLogins.swift:508-523 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:156— firefox-ios/Client/Frontend/Widgets/GradientProgressBar.swift:156-171 | focus-ios/Blockzilla/UIComponents/GradientProgressBar.swift:147-162 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) firefox-ios/Extensions/ShareTo/ShareViewController.swift:470— firefox-ios/Extensions/ShareTo/ShareViewController.swift:470-493 | firefox-ios/Extensions/ShareTo/ShareViewController.swift:495-510 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift:174— firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift:174-189 | firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift:191-206 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) firefox-ios/Storage/Rust/RustPlaces.swift:453— firefox-ios/Storage/Rust/RustPlaces.swift:453-468 | firefox-ios/Storage/Rust/RustPlaces.swift:471-488 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) firefox-ios/Client/Frontend/Settings/AppearanceSettings/AppearanceSettingsView.swift:146— firefox-ios/Client/Frontend/Settings/AppearanceSettings/AppearanceSettingsView.swift:146-161 | firefox-ios/Client/Frontend/Settings/AppearanceSettings/AppearanceSettingsView.swift:169-184 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (16 corresponding lines) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:718— firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:718-733 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:3174-3191 — These two members are one piece of code written twice and then edited apart: 16 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (13 lines × 2) BrowserKit/Sources/Common/Utilities/TextStyling.swift:76— BrowserKit/Sources/Common/Utilities/TextStyling.swift:76-88 | BrowserKit/Sources/Common/Utilities/TextStyling.swift:108-120 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) BrowserKit/Sources/MenuKit/MenuAccountCell.swift:143— BrowserKit/Sources/MenuKit/MenuAccountCell.swift:143-155 | BrowserKit/Sources/MenuKit/MenuCell.swift:122-134 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/MenuKit/MenuAccountCell.swift:143` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:44— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:44-56 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:44-56 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Unreachable.swift:44— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Unreachable.swift:44-56 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Unreachable.swift:44-56 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Unreachable.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Unreachable.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13 lines × 2) SampleBrowser/SampleBrowser/UI/Components/NavigationToolbarContainer.swift:67— SampleBrowser/SampleBrowser/UI/Components/NavigationToolbarContainer.swift:67-79 | firefox-ios/Client/Frontend/Browser/Toolbars/NavigationToolbarContainer.swift:112-124 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `SampleBrowser/SampleBrowser/UI/Components/NavigationToolbarContainer.swift:82` calls `configureContextualHint` and `firefox-ios/Client/Frontend/Browser/Toolbars/NavigationToolbarContainer.swift:127` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:86— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:86-98 | firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsEmptyView.swift:99-111 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:86` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:102` calls `invalidateIntrinsicContentSize`, `layoutIfNeeded` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsEmptyView.swift:112` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (13 lines × 2) firefox-ios/Client/Frontend/InternalSchemeHandler/AboutHomeHandler.swift:10— firefox-ios/Client/Frontend/InternalSchemeHandler/AboutHomeHandler.swift:10-22 | firefox-ios/Client/Frontend/InternalSchemeHandler/ErrorPageHelper.swift:208-220 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (13 lines × 2) firefox-ios/Storage/Rust/RustPlaces.swift:158— firefox-ios/Storage/Rust/RustPlaces.swift:158-170 | firefox-ios/Storage/Rust/RustPlaces.swift:222-234 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Storage/Rust/RustPlaces.swift:158` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (13 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:403— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:403-415 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabCell.swift:347-359 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/TabCell.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
MethodTooLong: TelemetryWrapper.gleanRecordEvent firefox-ios/Client/Telemetry/TelemetryWrapper.swift:771— MethodTooLong — gleanRecordEvent runs 670 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 570 over it, 6.70× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: FeatureFlagsDebugViewController.generateFeatureFlagToggleSettings firefox-ios/Client/Frontend/Settings/Main/Debug/FeatureFlags/FeatureFlagsDebugViewController.swift:30— MethodTooLong — generateFeatureFlagToggleSettings runs 361 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 261 over it, 3.61× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TranslationsDocument.constructor REDACTED:1082— MethodTooLong — constructor runs 299 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 199 over it, 2.99× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BrowserSchema.update firefox-ios/Storage/SQL/BrowserSchema.swift:969— MethodTooLong — update runs 269 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 169 over it, 2.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: BrowserSchema.create firefox-ios/Storage/SQL/BrowserSchema.swift:745— MethodTooLong — create runs 176 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 76 over it, 1.76× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: NimbusFeatureFlagLayer.checkNimbusConfigFor firefox-ios/Client/Nimbus/NimbusFeatureFlagLayer.swift:22— MethodTooLong — checkNimbusConfigFor runs 163 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 63 over it, 1.63× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: LoginFormState._getFormFields firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:622— MethodTooLong — _getFormFields runs 129 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 29 over it, 1.29× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
MethodTooLong: TranslationsDocument.#maybePrioritizeRequestsAndSubmitToScheduler REDACTED:3702— MethodTooLong — #maybePrioritizeRequestsAndSubmitToScheduler runs 104 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 4 over it, 1.04× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copies of one member (3 members, 9+ corresponding lines) · ×8
Edited copies of one member (3 members, 9+ corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Places.swift:571— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Places.swift:571-582 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Places.swift:608-616 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Places.swift:650-662 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:317— firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:317-325 | firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:327-335 | firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:337-347 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) firefox-ios/Client/Telemetry/MetricKit/MetricKitWrapper.swift:46— firefox-ios/Client/Telemetry/MetricKit/MetricKitWrapper.swift:46-54 | firefox-ios/Client/Telemetry/MetricKit/MetricKitWrapper.swift:56-64 | firefox-ios/Client/Telemetry/MetricKit/MetricKitWrapper.swift:66-74 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) firefox-ios/Storage/Rust/RustPlaces.swift:312— firefox-ios/Storage/Rust/RustPlaces.swift:312-324 | firefox-ios/Storage/Rust/RustPlaces.swift:348-356 | firefox-ios/Storage/SQL/SQLitePinnedSites.swift:125-133 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:289— firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:289-299 | firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:301-311 | firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:317-325 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/AdsTelemetryContentScript.swift:95— BrowserKit/Sources/WebEngine/WKWebview/Scripts/AdsTelemetryContentScript.swift:95-103 | firefox-ios/Client/Telemetry/AdsTelemetryHelper.swift:130-139 | focus-ios/Blockzilla/Utilities/AdsTelemetryHelper.swift:123-131 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) firefox-ios/Client/Extensions/UIControl+Extension.swift:11— firefox-ios/Client/Extensions/UIControl+Extension.swift:11-20 | firefox-ios/Client/Extensions/UIViewController+Extension.swift:148-156 | firefox-ios/Client/Extensions/UIViewController+Extension.swift:158-166 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 9+ corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:85— firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:85-93 | firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:95-103 | firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:105-113 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 16+ corresponding lines) · ×7
Edited copies of one member (3 members, 16+ corresponding lines) firefox-ios/Client/Frontend/Settings/AIControls/AIControlsSettingsView.swift:180— firefox-ios/Client/Frontend/Settings/AIControls/AIControlsSettingsView.swift:180-195 | firefox-ios/Client/Frontend/Settings/AIControls/AIControlsSettingsView.swift:198-213 | firefox-ios/Client/Frontend/Settings/AIControls/AIControlsSettingsView.swift:216-231 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) firefox-ios/Storage/Rust/RustLogins.swift:357— firefox-ios/Storage/Rust/RustLogins.swift:357-372 | firefox-ios/Storage/Rust/RustLogins.swift:427-442 | firefox-ios/Storage/Rust/RustLogins.swift:459-474 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) firefox-ios/Storage/Rust/RustLogins.swift:357— firefox-ios/Storage/Rust/RustLogins.swift:357-372 | firefox-ios/Storage/Rust/RustLogins.swift:427-442 | firefox-ios/Storage/Rust/RustLogins.swift:508-523 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) firefox-ios/Client/Frontend/Settings/PasswordDetailViewController.swift:229— firefox-ios/Client/Frontend/Settings/PasswordDetailViewController.swift:229-244 | firefox-ios/Client/Frontend/Settings/PasswordDetailViewController.swift:246-265 | firefox-ios/Client/Frontend/Settings/PasswordDetailViewController.swift:267-282 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) firefox-ios/Client/Frontend/Settings/AdvancedAccountSettingViewController.swift:37— firefox-ios/Client/Frontend/Settings/AdvancedAccountSettingViewController.swift:37-53 | firefox-ios/Client/Frontend/Settings/SettingsTableViewController.swift:482-497 | firefox-ios/Client/Frontend/Settings/SettingsTableViewController.swift:503-525 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarAction.swift:182— firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarAction.swift:182-198 | firefox-ios/Client/Frontend/Settings/Translation/TranslationSettingsAction.swift:17-32 | firefox-ios/Client/Frontend/WebCompatReporter/Redux/WebCompatReporterAction.swift:18-34 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 16+ corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKContentScriptManager.swift:31— BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKContentScriptManager.swift:31-46 | BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKContentScriptManager.swift:48-63 | BrowserKit/Sources/WebEngine/WKWebview/Scripts/WKContentScriptManager.swift:65-80 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 16 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (17 lines × 2) BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:103— BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift:103-119 | BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingMultipleChoiceCardView.swift:109-125 — before extracting anything, compare `BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingBasicCardView.swift` and `BrowserKit/Sources/OnboardingKit/Views/OnboardingFlow/OnboardingMultipleChoiceCardView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 32 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (17 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/Scripts/AdsTelemetryContentScript.swift:35— BrowserKit/Sources/WebEngine/WKWebview/Scripts/AdsTelemetryContentScript.swift:35-51 | firefox-ios/Client/Telemetry/AdsTelemetryHelper.swift:79-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift:130— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift:130-146 | firefox-ios/Storage/RustKeychain.swift:229-245 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift:130` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (17 lines × 2) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift:335— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift:335-351 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardTableViewModel.swift:42-58 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (17 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:216— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:216-232 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabCell.swift:206-222 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/TabCell.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 53 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:216` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 2) firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:98— firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:98-114 | firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift:82-98 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift` and `firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Note first that the copies are not typed on the same thing: the declarations holding them bind `viewModel` to `ButtonToastViewModel` in one and `PlainToastViewModel` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:115` calls `setupPaddedButton` and `firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift:99` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (17 lines × 2) focus-ios/Blockzilla/UIComponents/BrowserToolbar.swift:105— focus-ios/Blockzilla/UIComponents/BrowserToolbar.swift:105-121 | focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:547-563 — before extracting anything, compare `focus-ios/Blockzilla/UIComponents/BrowserToolbar.swift` and `focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Hotspot: firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2801— firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift changed 49 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 30 in BrowserViewController.handleNavigation at line 2801. 21 of those changes were fix/bug commits, and the other 28 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:408— firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift changed 33 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 19 in BrowserCoordinator.handle at line 408. 12 of those changes were fix/bug commits, and the other 21 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:970— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift changed 17 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 31 in BrowserViewController.webView at line 970. 11 of those changes were fix/bug commits, so the churn is repair rather than feature work. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:776— firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift changed 11 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 20 in SearchViewController.getCellForSection at line 776. 5 of those changes were fix/bug commits, and the other 6 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: firefox-ios/Client/Coordinators/Router/RouteBuilder.swift firefox-ios/Client/Coordinators/Router/RouteBuilder.swift:38— firefox-ios/Client/Coordinators/Router/RouteBuilder.swift changed 6 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 24 in RouteBuilder.makeRoute at line 38. 1 of those changes was a fix/bug commit, and the other 5 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/Client/Coordinators/Router/RouteBuilder.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
Hotspot: firefox-ios/RustFxA/FxAWebViewModel.swift firefox-ios/RustFxA/FxAWebViewModel.swift:339— firefox-ios/RustFxA/FxAWebViewModel.swift changed 3 times in last 90 days, and the most complex body those changes touched has cyclomatic complexity 21 in FxAWebViewModel.handleRemote at line 339. 1 of those changes was a fix/bug commit, and the other 2 changed it for other reasons — this file is under both repair and feature pressure. Before the next change lands here, make sure the area it touches is under test, then split that area out of the file so the following change is smaller than this one — a file this often edited pays the complexity back every time. Counted over 2026-08-15..2026-11-13, the 90 days ending at the analysed commit. Reproduce with `git log --since='2026-08-15 17:11:35 -05:00' --until='2026-11-13 17:11:35 -05:00' --full-history --no-merges -- firefox-ios/RustFxA/FxAWebViewModel.swift`: merges are excluded because a merge re-states changes already counted at their own commits, and history is NOT path-simplified because a change that reached the file through a merged branch is still a change to it. That command counts raw commits and can read HIGHER than this row, which counts a cherry-picked re-land, and a revert together with the commit it undoes, once each — a difference of several commits on a file whose history was re-landed or reverted inside the window.
FunctionTooLong: bergamot-translator.loadBergamot firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:5— FunctionTooLong — loadBergamot runs 2554 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 2454 over it, 25.54× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: NewPasswordModel.sys.makeRuleset firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:130— FunctionTooLong — makeRuleset runs 355 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 255 over it, 3.55× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: LoginsHelper.window.__firefox__.includeOnce("LoginsHelper") REDACTED:17— FunctionTooLong — window.__firefox__.includeOnce("LoginsHelper") runs 316 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 216 over it, 3.16× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: CreditCardRuleset.sys.makeRuleset firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:714— FunctionTooLong — makeRuleset runs 269 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 169 over it, 2.69× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: TrackingProtectionStats.install firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js:11— FunctionTooLong — install runs 107 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 7 over it, 1.07× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
FunctionTooLong: translations-document.sys.updateElement REDACTED:6023— FunctionTooLong — updateElement runs 106 significant lines (blank, comment-only and punctuation-only lines excluded) in one body. The bar is 100 significant lines; this is 6 over it, 1.06× the bar. This is length, not branching: a long straight-line body scores low on complexity and is still read whole to change any part of it, so the complexity numbers beside this row neither confirm nor excuse it. To reduce it, extract each cohesive step of the body — the runs of statements that work on the same values and would earn the same name — into its own named unit, and have this one call them in order.
D4 · Code Duplication· Edited copy of a member (23 corresponding lines) · ×6
Edited copy of a member (23 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:69— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:69-104 | firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsEmptyView.swift:90-112 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) BrowserKit/Sources/MenuKit/MenuCell.swift:137— BrowserKit/Sources/MenuKit/MenuCell.swift:137-159 | BrowserKit/Sources/MenuKit/MenuInfoCell.swift:117-145 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:371— firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataManagementViewController.swift:371-398 | firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataSearchResultsViewController.swift:180-202 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:36— firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:36-68 | firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:357-379 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionDetailsViewController.swift:122— firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionDetailsViewController.swift:122-146 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift:326-348 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (23 corresponding lines) BrowserKit/Sources/Shared/Date/TimeConstants.swift:195— BrowserKit/Sources/Shared/Date/TimeConstants.swift:195-227 | BrowserKit/Sources/Shared/Date/TimeConstants.swift:229-251 — These two members are one piece of code written twice and then edited apart: 23 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (19 corresponding lines) · ×6
Edited copy of a member (19 corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift:126— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift:126-146 | firefox-ios/Storage/RustKeychain.swift:227-245 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1070— firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1070-1089 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:337-355 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) firefox-ios/Client/Frontend/Library/LibraryPanelContextMenu.swift:52— firefox-ios/Client/Frontend/Library/LibraryPanelContextMenu.swift:52-73 | firefox-ios/Client/Frontend/Library/LibraryPanelContextMenu.swift:75-93 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+TabScrollHandlerDelegate.swift:100— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+TabScrollHandlerDelegate.swift:100-119 | firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:182-200 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:69— BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:69-90 | BrowserKit/Sources/VPNKit/KeychainVPNTokenStore.swift:41-59 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (19 corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Bookmark.swift:202— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Bookmark.swift:202-220 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Bookmark.swift:254-274 — These two members are one piece of code written twice and then edited apart: 19 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Duplicated block (19 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReaderModeContentScript.swift:65— BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReaderModeContentScript.swift:65-83 | firefox-ios/Client/Frontend/Reader/ReaderMode.swift:98-116 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReaderModeContentScript.swift:65` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:154— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:154-172 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:178-196 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:150` calls `startObservingContentScroll` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:174` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (19 lines × 2) REDACTED:183— REDACTED:183-201 | REDACTED:235-253 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `REDACTED:183` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:279— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:279-297 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:302-320 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (19 lines × 2) firefox-ios/Client/Telemetry/SearchTelemetry.swift:306— firefox-ios/Client/Telemetry/SearchTelemetry.swift:306-324 | firefox-ios/Client/Telemetry/SearchTelemetry.swift:414-432 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Telemetry/SearchTelemetry.swift:306` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:104— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:104-122 | firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:123-141 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
XxxComment taskcluster/ffios_taskgraph/loader/screenshots_locales.py:46— # XXX We add 1 to number because `log(100)` returns 2 instead of 3 — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `# REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment firefox-ios/firefox-ios-tests/Tests/ClientTests/TestHistory.swift:327— // XXX - We don't allow querying much info about visits here anymore, so there isn't a lot to do — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:4469— // XXX: Bug 1390200 - Disable NSUserActivity/CoreSpotlight temporarily — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment MozillaRustComponents/Tests/MozillaRustComponentsTests/PlacesTests.swift:176— // XXX: We don't clean up PlacesAPIs properly (issue 749), so — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
XxxComment MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Bookmark.swift:142— // XXX - This function exists to convert the return types of the `bookmarksGetAllWithUrl`, — source code is not a task system: move the work to your tracker and leave a reference instead (e.g. `// REF: #123`), so the task is planned where tasks live and the ticket links back to the code.
D4 · Code Duplication· Edited copy of a member (28 corresponding lines) · ×5
Edited copy of a member (28 corresponding lines) firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:97— firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:97-125 | firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift:81-108 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) firefox-ios/WidgetKit/OpenTabs/TabProvider.swift:21— firefox-ios/WidgetKit/OpenTabs/TabProvider.swift:21-55 | firefox-ios/WidgetKit/TopSites/TopSitesProvider.swift:26-53 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Redux/BrowserActionsBuilder.swift:105— firefox-ios/Client/Frontend/Browser/Toolbars/Redux/BrowserActionsBuilder.swift:105-134 | firefox-ios/Client/Frontend/Browser/Toolbars/Redux/NavigationActionsBuilder.swift:119-146 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift:42— BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift:42-69 | firefox-ios/Client/Frontend/InternalSchemeHandler/InternalSchemeHandler.swift:71-105 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (28 corresponding lines) firefox-ios/Storage/Rust/RustPlaces.swift:173— firefox-ios/Storage/Rust/RustPlaces.swift:173-200 | firefox-ios/Storage/Rust/RustPlaces.swift:237-269 — These two members are one piece of code written twice and then edited apart: 28 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 10+ corresponding lines) · ×5
Edited copies of one member (3 members, 10+ corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:221— firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:221-231 | firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:234-244 | firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:247-256 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) BrowserKit/Sources/SummarizeKit/UI/SummaryView/SummaryTitleCell.swift:30— BrowserKit/Sources/SummarizeKit/UI/SummaryView/SummaryTitleCell.swift:30-40 | SampleBrowser/SampleBrowser/UI/Settings/SettingsCell.swift:26-35 | SampleBrowser/SampleBrowser/UI/Suggestion/SuggestionCellViewModel.swift:25-34 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/AdsTelemetryContentScript.swift:82— BrowserKit/Sources/WebEngine/WKWebview/Scripts/AdsTelemetryContentScript.swift:82-91 | firefox-ios/Client/Telemetry/AdsTelemetryHelper.swift:113-128 | focus-ios/Blockzilla/Utilities/AdsTelemetryHelper.swift:109-121 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1497— firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1497-1506 | firefox-ios/Client/Coordinators/WebCompatReportCoordinator.swift:63-74 | firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseCoordinator.swift:98-109 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 10+ corresponding lines) firefox-ios/Client/Frontend/PasswordManagement/DevicePasscodeRequiredViewController.swift:87— firefox-ios/Client/Frontend/PasswordManagement/DevicePasscodeRequiredViewController.swift:87-96 | firefox-ios/Client/Frontend/PasswordManagement/PasswordManagerOnboardingViewController.swift:70-79 | firefox-ios/Client/Frontend/Settings/ContentBlockerSettingViewController.swift:196-205 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 6+ corresponding lines) · ×5
Edited copies of one member (3 members, 6+ corresponding lines) firefox-ios/Client/Frontend/Settings/AppIconSelection/AppIconSelectionView.swift:31— firefox-ios/Client/Frontend/Settings/AppIconSelection/AppIconSelectionView.swift:31-42 | firefox-ios/Client/Frontend/Settings/AppearanceSettings/AddressBarSettingsView.swift:25-34 | firefox-ios/Client/Frontend/Settings/AppearanceSettings/Zoom/PageZoomSettingView.swift:37-42 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 6+ corresponding lines) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:115— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:115-121 | firefox-ios/Client/Frontend/Autofill/Address/AddressCellView.swift:129-136 | firefox-ios/Client/Frontend/Autofill/CreditCard/ViewComponents/CreditCardAutofillToggle.swift:72-77 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 6+ corresponding lines) BrowserKit/Sources/Common/Utilities/AppInfo.swift:22— BrowserKit/Sources/Common/Utilities/AppInfo.swift:22-27 | BrowserKit/Sources/Shared/AppInfo.swift:9-14 | focus-ios/Shared/AppInfo.swift:46-51 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 6+ corresponding lines) BrowserKit/Sources/ComponentLibrary/Buttons/LinkButton.swift:13— BrowserKit/Sources/ComponentLibrary/Buttons/LinkButton.swift:13-18 | BrowserKit/Sources/ComponentLibrary/Buttons/RoundedButtonWithImage.swift:41-48 | BrowserKit/Sources/ComponentLibrary/Buttons/SecondaryRoundedButton.swift:40-49 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 6+ corresponding lines) BrowserKit/Sources/MenuKit/MenuSiteProtectionsHeader.swift:126— BrowserKit/Sources/MenuKit/MenuSiteProtectionsHeader.swift:126-131 | firefox-ios/Client/Frontend/Home/Homepage/SectionHeader/LabelButtonHeaderView.swift:119-125 | firefox-ios/Client/Frontend/PasswordManagement/BreachAlertsDetailView.swift:185-190 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 6 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 4+ corresponding lines) · ×5
Edited copies of one member (3 members, 4+ corresponding lines) firefox-ios/WidgetKit/Helpers.swift:14— firefox-ios/WidgetKit/Helpers.swift:14-17 | firefox-ios/WidgetKit/OpenTabs/OpenTabsWidget.swift:171-174 | firefox-ios/WidgetKit/TopSites/TopSitesWidget.swift:117-120 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Account/ConnectSetting.swift:34— firefox-ios/Client/Frontend/Settings/Main/Account/ConnectSetting.swift:34-37 | firefox-ios/Client/Frontend/Settings/Main/Privacy/AutofillCreditCardSettings.swift:36-39 | firefox-ios/Client/Frontend/Settings/Main/Support/ShowIntroductionSetting.swift:24-32 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) firefox-ios/Client/Frontend/Settings/HomepageSettings/HomePageSettingViewController.swift:64— firefox-ios/Client/Frontend/Settings/HomepageSettings/HomePageSettingViewController.swift:64-67 | firefox-ios/Client/Frontend/Settings/HomepageSettings/TopSitesSettings/TopSitesSettingsViewController.swift:22-25 | firefox-ios/Client/Frontend/Settings/NewTabContentSettingsViewController.swift:80-83 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) firefox-ios/Client/Frontend/Browser/TermsOfUse/View/TermsOfUseViewController.swift:147— firefox-ios/Client/Frontend/Browser/TermsOfUse/View/TermsOfUseViewController.swift:147-150 | firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:208-217 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:110-118 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 4+ corresponding lines) firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportRecorder.swift:13— firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportRecorder.swift:13-17 | firefox-ios/Client/Frontend/Share/ShareTelemetry.swift:15-18 | firefox-ios/Client/Telemetry/TabsPanelTelemetry.swift:47-50 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (16 lines × 2) BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:551— BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:551-566 | BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:569-584 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:585` calls `preferredColorScheme` and `BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:567` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) BrowserKit/Sources/Shared/Deferred/Deferred.swift:32— BrowserKit/Sources/Shared/Deferred/Deferred.swift:32-47 | focus-ios/Deferred/Deferred.swift:27-42 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (16 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkDiffableDataSource.swift:26— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkDiffableDataSource.swift:26-41 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkDiffableDataSource.swift:27-42 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkDiffableDataSource.swift:26` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note first that the copies are not typed on the same thing: the declarations holding them bind `folders` to `[Folder]` in one and `[GroupedFolder]` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (16 lines × 2) firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:177— firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:177-192 | firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:218-233 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:177` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:234` calls `recordEvent` and `firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:193` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (16 lines × 2) firefox-ios/Client/Frontend/Library/LibraryViewController/LibraryNavigationController.swift:9— firefox-ios/Client/Frontend/Library/LibraryViewController/LibraryNavigationController.swift:9-24 | firefox-ios/Client/Frontend/Settings/SettingsNavigationController.swift:9-30 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/LibraryViewController/LibraryNavigationController.swift` and `firefox-ios/Client/Frontend/Settings/SettingsNavigationController.swift` as WHOLE FILES: 93% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) BrowserKit/Sources/Common/Extensions/URLExtension.swift:427— BrowserKit/Sources/Common/Extensions/URLExtension.swift:427-441 | focus-ios/Blockzilla/Extensions/URLExtensions.swift:39-53 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/Common/Extensions/URLExtension.swift:427` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The `return` at the foot of the matched lines is the enclosing body's own terminal exit, not an early one: it moves with them unchanged, and each site calls the extracted unit from the position that `return` occupied — no decision has to be handed back and re-acted on.
Duplicated block (15 lines × 2) BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:559— BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:559-573 | BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:596-610 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:559` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) firefox-ios/Storage/SQL/SQLiteReadingList.swift:96— firefox-ios/Storage/SQL/SQLiteReadingList.swift:96-110 | firefox-ios/Storage/SQL/SQLiteReadingList.swift:136-150 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Storage/SQL/SQLiteReadingList.swift:96` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (15 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:81— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:81-95 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:81-95 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Sysctl.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (15 lines × 2) BrowserKit/Sources/ComponentLibrary/Buttons/LinkButton.swift:46— BrowserKit/Sources/ComponentLibrary/Buttons/LinkButton.swift:46-60 | firefox-ios/Client/Frontend/Reader/View/ReaderModeFontTypeButton.swift:32-46 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Off the main sequence: DesignSystem — DesignSystem: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 2 project(s), so it's rigid to change.
Off the main sequence: UIHelpers — UIHelpers: abstractness 0.00, instability 0.00, distance 1.00 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: Redux — Redux: abstractness 0.73, instability 1.00, distance 0.73 — zone of uselessness — abstract and unstable, so it's likely unused.
Off the main sequence: ContentBlockingGenerator — ContentBlockingGenerator: abstractness 0.29, instability 0.00, distance 0.71 — zone of pain — concrete and depended on by 1 project(s), so it's rigid to change.
Off the main sequence: ComponentLibrary — ComponentLibrary: abstractness 0.04, instability 0.25, distance 0.71 — zone of pain — concrete and depended on by 6 project(s), so it's rigid to change.
Change-coupling hub: BrowserViewController.swift → NavigationToolbarContainerModel.swift, ToolbarMiddleware.swift, ContextualHintCopyProvider.swift, ContextualHintEligibilityUtility.swift firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift— `firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift` changes together with 4 other files — `firefox-ios/Client/Frontend/Browser/Toolbars/Models/NavigationToolbarContainerModel.swift`, `firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarMiddleware.swift`, `firefox-ios/Client/Frontend/ContextualHint/ContextualHintCopyProvider.swift`, `firefox-ios/Client/Frontend/ContextualHint/ContextualHintEligibilityUtility.swift` — none of which declares a dependency on it: one file is the hub of 4 separate couplings, not 4 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 4.
Change-coupling hub: TabDisplayModel.swift → TabTrayState.swift, TabsPanelState.swift, TabDisplayView.swift firefox-ios/Client/Frontend/Browser/Tabs/Models/TabDisplayModel.swift— `firefox-ios/Client/Frontend/Browser/Tabs/Models/TabDisplayModel.swift` changes together with 3 other files — `firefox-ios/Client/Frontend/Browser/Tabs/State/TabTrayState.swift`, `firefox-ios/Client/Frontend/Browser/Tabs/State/TabsPanelState.swift`, `firefox-ios/Client/Frontend/Browser/Tabs/Views/TabDisplayView.swift` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: HomepageViewController.swift → HeaderState.swift, TopSitesSectionState.swift, HomepageTelemetry.swift firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift— `firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift` changes together with 3 other files — `firefox-ios/Client/Frontend/Home/Homepage/Header/HeaderState.swift`, `firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSitesSectionState.swift`, `firefox-ios/Client/Telemetry/HomepageTelemetry.swift` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
Change-coupling hub: BrowserCoordinator.swift → NavigationBrowserAction.swift, MenuNavigationDestination.swift, TemporaryDocument.swift firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift— `firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift` changes together with 3 other files — `firefox-ios/Client/Frontend/Browser/BrowserViewController/Actions/NavigationBrowserAction.swift`, `firefox-ios/Client/Frontend/Browser/MainMenu/Redux/MenuNavigationDestination.swift`, `firefox-ios/Client/TabManagement/Document/TemporaryDocument.swift` — none of which declares a dependency on it: one file is the hub of 3 separate couplings, not 3 unrelated pairs. Read the hub first: if the others each duplicate a part of what it does, the shared concern belongs in ONE unit and extracting it clears every edge at once; if the hub is a registry, dispatcher or barrel that must name each of them, the coupling is structural and the question is whether that list can be discovered instead of enumerated. Fixing the hub is one change; breaking the couplings one pair at a time is 3.
D4 · Code Duplication· Edited copy of a member (36 corresponding lines) · ×4
Edited copy of a member (36 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/BookmarksSaver.swift:119— firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/BookmarksSaver.swift:119-154 | firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/BookmarksSaver.swift:156-192 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:216— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentTabCell.swift:216-251 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabCell.swift:206-241 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) BrowserKit/Sources/ActionExtensionKit/FirefoxURLBuilding.swift:51— BrowserKit/Sources/ActionExtensionKit/FirefoxURLBuilding.swift:51-86 | BrowserKit/Sources/ActionExtensionKit/FirefoxURLBuilding.swift:88-129 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (36 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift:141— firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift:141-177 | firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift:437-472 — These two members are one piece of code written twice and then edited apart: 36 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (21 corresponding lines) · ×4
Edited copy of a member (21 corresponding lines) BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:20— BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:20-40 | firefox-ios/Client/Frontend/Onboarding/Models/OnboardingKitCardInfoModel.swift:23-51 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReaderModeContentScript.swift:63— BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/ReaderModeContentScript.swift:63-83 | firefox-ios/Client/Frontend/Reader/ReaderMode.swift:93-116 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/Redux/HomepageAction.swift:27— firefox-ios/Client/Frontend/Home/Homepage/Redux/HomepageAction.swift:27-47 | firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSitesAction.swift:25-45 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (21 corresponding lines) BrowserKit/Sources/ComponentLibrary/Buttons/LinkButton.swift:20— BrowserKit/Sources/ComponentLibrary/Buttons/LinkButton.swift:20-40 | firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTraySelectorButtonModel.swift:31-51 — These two members are one piece of code written twice and then edited apart: 21 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 17+ corresponding lines) · ×4
Edited copies of one member (3 members, 17+ corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewModel.swift:53— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewModel.swift:53-69 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewModel.swift:54-70 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:36-52 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 17+ corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Redux/AddressBarState.swift:344— firefox-ios/Client/Frontend/Browser/Toolbars/Redux/AddressBarState.swift:344-362 | firefox-ios/Client/Frontend/Browser/Toolbars/Redux/AddressBarState.swift:377-395 | firefox-ios/Client/Frontend/Browser/Toolbars/Redux/AddressBarState.swift:397-413 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 17+ corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/State/TabPeekState.swift:51— firefox-ios/Client/Frontend/Browser/Tabs/State/TabPeekState.swift:51-67 | firefox-ios/Client/Frontend/Settings/Translation/TranslationSettingsState.swift:68-84 | firefox-ios/Client/Frontend/TrackingProtection/TrackigProtectionRedux/TrackingProtectionState.swift:73-91 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 17+ corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:117— firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:117-133 | firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:135-151 | firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:155-171 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 17 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 14+ corresponding lines) · ×4
Edited copies of one member (3 members, 14+ corresponding lines) firefox-ios/Storage/Rust/RustAutofill.swift:287— firefox-ios/Storage/Rust/RustAutofill.swift:287-300 | firefox-ios/Storage/Rust/RustAutofill.swift:400-417 | firefox-ios/Storage/Rust/RustAutofill.swift:424-437 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) firefox-ios/Storage/Rust/RustAutofill.swift:145— firefox-ios/Storage/Rust/RustAutofill.swift:145-158 | firefox-ios/Storage/Rust/RustAutofill.swift:164-177 | firefox-ios/Storage/Rust/RustAutofill.swift:443-456 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) BrowserKit/Sources/Shared/Extensions/WKWebViewExtensions.swift:33— BrowserKit/Sources/Shared/Extensions/WKWebViewExtensions.swift:33-46 | BrowserKit/Sources/Shared/Extensions/WKWebViewExtensions.swift:59-73 | BrowserKit/Sources/WebEngine/WKWebview/WKEngineWebView.swift:111-124 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 14+ corresponding lines) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputView.swift:141— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputView.swift:141-154 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputView.swift:156-169 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputView.swift:171-186 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 14 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 5+ corresponding lines) · ×4
Edited copies of one member (3 members, 5+ corresponding lines) SampleBrowser/SampleBrowser/Extensions/UIAlertController+Error.swift:12— SampleBrowser/SampleBrowser/Extensions/UIAlertController+Error.swift:12-20 | firefox-ios/Client/Frontend/Settings/Main/Debug/ResetInstallationHistorySetting.swift:70-74 | firefox-ios/Client/Frontend/Settings/Main/Debug/TriggerVPNAttestationSetting.swift:112-117 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 5+ corresponding lines) firefox-ios/Client/Frontend/Settings/AutoplaySettingsViewController.swift:18— firefox-ios/Client/Frontend/Settings/AutoplaySettingsViewController.swift:18-24 | firefox-ios/Client/Frontend/Settings/QuickAnswers/QuickAnswersSettingsViewController.swift:16-20 | firefox-ios/Client/Frontend/Settings/Translation/TranslationSettingsViewController.swift:12-16 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 5+ corresponding lines) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:127— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:127-132 | firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:1051-1057 | firefox-ios/Client/Frontend/Home/PrivateHome/PrivateHomepageViewController.swift:246-250 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 5+ corresponding lines) firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseState.swift:37— firefox-ios/Client/Frontend/Browser/TermsOfUse/TermsOfUseState.swift:37-45 | firefox-ios/Client/Frontend/Home/Homepage/Redux/HomepageTelemetryState.swift:35-43 | firefox-ios/Client/Frontend/Microsurvey/Survey/MicrosurveyState.swift:42-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 5 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (23 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift:41— BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift:41-63 | firefox-ios/Storage/PageMetadata.swift:41-63 — before extracting anything, compare `BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/EnginePageMetadata.swift` and `firefox-ios/Storage/PageMetadata.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 42 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (23 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewModel.swift:120— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewModel.swift:120-142 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewModel.swift:135-157 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (23 lines × 2) focus-ios/Blockzilla/UIComponents/BrowserToolbar.swift:121— focus-ios/Blockzilla/UIComponents/BrowserToolbar.swift:121-143 | focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:578-600 — before extracting anything, compare `focus-ios/Blockzilla/UIComponents/BrowserToolbar.swift` and `focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `focus-ios/Blockzilla/UIComponents/BrowserToolbar.swift:121` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (23 lines × 2) focus-ios/Blockzilla/UIComponents/BrowserToolbar.swift:146— focus-ios/Blockzilla/UIComponents/BrowserToolbar.swift:146-168 | focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:624-646 — before extracting anything, compare `focus-ios/Blockzilla/UIComponents/BrowserToolbar.swift` and `focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (8 lines × 3) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:99— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:99-106 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:128-135 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:169-176 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:99` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (8 lines × 3) firefox-ios/Client/Frontend/Settings/AppearanceSettings/WallpaperSettings/v1/WallpaperSettingsViewController.swift:248— firefox-ios/Client/Frontend/Settings/AppearanceSettings/WallpaperSettings/v1/WallpaperSettingsViewController.swift:248-255 | firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:602-609 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:312-319 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Settings/AppearanceSettings/WallpaperSettings/v1/WallpaperSettingsViewController.swift:248` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8 lines × 3) firefox-ios/Storage/Rust/RustAutofill.swift:86— firefox-ios/Storage/Rust/RustAutofill.swift:86-93 | firefox-ios/Storage/Rust/RustLogins.swift:287-297 | firefox-ios/Storage/Rust/RustRemoteTabs.swift:50-60 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (8 lines × 3) firefox-ios/Storage/Rust/RustAutofill.swift:98— firefox-ios/Storage/Rust/RustAutofill.swift:98-105 | firefox-ios/Storage/Rust/RustLogins.swift:299-309 | firefox-ios/Storage/Rust/RustRemoteTabs.swift:62-72 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once.
Duplicated block (6 lines × 3) firefox-ios/Client/Frontend/Browser/Tabs/Views/EmptyPrivateTabsView.swift:107— firefox-ios/Client/Frontend/Browser/Tabs/Views/EmptyPrivateTabsView.swift:107-112 | firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:106-111 | firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:125-130 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `firefox-ios/Client/Frontend/Browser/Tabs/Views/EmptyPrivateTabsView.swift:113` calls `constraint` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:112` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 3) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:283— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:283-288 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:306-311 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:254-259 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:283` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 3) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:195— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift:195-200 | BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:392-397 | BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift:268-273 — before extracting anything, compare `BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift` and `BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (6 lines × 3) firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksCell.swift:56— firefox-ios/Client/Frontend/Home/Homepage/Bookmark/BookmarksCell.swift:56-61 | firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/JumpBackInCell.swift:84-91 | firefox-ios/Client/Frontend/Home/Homepage/JumpBackIn/SyncedTabCell.swift:179-186 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
HackComment focus-ios/Blockzilla/Utilities/KeyboardHelper.swift:18— // HACK: UIViewAnimationCurve doesn't expose the keyboard animation used (curveValue = 7), — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment BrowserKit/Sources/Shared/KeyboardHelper.swift:29— // HACK: UIViewAnimationCurve doesn't expose the keyboard animation used (curveValue = 7), — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
HackComment focus-ios/Blockzilla/Settings/Controller/AboutViewController.swift:132— // Hack to cover header separator line — a workaround marked in source: record what it is compensating for and what would allow its removal (the upstream fix, the API it is waiting on, the invariant it restores), so the next reader can judge whether it is still needed rather than rediscovering why it is there.
D4 · Code Duplication· Members sharing a duplicated core (4 members, 50+ identical tokens) · ×3
Members sharing a duplicated core (4 members, 50+ identical tokens) BrowserKit/Sources/Shared/InstallationUtils.swift:9— BrowserKit/Sources/Shared/InstallationUtils.swift:9-15 | MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:147-181 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:144-194 | firefox-ios/Client/Experiments/RecordedNimbusContext.swift:67-124 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:217— firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:217-235 | firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:237-255 | firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:257-279 | firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:281-303 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
Members sharing a duplicated core (4 members, 50+ identical tokens) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:168— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:168-184 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:173-189 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:146-162 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift:189-205 — These 4 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 4 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 4 times.
D4 · Code Duplication· Edited copy of a member (31 corresponding lines) · ×3
Edited copy of a member (31 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:38— firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:38-72 | firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTraySelectorView.swift:128-158 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) firefox-ios/Storage/Rust/RustLogins.swift:476— firefox-ios/Storage/Rust/RustLogins.swift:476-506 | firefox-ios/Storage/Rust/RustLogins.swift:525-558 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (31 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:112— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:112-145 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:112-142 — These two members are one piece of code written twice and then edited apart: 31 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (32 corresponding lines) · ×3
Edited copy of a member (32 corresponding lines) firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:171— firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:171-202 | firefox-ios/Client/Frontend/TabContentsScripts/FormAutofillHelper/FormAutofillHelper.swift:204-245 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEngineProvider.swift:176— firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEngineProvider.swift:176-208 | firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEngineProvider.swift:211-242 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (32 corresponding lines) firefox-ios/Client/Frontend/Browser/MainMenu/MainMenuConfigurationUtility.swift:393— firefox-ios/Client/Frontend/Browser/MainMenu/MainMenuConfigurationUtility.swift:393-424 | firefox-ios/Client/Frontend/Browser/MainMenu/MainMenuConfigurationUtility.swift:667-700 — These two members are one piece of code written twice and then edited apart: 32 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (37 corresponding lines) · ×3
Edited copy of a member (37 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:188— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:188-224 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:193-230 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (37 corresponding lines) REDACTED:170— REDACTED:170-207 | REDACTED:224-260 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (37 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift:357— firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift:357-393 | firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabAnimation.swift:395-435 — These two members are one piece of code written twice and then edited apart: 37 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (30 corresponding lines) · ×3
Edited copy of a member (30 corresponding lines) firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:282— firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:282-314 | focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift:187-216 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) firefox-ios/Client/Telemetry/SearchTelemetry.swift:482— firefox-ios/Client/Telemetry/SearchTelemetry.swift:482-515 | firefox-ios/Client/Telemetry/SearchTelemetry.swift:520-549 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (30 corresponding lines) firefox-ios/Client/Coordinators/Library/DownloadsCoordinator.swift:53— firefox-ios/Client/Coordinators/Library/DownloadsCoordinator.swift:53-84 | firefox-ios/Client/Coordinators/Library/LibraryCoordinator.swift:99-128 — These two members are one piece of code written twice and then edited apart: 30 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 8+ corresponding lines) · ×3
Edited copies of one member (3 members, 8+ corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewModel.swift:103— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewModel.swift:103-110 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewModel.swift:104-111 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:70-77 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:4534— firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:4534-4541 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:4543-4550 | firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:413-421 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 8+ corresponding lines) firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:233— firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:233-240 | firefox-ios/Client/Frontend/TrackingProtection/TrackingDetailsHelpers/BlockedTrackersLearnMoreViewController.swift:131-138 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionDetailsViewController.swift:185-192 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 8 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 4+ corresponding lines) · ×3
Edited copies of one member (4 members, 4+ corresponding lines) BrowserKit/Sources/MenuKit/MenuAccountCell.swift:60— BrowserKit/Sources/MenuKit/MenuAccountCell.swift:60-63 | BrowserKit/Sources/MenuKit/MenuCell.swift:56-59 | BrowserKit/Sources/MenuKit/MenuInfoCell.swift:60-63 | firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersHelpers/BlockedTrackerCell.swift:36-39 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) BrowserKit/Sources/SummarizeKit/UI/SummaryView/SummaryAnswerCell.swift:17— BrowserKit/Sources/SummarizeKit/UI/SummaryView/SummaryAnswerCell.swift:17-20 | BrowserKit/Sources/SummarizeKit/UI/SummaryView/SummaryTitleCell.swift:21-24 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkCell.swift:49-52 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderCell.swift:28-31 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 4+ corresponding lines) firefox-ios/Client/Frontend/PasswordManagement/AddCredentialViewController.swift:265— firefox-ios/Client/Frontend/PasswordManagement/AddCredentialViewController.swift:265-268 | firefox-ios/Client/Frontend/PasswordManagement/PasswordManagerListViewController.swift:495-498 | firefox-ios/Client/Frontend/Settings/PasswordDetailViewController.swift:392-395 | firefox-ios/Client/Frontend/Settings/WebsiteDataManagement/WebsiteDataSearchResultsViewController.swift:260-264 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Duplicated block (33 lines × 2) BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:121— BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:121-153 | focus-ios/Deferred/ReadWriteLock.swift:117-149 — before extracting anything, compare `BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift` and `focus-ios/Deferred/ReadWriteLock.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (33 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:270— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:270-302 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:303-335 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (33 lines × 2) focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/OnboardingSearchWidgetView.swift:18— focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/OnboardingSearchWidgetView.swift:18-50 | focus-ios/Widgets/SearchWidgetView.swift:18-50 — before extracting anything, compare `focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/OnboardingSearchWidgetView.swift` and `focus-ios/Widgets/SearchWidgetView.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 44 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–15 lines × 2) BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:71— BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:71-85 | BrowserKit/Sources/VPNKit/KeychainVPNTokenStore.swift:42-54 — before extracting anything, compare `BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift` and `BrowserKit/Sources/VPNKit/KeychainVPNTokenStore.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (13–15 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:110— BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:110-122 | firefox-ios/Client/Application/WebServer.swift:148-162 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:110` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–15 lines × 2) firefox-ios/Client/Frontend/Reader/SchemeHandler/ReaderModeSchemeHandler.swift:135— firefox-ios/Client/Frontend/Reader/SchemeHandler/ReaderModeSchemeHandler.swift:135-147 | firefox-ios/Client/Frontend/Translations/SchemeHandler/TranslationsSchemeHandler.swift:131-145 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (12–13 lines × 2) firefox-ios/Client/Coordinators/Launch/LaunchCoordinator.swift:151— firefox-ios/Client/Coordinators/Launch/LaunchCoordinator.swift:151-163 | firefox-ios/Client/Frontend/Onboarding/Views/PrivacyPreferencesViewController.swift:245-256 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Coordinators/Launch/LaunchCoordinator.swift:151` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift:114— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift:114-125 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift:128-140 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewModel.swift:114` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (12–13 lines × 2) firefox-ios/Client/Frontend/Browser/BackForwardListAnimator.swift:87— firefox-ios/Client/Frontend/Browser/BackForwardListAnimator.swift:87-98 | firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetAnimator.swift:80-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/BackForwardListAnimator.swift:87` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–12 lines × 2) BrowserKit/Sources/TestKit/MockLogger.swift:28— BrowserKit/Sources/TestKit/MockLogger.swift:28-39 | firefox-ios/Client/Frontend/Autofill/LoginListViewModel.swift:79-89 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/TestKit/MockLogger.swift:28` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (11–12 lines × 2) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1031— firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1031-1042 | firefox-ios/Client/Coordinators/Library/LibraryCoordinator.swift:100-110 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1031` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (11–12 lines × 2) firefox-ios/Storage/SQL/BrowserSchema.swift:165— firefox-ios/Storage/SQL/BrowserSchema.swift:165-176 | firefox-ios/Storage/SQL/ReadingListSchema.swift:71-81 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once.
Duplicated block (7 lines × 3) firefox-ios/Client/Frontend/AuthenticationManager/SensitiveViewController.swift:108— firefox-ios/Client/Frontend/AuthenticationManager/SensitiveViewController.swift:108-114 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2291-2297 | firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheet.swift:249-255 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 3) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewController.swift:129— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewController.swift:129-135 | firefox-ios/Client/Frontend/Settings/AppearanceSettings/WallpaperSettings/v1/WallpaperSettingsViewController.swift:253-259 | firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:607-613 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewController.swift:129` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (7 lines × 3) firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:90— firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:90-96 | firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:109-115 | firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsEmptyView.swift:121-127 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 40 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:90` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:87` calls `configureLearnMoreButton` and `firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:106` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 3) firefox-ios/Client/Frontend/Settings/Main/Debug/InstallationDetailsSetting.swift:24— firefox-ios/Client/Frontend/Settings/Main/Debug/InstallationDetailsSetting.swift:24-28 | firefox-ios/Client/Frontend/Settings/Main/Debug/ResetInstallationHistorySetting.swift:26-30 | firefox-ios/Client/Frontend/Settings/Main/Debug/ResetTipsSetting.swift:17-23 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) firefox-ios/Client/Frontend/Settings/Main/About/LicenseAndAcknowledgementsSetting.swift:10— firefox-ios/Client/Frontend/Settings/Main/About/LicenseAndAcknowledgementsSetting.swift:10-14 | firefox-ios/Client/Frontend/Settings/Main/About/YourRightsSetting.swift:9-13 | firefox-ios/Client/Frontend/Settings/Main/Support/SendFeedbackSetting.swift:10-14 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (5 lines × 3) firefox-ios/Client/Telemetry/TelemetryWrapper.swift:1006— firefox-ios/Client/Telemetry/TelemetryWrapper.swift:1006-1010 | firefox-ios/Client/Telemetry/TelemetryWrapper.swift:1034-1038 | firefox-ios/Client/Telemetry/TelemetryWrapper.swift:1069-1073 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (13 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/LoginManager.shared.sys.mjs:93— firefox-ios/Client/Assets/CC_Script/LoginManager.shared.sys.mjs:93 · firefox-ios/Client/Assets/CC_Script/LoginManager.shared.sys.mjs:124 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (13 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1672— firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1672 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1749 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (13 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2620— firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2620 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2683 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (7 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:261— firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:261 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:268 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (7 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:283— firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:283 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:397 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (7 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:847— firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:847 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:854 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Dead file (~28 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/__firefox__.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~28 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentStart/__firefox__.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~28 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/NightModeAtDocumentStart/__firefox__.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Low contrast colour pair in CSS (2.7:1) firefox-ios/Client/Assets/CertError.css:45— `button` sets color: white on background-color: rgb(76, 158, 255) — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (2.7:1) firefox-ios/Client/Assets/NetError.css:51— `button` sets color: white on background-color: rgb(76, 158, 255) — 2.7:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
(anonymous)::_fillForm (cyclomatic 27) REDACTED:321— (anonymous)::_fillForm has cyclomatic complexity 27 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
(anonymous)::onFocusIn (cyclomatic 17) REDACTED:518— (anonymous)::onFocusIn has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
Floating branch dependency: fuzi — Dependency `fuzi` is declared in BrowserKit/Package.swift against branch `master` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
Floating branch dependency: gcdwebserver — Dependency `gcdwebserver` is declared in BrowserKit/Package.swift against branch `master` — the declaration pins no immutable point, so `swift package update` moves this dependency to whatever that branch holds at the time, which is code nobody reviewed. Pin it to a version requirement (`from:`, `.upToNextMajor(from:)`, `exact:`) or to a `revision:` commit SHA.
loadBergamot::genericPointerToWireType (cognitive 35) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1659— loadBergamot::genericPointerToWireType has cognitive complexity 35 (threshold 15). Drivers by points: if/else 14 (26 pts), ternaries 2 (6 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 17). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
loadBergamot::__embind_register_std_string::toWireType (cognitive 20) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2578— loadBergamot::__embind_register_std_string::toWireType has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (11 pts), boolean chains 5, loops 2 (4 pts) (nesting depth added 4). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
(anonymous)::_fillForm (cognitive 27) REDACTED:321— (anonymous)::_fillForm has cognitive complexity 27 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 11 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous)::_getFormFields (cognitive 20) REDACTED:126— (anonymous)::_getFormFields has cognitive complexity 20 (threshold 15). Drivers by points: if/else 13 (16 pts), boolean chains 2, loops 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
BookmarksViewController.tableView (cognitive 17) firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:537— BookmarksViewController.tableView has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 5 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BookmarksViewController.tableView (cognitive 17) firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:584— BookmarksViewController.tableView has cognitive complexity 17 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
D4 · Code Duplication· Edited copy of a member (35 corresponding lines) · ×2
Edited copy of a member (35 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:128— BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:128-166 | firefox-ios/Client/Application/WebServerUtil.swift:55-95 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (35 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift:92— firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift:92-126 | firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/GroupedFolderHierarchyFetcher.swift:163-207 — These two members are one piece of code written twice and then edited apart: 35 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Members sharing a duplicated core (7 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (7 members, 50+ identical tokens) firefox-ios/Client/Frontend/Autofill/Address/AddressAutoFillBottomSheetView.swift:18— firefox-ios/Client/Frontend/Autofill/Address/AddressAutoFillBottomSheetView.swift:18-43 | firefox-ios/Client/Frontend/Autofill/Address/AddressScrollView.swift:23-51 | firefox-ios/Client/Frontend/Autofill/AutofillFooterView.swift:35-53 | firefox-ios/Client/Frontend/Autofill/AutofillHeaderView.swift:35-67 | firefox-ios/Client/Frontend/Autofill/LoginAutofillView.swift:17-43 | firefox-ios/Client/Frontend/Autofill/LoginCellView.swift:27-63 | firefox-ios/Client/Frontend/Autofill/LoginListView.swift:22-44 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
Members sharing a duplicated core (7 members, 50+ identical tokens) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsView.swift:30— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsView.swift:30-56 | firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:43-77 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSectionHeader.swift:15-34 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSettingsEmptyView.swift:22-41 | firefox-ios/Client/Frontend/Autofill/CreditCard/ViewComponents/CreditCardAutofillToggle.swift:43-70 | firefox-ios/Client/Frontend/Autofill/CreditCard/ViewComponents/CreditCardInputField.swift:89-121 | firefox-ios/Client/Frontend/Autofill/CreditCard/ViewComponents/RemoveCardButton.swift:37-84 — These 7 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 7 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 7 times.
D4 · Code Duplication· Members sharing a duplicated core (5 members, 50+ identical tokens) · ×2
Members sharing a duplicated core (5 members, 50+ identical tokens) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1145— firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1145-1166 | firefox-ios/Client/Coordinators/Launch/LaunchCoordinator.swift:334-353 | firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:151-170 | firefox-ios/Client/Coordinators/SettingsCoordinator.swift:301-320 | firefox-ios/Client/Coordinators/TabTray/RemoteTabsCoordinator.swift:73-92 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
Members sharing a duplicated core (5 members, 50+ identical tokens) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewController.swift:123— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewController.swift:123-135 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:4964-4987 | firefox-ios/Client/Frontend/Settings/AppearanceSettings/WallpaperSettings/v1/WallpaperSettingsViewController.swift:238-259 | firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:599-613 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:295-334 — These 5 members share a duplicated core: a run of at least 50 identical tokens appears in every one of them. That run is NOT broken out as duplicated-block rows below — it is what admitted this row, and the blocks below cover only the part of it that clears the block floor, so they understate the correspondence. Read the members as one construct written 5 times. The repair is at the members' grain — factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Extracting the individual blocks below is not the same fix: it leaves every body in place and the next edit still has to be made 5 times.
D4 · Code Duplication· Edited copy of a member (50 corresponding lines) · ×2
Edited copy of a member (50 corresponding lines) firefox-ios/Client/Telemetry/FxSuggestTelemetry.swift:27— firefox-ios/Client/Telemetry/FxSuggestTelemetry.swift:27-76 | firefox-ios/Client/Telemetry/FxSuggestTelemetry.swift:78-134 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (50 corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/LayoutManager/TabsSectionManager.swift:88— firefox-ios/Client/Frontend/Browser/Tabs/LayoutManager/TabsSectionManager.swift:88-137 | firefox-ios/Client/Frontend/Browser/Tabs/LayoutManager/TabsSectionManager.swift:143-199 — These two members are one piece of code written twice and then edited apart: 50 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (43 corresponding lines) · ×2
Edited copy of a member (43 corresponding lines) firefox-ios/Client/Application/UITestAppDelegate.swift:137— firefox-ios/Client/Application/UITestAppDelegate.swift:137-179 | firefox-ios/Client/Application/UITestAppDelegate.swift:181-227 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (43 corresponding lines) firefox-ios/Client/Frontend/TabContentsScripts/LoginsHelper.swift:269— firefox-ios/Client/Frontend/TabContentsScripts/LoginsHelper.swift:269-319 | firefox-ios/Client/Frontend/TabContentsScripts/LoginsHelper.swift:321-363 — These two members are one piece of code written twice and then edited apart: 43 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (24 corresponding lines) · ×2
Edited copy of a member (24 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:94— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewModel.swift:94-117 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewModel.swift:116-139 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (24 corresponding lines) firefox-ios/Client/Frontend/Browser/Toolbars/Models/AddressToolbarContainerModel.swift:363— firefox-ios/Client/Frontend/Browser/Toolbars/Models/AddressToolbarContainerModel.swift:363-386 | firefox-ios/Client/Frontend/Browser/Toolbars/Models/NavigationToolbarContainerModel.swift:85-108 — These two members are one piece of code written twice and then edited apart: 24 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (29 corresponding lines) · ×2
Edited copy of a member (29 corresponding lines) firefox-ios/Storage/Rust/RustPlaces.swift:142— firefox-ios/Storage/Rust/RustPlaces.swift:142-170 | firefox-ios/Storage/Rust/RustPlaces.swift:202-234 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (29 corresponding lines) firefox-ios/Client/Frontend/Settings/Summarize/SummarizeSettingsViewController.swift:53— firefox-ios/Client/Frontend/Settings/Summarize/SummarizeSettingsViewController.swift:53-82 | firefox-ios/Client/Frontend/Settings/Translation/TranslationSettingsViewController.swift:30-58 — These two members are one piece of code written twice and then edited apart: 29 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (27 corresponding lines) · ×2
Edited copy of a member (27 corresponding lines) BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:92— BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:92-119 | BrowserKit/Sources/VPNKit/KeychainVPNTokenStore.swift:61-87 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (27 corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift:178— firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift:178-204 | firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift:206-232 — These two members are one piece of code written twice and then edited apart: 27 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (25 corresponding lines) · ×2
Edited copy of a member (25 corresponding lines) firefox-ios/Storage/SQL/SQLiteReadingList.swift:79— firefox-ios/Storage/SQL/SQLiteReadingList.swift:79-110 | firefox-ios/Storage/SQL/SQLiteReadingList.swift:126-150 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
Edited copy of a member (25 corresponding lines) firefox-ios/Storage/Rust/RustAutofill.swift:113— firefox-ios/Storage/Rust/RustAutofill.swift:113-137 | firefox-ios/Storage/Rust/RustAutofill.swift:214-239 — These two members are one piece of code written twice and then edited apart: 25 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 15+ corresponding lines) · ×2
Edited copies of one member (3 members, 15+ corresponding lines) firefox-ios/Client/Frontend/Browser/MainMenu/Redux/MainMenuState.swift:278— firefox-ios/Client/Frontend/Browser/MainMenu/Redux/MainMenuState.swift:278-292 | firefox-ios/Client/Frontend/Browser/MainMenu/Redux/MainMenuState.swift:294-310 | firefox-ios/Client/Frontend/Browser/MainMenu/Redux/MainMenuState.swift:312-328 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 15+ corresponding lines) firefox-ios/Client/TabManagement/TabContentScriptManager.swift:32— firefox-ios/Client/TabManagement/TabContentScriptManager.swift:32-46 | firefox-ios/Client/TabManagement/TabContentScriptManager.swift:48-62 | firefox-ios/Client/TabManagement/TabContentScriptManager.swift:64-78 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 12+ corresponding lines) · ×2
Edited copies of one member (7 members, 12+ corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountDeviceConstellation.swift:84— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountDeviceConstellation.swift:84-95 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountDeviceConstellation.swift:138-150 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:213-226 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:235-246 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:288-300 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:303-314 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountManager.swift:317-330 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
Edited copies of one member (7 members, 12+ corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:197— firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:197-213 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabPeekViewController.swift:48-59 | firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:428-445 | firefox-ios/Client/Frontend/Microsurvey/Survey/View/MicrosurveyViewController.swift:161-172 | firefox-ios/Client/Frontend/NativeErrorPage/NativeErrorPageViewController.swift:258-269 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:132-149 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift:305-316 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 13+ corresponding lines) · ×2
Edited copies of one member (3 members, 13+ corresponding lines) firefox-ios/Client/Frontend/Home/PrivateHome/PrivateHomepageViewController.swift:85— firefox-ios/Client/Frontend/Home/PrivateHome/PrivateHomepageViewController.swift:85-97 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:46-62 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift:132-147 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 13+ corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Places.swift:754— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Places.swift:754-766 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Places.swift:768-780 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Places.swift:782-794 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 10+ corresponding lines) · ×2
Edited copies of one member (4 members, 10+ corresponding lines) firefox-ios/Client/Frontend/Onboarding/Views/PrivacyPolicyViewController.swift:19— firefox-ios/Client/Frontend/Onboarding/Views/PrivacyPolicyViewController.swift:19-31 | firefox-ios/Client/Frontend/Reader/View/ReaderModeStyleViewController.swift:67-83 | firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:51-66 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionDetailsViewController.swift:80-89 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
Edited copies of one member (4 members, 10+ corresponding lines) firefox-ios/Client/Frontend/Browser/LegacyClipboardBarDisplayHandlerDelegate.swift:42— firefox-ios/Client/Frontend/Browser/LegacyClipboardBarDisplayHandlerDelegate.swift:42-53 | firefox-ios/Client/Frontend/Home/Homepage/SectionHeader/LabelButtonHeaderView.swift:154-163 | firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheet.swift:353-362 | firefox-ios/Client/Telemetry/GleanUsageReporting.swift:106-118 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 3+ corresponding lines) · ×2
Edited copies of one member (3 members, 3+ corresponding lines) BrowserKit/Sources/Shared/InternalURL.swift:28— BrowserKit/Sources/Shared/InternalURL.swift:28-30 | BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalURL.swift:24-29 | focus-ios/Blockzilla/Utilities/InternalURL.swift:14-16 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Edited copies of one member (3 members, 3+ corresponding lines) firefox-ios/Client/Frontend/Settings/SiriSettingsViewController.swift:76— firefox-ios/Client/Frontend/Settings/SiriSettingsViewController.swift:76-82 | focus-ios/Blockzilla/Settings/Controller/SettingsViewController.swift:689-691 | focus-ios/Blockzilla/Siri/SiriFavoriteViewController.swift:260-262 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 3 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
Duplicated block (37 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:8— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:8-44 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:8-44 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/ArgumentProcessor.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (37 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift:46— firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift:46-82 | firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/GroupedFolderHierarchyFetcher.swift:114-150 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift:46` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also register a scope-exit action (a `defer`-style statement) that runs when the function holding them returns: moved into a called unit it would run when THAT unit returns instead — before the caller uses what it releases — so keep the registration at the call site and extract only the work around it, or have the extracted unit hand the resource back for the caller to register.
Duplicated block (24–25 lines × 2) BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:95— BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:95-119 | BrowserKit/Sources/VPNKit/KeychainVPNTokenStore.swift:64-87 — before extracting anything, compare `BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift` and `BrowserKit/Sources/VPNKit/KeychainVPNTokenStore.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 52 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/AppAttestKit/KeychainAppAttestKeyIDStore.swift:95` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24–25 lines × 2) firefox-ios/Client/Frontend/Browser/Toolbars/Redux/BrowserActionsBuilder.swift:110— firefox-ios/Client/Frontend/Browser/Toolbars/Redux/BrowserActionsBuilder.swift:110-134 | firefox-ios/Client/Frontend/Browser/Toolbars/Redux/NavigationActionsBuilder.swift:123-146 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Toolbars/Redux/BrowserActionsBuilder.swift:110` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (19–20 lines × 2) firefox-ios/Client/TabManagement/TabManagerImplementation.swift:455— firefox-ios/Client/TabManagement/TabManagerImplementation.swift:455-473 | firefox-ios/Client/TabManagement/TabManagerImplementation.swift:492-511 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/TabManagement/TabManagerImplementation.swift:455` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (19–20 lines × 2) firefox-ios/Client/Telemetry/FxSuggestTelemetry.swift:58— firefox-ios/Client/Telemetry/FxSuggestTelemetry.swift:58-76 | firefox-ios/Client/Telemetry/FxSuggestTelemetry.swift:115-134 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Telemetry/FxSuggestTelemetry.swift:58` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (18 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:304— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:304-321 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:337-354 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (18 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:88— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:88-105 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:93-110 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (13–14 lines × 2) BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:22— BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:22-34 | firefox-ios/Client/Frontend/Onboarding/Models/OnboardingKitCardInfoModel.swift:25-38 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:22` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (13–14 lines × 2) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+TabScrollHandlerDelegate.swift:106— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+TabScrollHandlerDelegate.swift:106-119 | firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:188-200 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+TabScrollHandlerDelegate.swift:106` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeMLPAEndpointSetting.swift:27— firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeMLPAEndpointSetting.swift:27-37 | firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeRSServerSetting.swift:28-38 | firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeVPNEndpointSetting.swift:27-37 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeMLPAEndpointSetting.swift:27` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 3) firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:77— firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:77-87 | firefox-ios/Client/Frontend/Browser/Toasts/DownloadToast.swift:135-145 | firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift:61-71 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift` and `firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (10–11 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/WKNavigationHandler.swift:165— BrowserKit/Sources/WebEngine/WKWebview/WKNavigationHandler.swift:165-174 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:1684-1694 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (10–11 lines × 2) firefox-ios/CredentialProvider/Cells/EmptyPlaceholderCell.swift:25— firefox-ios/CredentialProvider/Cells/EmptyPlaceholderCell.swift:25-34 | firefox-ios/CredentialProvider/Cells/NoSearchResultCell.swift:24-34 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/CredentialProvider/Cells/EmptyPlaceholderCell.swift:25` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `firefox-ios/CredentialProvider/Cells/EmptyPlaceholderCell.swift:35` calls `constraint` and `firefox-ios/CredentialProvider/Cells/NoSearchResultCell.swift:35` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (10 lines × 3) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:153— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:153-162 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:166-175 | firefox-ios/Client/Experiments/RecordedNimbusContext.swift:97-106 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (10 lines × 3) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift:11— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAKeychain/FxAKeychain.swift:11-20 | SampleBrowser/SampleBrowser/Dependency/DependencyHelper.swift:26-35 | SampleComponentLibraryApp/SampleComponentLibraryApp/Dependency/DependencyHelper.swift:26-35 — before extracting anything, compare `SampleBrowser/SampleBrowser/Dependency/DependencyHelper.swift` and `SampleComponentLibraryApp/SampleComponentLibraryApp/Dependency/DependencyHelper.swift` as WHOLE FILES: 100% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (7–8 lines × 2) firefox-ios/Client/Coordinators/Router/URLScanner.swift:32— firefox-ios/Client/Coordinators/Router/URLScanner.swift:32-38 | focus-ios/Blockzilla/NavigationPath.swift:34-41 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (7–8 lines × 2) firefox-ios/Client/Frontend/PasswordManagement/AddCredentialViewController.swift:112— firefox-ios/Client/Frontend/PasswordManagement/AddCredentialViewController.swift:112-118 | firefox-ios/Client/Frontend/Settings/PasswordDetailViewController.swift:88-95 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (6 lines × 4) BrowserKit/Sources/Shared/InstallationUtils.swift:9— BrowserKit/Sources/Shared/InstallationUtils.swift:9-15 | MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:154-159 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:167-172 | firefox-ios/Client/Experiments/RecordedNimbusContext.swift:98-103 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (6 lines × 4) firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:270— firefox-ios/Client/Frontend/TrackingProtection/BlockedTrackersTableController.swift:270-275 | firefox-ios/Client/Frontend/TrackingProtection/CertificatesViewController.swift:293-298 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionDetailsViewController.swift:219-224 | firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionViewController.swift:592-597 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (5 lines × 6) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsView.swift:52— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsView.swift:52-56 | firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:73-77 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSectionHeader.swift:30-34 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSettingsEmptyView.swift:37-41 | firefox-ios/Client/Frontend/Autofill/CreditCard/ViewComponents/CreditCardAutofillToggle.swift:66-70 | firefox-ios/Client/Frontend/Autofill/CreditCard/ViewComponents/CreditCardInputField.swift:117-121 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsView.swift:52` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsView.swift:49` calls `fetchAddresses` and `firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSettingsEmptyView.swift:34` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (5 lines × 6) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:70— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:70-74 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSectionHeader.swift:27-31 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSettingsEmptyView.swift:34-38 | firefox-ios/Client/Frontend/Autofill/CreditCard/ViewComponents/CreditCardAutofillToggle.swift:63-67 | firefox-ios/Client/Frontend/Autofill/CreditCard/ViewComponents/CreditCardInputField.swift:114-118 | firefox-ios/Client/Frontend/Autofill/CreditCard/ViewComponents/RemoveCardButton.swift:67-71 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 6 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 6 times. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:70` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillToggle.swift:67` calls `modifier`, `ToggleStyle` and `firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardSettingsEmptyView.swift:33` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Sync-over-async blocking REDACTED:42— `query_github` is async and calls urllib.request.urlopen — a blocking call inside async code stalls the event loop — every other task on it waits for as long as it runs.
Sync-over-async blocking firefox-ios/Client/VPN/VPNGuardian.swift:162— `sleep` is async and calls sleep — a blocking call inside async code stalls the cooperative pool's thread — one per core — and every task scheduled on it for as long as it runs.
Duplicated block (31 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/FormAutofill.sys.mjs:235— firefox-ios/Client/Assets/CC_Script/FormAutofill.sys.mjs:235 · firefox-ios/Client/Assets/CC_Script/FormAutofill.sys.mjs:281 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (31 lines × 2 locations) REDACTED:1159— REDACTED:1159 · REDACTED:1280 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:520— firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:520 · firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:564 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (24 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:223— firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:223 · firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:248 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (10 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2556— firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2556 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2658 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (10 lines × 2 locations) REDACTED:4129— REDACTED:4129 · REDACTED:4154 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (8 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:326— firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:326 · firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:463 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (8 lines × 2 locations) REDACTED:4455— REDACTED:4455 · REDACTED:4495 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Dead file (~235 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~235 LoC) focus-ios/Blockzilla/MetadataHelper.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~63 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/LanguageSampleExtractor.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/TranslationsEntrypoint.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~63 LoC) focus-ios/Blockzilla/Ads.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~58 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/Ads.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~58 LoC) focus-ios/Blockzilla/Lib/TrackingProtection/Assets/preload.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~44 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/FocusHelper.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~44 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentStart/ContextMenu.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~17 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/BackgroundAudioHelper.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~17 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentEnd/ErrorPage.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
AC3 · Page structure· Heading level jumps from h1 to h3 · ×1
Heading level jumps from h1 to h3 REDACTED:16— Skipping heading levels breaks the document outline assistive tech relies on. Don't jump levels — increase by at most one.
Low contrast colour pair in CSS (3.6:1) focus-ios/Blockzilla/UIComponents/ErrorPage/errorPage.html:33— `button` sets color: white on background-color: #0a84ff — 3.6:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
Low contrast colour pair in CSS (4.4:1) firefox-ios/Client/Assets/CertError.css:68— `#advancedButton` sets color: #777 on background-color: white — 4.4:1, below the 4.5:1 WCAG AA minimum for normal text. Darken or lighten one of them.
AC6 · Visual & motion safety· Focus outline removed in CSS without a · ×1
Focus outline removed in CSS without a :focus replacement firefox-ios/Client/Frontend/UserContent/UserScripts/AddressFormManager/AddressFormManager.css:56— `label input` sets the outline to none/0 and no visible :focus / :focus-visible style for that element replaces it in this stylesheet, so a keyboard user cannot see where focus is. Draw a focus ring (outline, box-shadow or border) under :focus-visible.
TelemetryWrapper.gleanRecordEvent (cyclomatic 244) firefox-ios/Client/Telemetry/TelemetryWrapper.swift:771— TelemetryWrapper.gleanRecordEvent has cyclomatic complexity 244 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
BrowserSchema.update (cyclomatic 104) firefox-ios/Storage/SQL/BrowserSchema.swift:969— BrowserSchema.update has cyclomatic complexity 104 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NewPasswordModel.sys.makeRuleset (cyclomatic 55) firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:130— NewPasswordModel.sys.makeRuleset has cyclomatic complexity 55 (threshold 15). Most of this is not in the body itself: 2 of the 55 points are its own statements and the rest belongs to 18 function items inside it that branch (hasLabelMatchingRegex, nextInputIsConfirmy, formHasMultipleVisibleInput, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
constructor (cyclomatic 39) REDACTED:1082— constructor has cyclomatic complexity 39 (threshold 15). Most of this is not in the body itself: 3 of the 39 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 1404, a function literal at line 1218, addRootElements, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
bergamot-translator.loadBergamot (cyclomatic 36) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:5— bergamot-translator.loadBergamot has cyclomatic complexity 36 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This shape REPEATS in the file: one other method here (bergamot-translator.loadBergamot::genericPointerToWireType) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
LoginFormState._getFormFields (cyclomatic 34) firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:622— LoginFormState._getFormFields has cyclomatic complexity 34 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PasswordRulesParser.sys._canonicalizedPropertyValues (cyclomatic 33) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:167— PasswordRulesParser.sys._canonicalizedPropertyValues has cyclomatic complexity 33 (threshold 15). Of this number, 30 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BrowserViewController.webView (cyclomatic 31) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:970— BrowserViewController.webView has cyclomatic complexity 31 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BrowserViewController.handleNavigation (cyclomatic 30) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2801— BrowserViewController.handleNavigation has cyclomatic complexity 30 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
OpenSearchParser.parse (cyclomatic 28) focus-ios/Blockzilla/Search/OpenSearchParser.swift:26— OpenSearchParser.parse has cyclomatic complexity 28 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AddressToolbarContainerModel.== (cyclomatic 28) firefox-ios/Client/Frontend/Browser/Toolbars/Models/AddressToolbarContainerModel.swift:400— AddressToolbarContainerModel.== has cyclomatic complexity 28 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
MainMenuCoordinator.handleDestination (cyclomatic 27) firefox-ios/Client/Frontend/Browser/MainMenu/MainMenuCoordinator.swift:113— MainMenuCoordinator.handleDestination has cyclomatic complexity 27 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SettingsViewController.tableView (cyclomatic 26) focus-ios/Blockzilla/Settings/Controller/SettingsViewController.swift:314— SettingsViewController.tableView has cyclomatic complexity 26 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TrackingProtectionStats.install (cyclomatic 26) firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js:11— TrackingProtectionStats.install has cyclomatic complexity 26 (threshold 15). Most of this is not in the body itself: 1 of the 26 points is its own statement and the rest belongs to 6 function items inside it that branch (injectStatsTracking, sendMessage, a function literal at line 166, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
BrowserViewController.readerModeBar (cyclomatic 25) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+ReaderMode.swift:195— BrowserViewController.readerModeBar has cyclomatic complexity 25 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BrowserViewController.webView (cyclomatic 25) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:622— BrowserViewController.webView has cyclomatic complexity 25 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
RouteBuilder.makeRoute (cyclomatic 24) firefox-ios/Client/Coordinators/Router/RouteBuilder.swift:38— RouteBuilder.makeRoute has cyclomatic complexity 24 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
findCreditCardSelectOption (cyclomatic 24) firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:1002— findCreditCardSelectOption has cyclomatic complexity 24 (threshold 15). Of this number, 22 points are the body's own statements and 2 belong to 5 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ToolbarElement.== (cyclomatic 23) BrowserKit/Sources/ToolbarKit/ToolbarElement.swift:161— ToolbarElement.== has cyclomatic complexity 23 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
SearchViewController.tableView (cyclomatic 23) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:646— SearchViewController.tableView has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
translations-document.sys.updateElement::merge (cyclomatic 23) REDACTED:6101— translations-document.sys.updateElement::merge has cyclomatic complexity 23 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This is NOT this file's highest cyclomatic complexity: TranslationsDocument.constructor (cyclomatic 38) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
SearchViewController.tableView (cyclomatic 22) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:487— SearchViewController.tableView has cyclomatic complexity 22 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FxAWebViewModel.handleRemote (cyclomatic 21) firefox-ios/RustFxA/FxAWebViewModel.swift:339— FxAWebViewModel.handleRemote has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
ErrorPageHandler.responseForErrorWebPage (cyclomatic 21) firefox-ios/Client/Frontend/InternalSchemeHandler/ErrorPageHelper.swift:222— ErrorPageHandler.responseForErrorWebPage has cyclomatic complexity 21 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: ErrorPageHelper.swift.cfErrorToName (cyclomatic 83) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
FormAutofillCreditCardSection.isValidSection (cyclomatic 21) firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs:527— FormAutofillCreditCardSection.isValidSection has cyclomatic complexity 21 (threshold 15). To reduce it, separate the branches: extract each independent case into its own named function so the top-level body reads as a short sequence of named decisions.
_parsePhoneFields (cyclomatic 21) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:244— _parsePhoneFields has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_parseStreetAddressFields (cyclomatic 21) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:370— _parseStreetAddressFields has cyclomatic complexity 21 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
NavigationPath.init (cyclomatic 20) focus-ios/Blockzilla/NavigationPath.swift:14— NavigationPath.init has cyclomatic complexity 20 (threshold 15). Of this number, 16 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
SearchViewController.getCellForSection (cyclomatic 20) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:776— SearchViewController.getCellForSection has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
findAddressSelectOption (cyclomatic 20) firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:882— findAddressSelectOption has cyclomatic complexity 20 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BrowserViewController.viewWillTransition (cyclomatic 19) focus-ios/Blockzilla/BrowserViewController.swift:1013— BrowserViewController.viewWillTransition has cyclomatic complexity 19 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
UITestAppDelegate.getProfile (cyclomatic 19) firefox-ios/Client/Application/UITestAppDelegate.swift:27— UITestAppDelegate.getProfile has cyclomatic complexity 19 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BrowserCoordinator.handle (cyclomatic 19) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:408— BrowserCoordinator.handle has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
SearchSettingsTableViewController.tableView (cyclomatic 19) firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:220— SearchSettingsTableViewController.tableView has cyclomatic complexity 19 (threshold 15). To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Where every arm is uniform — the same kind of value, with no behaviour of its own — a table keyed by the case is the shorter form; wherever the arms carry different data or different behaviour, keep them as cases, because collapsing those trades an explicit, reviewable set of cases for nothing.
URLBar.updateViews (cyclomatic 19) focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:857— URLBar.updateViews has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
bergamot-translator.loadBergamot::genericPointerToWireType (cyclomatic 19) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1659— bergamot-translator.loadBergamot::genericPointerToWireType has cyclomatic complexity 19 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top. This shape REPEATS in the file: one other method here (bergamot-translator.loadBergamot) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
BrowserViewController.webController (cyclomatic 18) focus-ios/Blockzilla/BrowserViewController.swift:1790— BrowserViewController.webController has cyclomatic complexity 18 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BrowserViewController.updateUIAfterTabSelection (cyclomatic 18) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:4824— BrowserViewController.updateUIAfterTabSelection has cyclomatic complexity 18 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: BrowserViewController.performNotificationHandler (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
SettingsViewController.tableView (cyclomatic 18) focus-ios/Blockzilla/Settings/Controller/SettingsViewController.swift:489— SettingsViewController.tableView has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
SearchViewController.tableView (cyclomatic 18) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:700— SearchViewController.tableView has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
_parseCreditCardNameFields (cyclomatic 18) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:647— _parseCreditCardNameFields has cyclomatic complexity 18 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
#submitForContentTranslation (cyclomatic 18) REDACTED:2982— #submitForContentTranslation has cyclomatic complexity 18 (threshold 15). Of this number, 10 points are the body's own statements and 8 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
DefaultWKEngineWebView.setupObservers (cyclomatic 17) BrowserKit/Sources/WebEngine/WKWebview/WKEngineWebView.swift:204— DefaultWKEngineWebView.setupObservers has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
ExtensionUtils.extractSharedItem (cyclomatic 17) firefox-ios/Storage/ExtensionUtils.swift:41— ExtensionUtils.extractSharedItem has cyclomatic complexity 17 (threshold 15). Of this number, 14 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
LoginsHelper.userContentController (cyclomatic 17) firefox-ios/Client/Frontend/TabContentsScripts/LoginsHelper.swift:134— LoginsHelper.userContentController has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
BrowserViewController.handleURL (cyclomatic 17) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2561— BrowserViewController.handleURL has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages. This is NOT this file's highest cyclomatic complexity: BrowserViewController.performNotificationHandler (cyclomatic 20) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
TabManagerMiddleware.resolveTabPanelViewActions (cyclomatic 17) firefox-ios/Client/Frontend/Browser/Tabs/Middleware/TabManagerMiddleware.swift:205— TabManagerMiddleware.resolveTabPanelViewActions has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
String.encode (cyclomatic 17) focus-ios/Blockzilla/Extensions/StringExtensions.swift:61— String.encode has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
FormAutofillHandler.adaptFieldMaxLength (cyclomatic 17) REDACTED:893— FormAutofillHandler.adaptFieldMaxLength has cyclomatic complexity 17 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
PasswordRulesParser.sys.parsePasswordRules (cyclomatic 17) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:621— PasswordRulesParser.sys.parsePasswordRules has cyclomatic complexity 17 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
LoginsHelper.window.__firefox__.includeOnce("LoginsHelper")::onFocusIn (cyclomatic 17) REDACTED:518— LoginsHelper.window.__firefox__.includeOnce("LoginsHelper")::onFocusIn has cyclomatic complexity 17 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BrowserViewController.configureGoogleLensTip (cyclomatic 16) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+ToolBarActionMenuDelegate.swift:96— BrowserViewController.configureGoogleLensTip has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
AutocompleteTextField.handleKeyCommand (cyclomatic 16) focus-ios/Blockzilla/UIComponents/AutocompleteTextField.swift:100— AutocompleteTextField.handleKeyCommand has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
URIFixup.getURL (cyclomatic 16) focus-ios/Blockzilla/Utilities/URIFixup.swift:8— URIFixup.getURL has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
FxAPairingURLParser.parse (cyclomatic 16) firefox-ios/Client/Coordinators/Router/FxAPairingURLParser.swift:15— FxAPairingURLParser.parse has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
TranslationPickerSettingsViewController.makeDataSource (cyclomatic 16) firefox-ios/Client/Frontend/Settings/Translation/TranslationPickerSettingsViewController.swift:193— TranslationPickerSettingsViewController.makeDataSource has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
AppDataUsageReportSetting.generateAppDataSummary (cyclomatic 16) firefox-ios/Client/Frontend/Settings/Main/Debug/AppDataUsageReportSetting.swift:34— AppDataUsageReportSetting.generateAppDataSummary has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
TranslationsDocument.#maybePrioritizeRequestsAndSubmitToScheduler (cyclomatic 16) REDACTED:3702— TranslationsDocument.#maybePrioritizeRequestsAndSubmitToScheduler has cyclomatic complexity 16 (threshold 15). Most of this is not in the body itself: 7 of the 16 points are its own statements and the rest belongs to one function literal inside it that branches (line 3726). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest. This is NOT this file's highest cyclomatic complexity: TranslationsDocument.constructor (cyclomatic 38) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
translations-document.sys.isNodeHidden (cyclomatic 16) REDACTED:5840— translations-document.sys.isNodeHidden has cyclomatic complexity 16 (threshold 15). To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators. This is NOT this file's highest cyclomatic complexity: TranslationsDocument.constructor (cyclomatic 38) is higher and carries no row of its own — it was excluded as a flat dispatcher (a long switch/match over independent cases: many branches, almost no nesting), which this dimension does not treat as a refactor obligation. It is named here so the ranking you see in this file is not mistaken for the whole of it; the excluded method is counted neither in this dimension's figures nor in its score.
create (cyclomatic 16) firefox-ios/Client/Assets/CC_Script/FieldScanner.sys.mjs:93— create has cyclomatic complexity 16 (threshold 15). To reduce it, split the body: these branches sit side by side rather than nested inside one another, so extracting each one on its own would leave a function per branch. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
_parseCreditCardExpiryFields (cyclomatic 16) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:535— _parseCreditCardExpiryFields has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
inferFieldInfo (cyclomatic 16) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:979— inferFieldInfo has cyclomatic complexity 16 (threshold 15). Of this number, 14 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
distance (cyclomatic 16) firefox-ios/Client/Assets/CC_Script/fathom.mjs:770— distance has cyclomatic complexity 16 (threshold 15). To reduce it, separate the cases: extract each independent branch into its own named function, and where the body has guards that only reject input, fold those into early returns at the top.
D10 · Test Quality· Test project verifies nothing · ×1
Test project verifies nothing: StoragePerfTests firefox-ios/firefox-ios-tests/Tests/StoragePerfTests/StoragePerfTests.swift:11— No conventional assertion call was detected in 1 of 1 tests in `StoragePerfTests` — the project as a whole, not one method. Two things look like this: verification that happens indirectly (an approval/verifier harness or BDD step methods), or a suite that genuinely checks nothing. If it is the latter, this project passes unconditionally and cannot fail.
TodoComment repeated across 25 files firefox-ios/Client/TabManagement/TabWebView.swift:37— The identical TodoComment appears in 25 files (26 occurrences) — almost certainly one boilerplate line from a single migration or decision, not 26 independent debts. Fix the systemic cause once rather than file-by-file. Text: "// TODO: FXIOS-13097 This is a work around until we can leverage isolated deinits". Source code is not a task system: track the cleanup where tasks live. (Every occurrence still counts toward the score and metrics.)
TelemetryWrapper.gleanRecordEvent (cognitive 183) firefox-ios/Client/Telemetry/TelemetryWrapper.swift:771— TelemetryWrapper.gleanRecordEvent has cognitive complexity 183 (threshold 15). Drivers by points: if/else 85 (129 pts), boolean chains 53, match/switch 1 (nesting depth added 44). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserSchema.update (cognitive 141) firefox-ios/Storage/SQL/BrowserSchema.swift:969— BrowserSchema.update has cognitive complexity 141 (threshold 15). Drivers by points: if/else 69 (106 pts), boolean chains 35 (nesting depth added 37). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LoginsHelper.window.__firefox__.includeOnce("LoginsHelper") (cognitive 98) REDACTED:17— LoginsHelper.window.__firefox__.includeOnce("LoginsHelper") has cognitive complexity 98 (threshold 15). Drivers by points: if/else 49 (59 pts), boolean chains 28, ternaries 6 (7 pts), loops 2, error handling 1, match/switch 1 (nesting depth added 11). None of this is in the body itself: all 98 points belong to 16 function items inside it that branch (a function literal at line 321, a function literal at line 126, onFocusIn, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
constructor (cognitive 80) REDACTED:1082— constructor has cognitive complexity 80 (threshold 15). Drivers by points: if/else 24 (58 pts), loops 7 (11 pts), ternaries 3 (5 pts), boolean chains 3, match/switch 1 (2 pts), other 1 (nesting depth added 41). Most of this is not in the body itself: 3 of the 80 points are its own statements and the rest belongs to 7 function items inside it that branch (a function literal at line 1404, a function literal at line 1218, a function literal at line 1337, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
NewPasswordModel.sys.makeRuleset (cognitive 67) firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:130— NewPasswordModel.sys.makeRuleset has cognitive complexity 67 (threshold 15). Drivers by points: if/else 29 (45 pts), boolean chains 14, loops 6 (7 pts), ternaries 1 (nesting depth added 17). Most of this is not in the body itself: 1 of the 67 points is its own statement and the rest belongs to 18 function items inside it that branch (nextInputIsConfirmy, formHasMultipleVisibleInput, hasLabelMatchingRegex, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
_getFormFields (cognitive 52) firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:622— _getFormFields has cognitive complexity 52 (threshold 15). Drivers by points: if/else 26 (40 pts), boolean chains 5, ternaries 4 (5 pts), loops 1 (2 pts) (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SearchViewController.tableView (cognitive 46) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:646— SearchViewController.tableView has cognitive complexity 46 (threshold 15). Drivers by points: if/else 13 (43 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 31). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
translations-document.sys.updateElement::merge (cognitive 46) REDACTED:6101— translations-document.sys.updateElement::merge has cognitive complexity 46 (threshold 15). Drivers by points: if/else 15 (35 pts), loops 5 (8 pts), boolean chains 3 (nesting depth added 23). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PasswordRulesParser.sys._canonicalizedPropertyValues (cognitive 44) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:167— PasswordRulesParser.sys._canonicalizedPropertyValues has cognitive complexity 44 (threshold 15). Drivers by points: if/else 23 (35 pts), loops 6, boolean chains 3 (nesting depth added 12). Of this number, 40 points are the body's own statements and 4 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bergamot-translator.loadBergamot (cognitive 44) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:5— bergamot-translator.loadBergamot has cognitive complexity 44 (threshold 15). Drivers by points: if/else 282 (374 pts), loops 56 (67 pts), boolean chains 64, ternaries 25 (39 pts), match/switch 7 (8 pts), error handling 3 (4 pts) (nesting depth added 119). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (bergamot-translator.loadBergamot::stringToUTF8Array) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
BrowserViewController.webView (cognitive 41) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:970— BrowserViewController.webView has cognitive complexity 41 (threshold 15). Drivers by points: if/else 19 (27 pts), boolean chains 14 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
OpenSearchParser.parse (cognitive 39) focus-ios/Blockzilla/Search/OpenSearchParser.swift:26— OpenSearchParser.parse has cognitive complexity 39 (threshold 15). Drivers by points: if/else 17 (27 pts), boolean chains 11, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AppDataUsageReportSetting.generateAppDataSummary (cognitive 38) firefox-ios/Client/Frontend/Settings/Main/Debug/AppDataUsageReportSetting.swift:34— AppDataUsageReportSetting.generateAppDataSummary has cognitive complexity 38 (threshold 15). Drivers by points: if/else 9 (23 pts), loops 5 (10 pts), error handling 1 (4 pts), boolean chains 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MetadataHelper.buildRuleSet.<returned closure> (cognitive 35) focus-ios/Blockzilla/MetadataHelper.js:28— MetadataHelper.buildRuleSet.<returned closure> has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 4 (12 pts), boolean chains 1 (nesting depth added 22). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
buildRuleSet (cognitive 35) focus-ios/Blockzilla/MetadataHelper.js:27— buildRuleSet has cognitive complexity 35 (threshold 15). Drivers by points: if/else 8 (22 pts), loops 4 (12 pts), boolean chains 1 (nesting depth added 22). None of this is in the body itself: all 35 points belong to one function literal inside it that branches (line 28). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
findCreditCardSelectOption (cognitive 35) firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:1002— findCreditCardSelectOption has cognitive complexity 35 (threshold 15). Drivers by points: if/else 7 (18 pts), loops 4 (8 pts), boolean chains 4, ternaries 4, match/switch 1 (nesting depth added 15). Of this number, 33 points are the body's own statements and 2 belong to 5 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SettingsViewController.tableView (cognitive 34) focus-ios/Blockzilla/Settings/Controller/SettingsViewController.swift:314— SettingsViewController.tableView has cognitive complexity 34 (threshold 15). Drivers by points: ternaries 6 (18 pts), if/else 10 (14 pts), boolean chains 1, match/switch 1 (nesting depth added 16). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
_parsePhoneFields (cognitive 34) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:244— _parsePhoneFields has cognitive complexity 34 (threshold 15). Drivers by points: if/else 9 (21 pts), loops 4 (7 pts), boolean chains 6 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_parseStreetAddressFields (cognitive 34) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:370— _parseStreetAddressFields has cognitive complexity 34 (threshold 15). Drivers by points: if/else 10 (24 pts), loops 3 (5 pts), boolean chains 4, match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
String.encode (cognitive 33) focus-ios/Blockzilla/Extensions/StringExtensions.swift:61— String.encode has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (22 pts), loops 5 (9 pts), boolean chains 2 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
findAddressSelectOption (cognitive 33) firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:882— findAddressSelectOption has cognitive complexity 33 (threshold 15). Drivers by points: if/else 8 (19 pts), loops 4 (9 pts), boolean chains 4, match/switch 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
#submitForContentTranslation (cognitive 33) REDACTED:2982— #submitForContentTranslation has cognitive complexity 33 (threshold 15). Drivers by points: if/else 11 (25 pts), boolean chains 4, error handling 1 (2 pts), loops 1, other 1 (nesting depth added 15). Most of this is not in the body itself: 15 of the 33 points are its own statements and the rest belongs to 3 function literals inside it that branch (lines 3038, 3062, 2989). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
FormAutofillHandler.adaptFieldMaxLength (cognitive 32) REDACTED:893— FormAutofillHandler.adaptFieldMaxLength has cognitive complexity 32 (threshold 15). Drivers by points: if/else 9 (19 pts), ternaries 1 (5 pts), boolean chains 4, match/switch 1 (3 pts), loops 1 (nesting depth added 16). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ExtensionUtils.extractSharedItem (cognitive 31) firefox-ios/Storage/ExtensionUtils.swift:41— ExtensionUtils.extractSharedItem has cognitive complexity 31 (threshold 15). Drivers by points: if/else 12 (25 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 14). Of this number, 28 points are the body's own statements and 3 belong to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TPStatsBlocklists.load (cognitive 30) firefox-ios/Client/ContentBlocker/TrackingProtectionPageStats.swift:170— TPStatsBlocklists.load has cognitive complexity 30 (threshold 15). Drivers by points: if/else 6 (18 pts), ternaries 2 (6 pts), loops 2 (3 pts), error handling 1 (2 pts), boolean chains 1 (nesting depth added 18). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SearchViewController.handleKeyCommands (cognitive 30) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:1043— SearchViewController.handleKeyCommands has cognitive complexity 30 (threshold 15). Drivers by points: if/else 15 (28 pts), boolean chains 1, match/switch 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserViewController.readerModeBar (cognitive 29) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+ReaderMode.swift:195— BrowserViewController.readerModeBar has cognitive complexity 29 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 8, ternaries 2 (4 pts), match/switch 1 (nesting depth added 10). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
install (cognitive 29) firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js:11— install has cognitive complexity 29 (threshold 15). Drivers by points: if/else 20 (23 pts), boolean chains 5, error handling 1 (nesting depth added 3). None of this is in the body itself: all 29 points belong to 16 function items inside it that branch (a function literal at line 166, injectStatsTracking, sendMessage, …). The named helpers are already separate functions; the literals' work cannot be called, reviewed or tested from outside this body. To reduce it, move the named helpers out of the body to the enclosing scope and lift each literal's work into a named function there, so each is measured, reviewed and tested on its own, and reduce whichever one then reads as the largest.
(anonymous).FormatNumber (cognitive 28) REDACTED:145— (anonymous).FormatNumber has cognitive complexity 28 (threshold 15). Drivers by points: if/else 10 (24 pts), ternaries 1 (2 pts), boolean chains 1, loops 1 (nesting depth added 15). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AutocompleteTextField.handleKeyCommand (cognitive 27) focus-ios/Blockzilla/UIComponents/AutocompleteTextField.swift:100— AutocompleteTextField.handleKeyCommand has cognitive complexity 27 (threshold 15). Drivers by points: if/else 13 (26 pts), match/switch 1 (nesting depth added 13). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
AddressToolbarContainerModel.== (cognitive 27) firefox-ios/Client/Frontend/Browser/Toolbars/Models/AddressToolbarContainerModel.swift:400— AddressToolbarContainerModel.== has cognitive complexity 27 (threshold 15). Drivers by points: boolean chains 27. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
AddressRecord.#computeTelFields (cognitive 27) REDACTED:77— AddressRecord.#computeTelFields has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (24 pts), boolean chains 3 (nesting depth added 16). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
FormAutofillSection.groupFields (cognitive 27) firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs:218— FormAutofillSection.groupFields has cognitive complexity 27 (threshold 15). Drivers by points: if/else 8 (20 pts), loops 2 (4 pts), boolean chains 3 (nesting depth added 14). Of this number, 26 points are the body's own statements and 1 belongs to one function literal inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generateLabelMap (cognitive 26) firefox-ios/Client/Assets/CC_Script/LabelUtils.sys.mjs:179— generateLabelMap has cognitive complexity 26 (threshold 15). Drivers by points: if/else 10 (21 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
(anonymous).FindMetaDataForRegion (cognitive 26) REDACTED:97— (anonymous).FindMetaDataForRegion has cognitive complexity 26 (threshold 15). Drivers by points: if/else 6 (20 pts), loops 2 (4 pts), boolean chains 2 (nesting depth added 16). To reduce it, flatten the nesting: this score is depth rather than breadth — most of its points come from checks stacked inside one another, so the work sits several levels in. Invert each enclosing check into an early exit (a return, or the language's equivalent) so the happy path stays at one level, and where a level cannot be exited early, lift the block it encloses into its own named function.
BrowserViewController.webView (cognitive 25) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:622— BrowserViewController.webView has cognitive complexity 25 (threshold 15). Drivers by points: if/else 16 (17 pts), boolean chains 8 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TPStatsBlocklists.load (cognitive 25) focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift:125— TPStatsBlocklists.load has cognitive complexity 25 (threshold 15). Drivers by points: if/else 4 (12 pts), ternaries 2 (6 pts), loops 2 (3 pts), boolean chains 2, error handling 1 (2 pts) (nesting depth added 14). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
URLBar.updateViews (cognitive 25) focus-ios/Blockzilla/UIComponents/URLBar/URLBar.swift:857— URLBar.updateViews has cognitive complexity 25 (threshold 15). Drivers by points: ternaries 7 (13 pts), if/else 5 (8 pts), boolean chains 3, match/switch 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserViewController.configureGoogleLensTip (cognitive 24) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+ToolBarActionMenuDelegate.swift:96— BrowserViewController.configureGoogleLensTip has cognitive complexity 24 (threshold 15). Drivers by points: if/else 6 (13 pts), boolean chains 5, ternaries 1 (3 pts), match/switch 1 (2 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LoginsHelper.userContentController (cognitive 24) firefox-ios/Client/Frontend/TabContentsScripts/LoginsHelper.swift:134— LoginsHelper.userContentController has cognitive complexity 24 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 5 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserViewController.updateUIAfterTabSelection (cognitive 23) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:4824— BrowserViewController.updateUIAfterTabSelection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 15 (16 pts), boolean chains 6, ternaries 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
NavigationPath.init (cognitive 23) focus-ios/Blockzilla/NavigationPath.swift:14— NavigationPath.init has cognitive complexity 23 (threshold 15). Drivers by points: if/else 13 (15 pts), boolean chains 8 (nesting depth added 2). Of this number, 19 points are the body's own statements and 4 belong to 2 function items inside it that branch. To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
ActionViewController.configurationItems (cognitive 23) focus-ios/OpenInFocus/ActionViewController.swift:55— ActionViewController.configurationItems has cognitive complexity 23 (threshold 15). Drivers by points: if/else 10 (17 pts), boolean chains 3, loops 2 (3 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
QRCodeViewController.metadataOutput (cognitive 23) firefox-ios/Client/Frontend/Browser/QRCodeViewController.swift:367— QRCodeViewController.metadataOutput has cognitive complexity 23 (threshold 15). Drivers by points: if/else 9 (15 pts), boolean chains 4, match/switch 1 (4 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ScreenshotHelper.takeScreenshot (cognitive 23) firefox-ios/Client/Frontend/Browser/ScreenshotHelper.swift:40— ScreenshotHelper.takeScreenshot has cognitive complexity 23 (threshold 15). Drivers by points: if/else 14 (21 pts), boolean chains 2 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SearchViewController.tableView (cognitive 23) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:487— SearchViewController.tableView has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (16 pts), boolean chains 4, ternaries 1 (2 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
SearchViewController.getCellForSection (cognitive 23) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:776— SearchViewController.getCellForSection has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), ternaries 1 (3 pts), boolean chains 2, match/switch 1 (nesting depth added 11). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
URL.publicSuffixFromHost (cognitive 23) focus-ios/Blockzilla/Extensions/URLExtensions.swift:363— URL.publicSuffixFromHost has cognitive complexity 23 (threshold 15). Drivers by points: if/else 12 (17 pts), boolean chains 3, ternaries 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_parseCreditCardNameFields (cognitive 23) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:647— _parseCreditCardNameFields has cognitive complexity 23 (threshold 15). Drivers by points: if/else 7 (11 pts), boolean chains 6, loops 4 (6 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
identifyCountryCode (cognitive 23) firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:737— identifyCountryCode has cognitive complexity 23 (threshold 15). Drivers by points: if/else 8 (17 pts), loops 2 (3 pts), boolean chains 2, ternaries 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ToolbarElement.== (cognitive 22) BrowserKit/Sources/ToolbarKit/ToolbarElement.swift:161— ToolbarElement.== has cognitive complexity 22 (threshold 15). Drivers by points: boolean chains 22. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BrowserProfile.pollCommands (cognitive 22) firefox-ios/Providers/Profile.swift:610— BrowserProfile.pollCommands has cognitive complexity 22 (threshold 15). Drivers by points: if/else 6 (12 pts), boolean chains 5, match/switch 1 (3 pts), loops 1 (2 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ErrorPageHandler.responseForErrorWebPage (cognitive 22) firefox-ios/Client/Frontend/InternalSchemeHandler/ErrorPageHelper.swift:222— ErrorPageHandler.responseForErrorWebPage has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 10 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
LegacyWebViewController.webView (cognitive 22) focus-ios/Blockzilla/Modules/WebView/LegacyWebViewController.swift:488— LegacyWebViewController.webView has cognitive complexity 22 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 3 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
bergamot-translator.loadBergamot::stringToUTF8Array (cognitive 22) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:238— bergamot-translator.loadBergamot::stringToUTF8Array has cognitive complexity 22 (threshold 15). Drivers by points: if/else 10 (20 pts), boolean chains 1, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body. This shape REPEATS in the file: one other method here (bergamot-translator.loadBergamot) has the same decision points, in the same order, at the same nesting depths — so this is one pattern written twice rather than two separate problems. Splitting this body alone leaves the other exactly as it is. Where these are variations on one operation, the change that clears both is the shared one: lift the common shape into a single routine the variants call, parameterised by whatever genuinely differs between them, and keep in each method only the part that is not shared.
computeFillingValue (cognitive 22) REDACTED:775— computeFillingValue has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (16 pts), boolean chains 4, match/switch 1, other 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
#submitForAttributeTranslation (cognitive 22) REDACTED:2786— #submitForAttributeTranslation has cognitive complexity 22 (threshold 15). Drivers by points: if/else 7 (17 pts), boolean chains 2, error handling 1 (2 pts), loops 1 (nesting depth added 11). Most of this is not in the body itself: 7 of the 22 points are its own statements and the rest belongs to 2 function literals inside it that branch (lines 2809, 2833). The decisions are inside those literals, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literals' work into a named function or method at the enclosing scope and have each literal call it, then reduce whichever part then reads as the largest.
RustSyncManager.doRegisterSyncEngines (cognitive 21) firefox-ios/Providers/RustSyncManager.swift:421— RustSyncManager.doRegisterSyncEngines has cognitive complexity 21 (threshold 15). Drivers by points: if/else 5 (16 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 12). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserViewController.webView (cognitive 21) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:1287— BrowserViewController.webView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 11 (19 pts), boolean chains 2 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TPAccessoryInfo.tableView (cognitive 21) firefox-ios/Client/Frontend/Settings/TPAccessoryInfo.swift:103— TPAccessoryInfo.tableView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 16 (21 pts) (nesting depth added 5). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
SettingsViewController.tableView (cognitive 21) focus-ios/Blockzilla/Settings/Controller/SettingsViewController.swift:489— SettingsViewController.tableView has cognitive complexity 21 (threshold 15). Drivers by points: if/else 12 (19 pts), boolean chains 1, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
FormAutofillHandler.fillFields (cognitive 21) REDACTED:452— FormAutofillHandler.fillFields has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (18 pts), boolean chains 2, loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TranslationsDocument.#ensureMutationUpdateCallbackIsRegistered (cognitive 21) REDACTED:1902— TranslationsDocument.#ensureMutationUpdateCallbackIsRegistered has cognitive complexity 21 (threshold 15). Drivers by points: if/else 8 (14 pts), loops 5 (6 pts), boolean chains 1 (nesting depth added 7). Most of this is not in the body itself: 3 of the 21 points are its own statements and the rest belongs to one function literal inside it that branches (line 1922). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
FirefoxURLBuilder.findTextInItems (cognitive 20) BrowserKit/Sources/ActionExtensionKit/FirefoxURLBuilding.swift:88— FirefoxURLBuilder.findTextInItems has cognitive complexity 20 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 2 (3 pts), match/switch 1 (3 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
CodeUsageDetector.collect (cognitive 20) Dangerfile.swift:806— CodeUsageDetector.collect has cognitive complexity 20 (threshold 15). Drivers by points: if/else 5 (13 pts), boolean chains 4, loops 2 (3 pts) (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FxAWebViewModel.handleRemote (cognitive 20) firefox-ios/RustFxA/FxAWebViewModel.swift:339— FxAWebViewModel.handleRemote has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (17 pts), boolean chains 2, match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BrowserCoordinator.showTabTray (cognitive 20) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1168— BrowserCoordinator.showTabTray has cognitive complexity 20 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 4, ternaries 1 (2 pts) (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhotonActionSheetCell.configure (cognitive 20) focus-ios/Blockzilla/Menu/Old/PhotonActionSheetCell.swift:106— PhotonActionSheetCell.configure has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (14 pts), ternaries 3 (4 pts), boolean chains 1, match/switch 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SearchSettingsViewController.tableView (cognitive 20) focus-ios/Blockzilla/Settings/Controller/SearchSettingsViewController.swift:86— SearchSettingsViewController.tableView has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (16 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ASSearchEngineIconDataFetcher.populateIconData (cognitive 20) firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEngineIconDataFetcher.swift:59— ASSearchEngineIconDataFetcher.populateIconData has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 2 (3 pts), boolean chains 2 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PasswordRulesParser.sys._parsePasswordRequiredOrAllowedPropertyValue (cognitive 20) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:409— PasswordRulesParser.sys._parsePasswordRequiredOrAllowedPropertyValue has cognitive complexity 20 (threshold 15). Drivers by points: if/else 8 (17 pts), boolean chains 2, loops 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TranslationsDocument.#subdivideNodeForContentTranslations (cognitive 20) REDACTED:2503— TranslationsDocument.#subdivideNodeForContentTranslations has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (15 pts), loops 1 (3 pts), boolean chains 1, match/switch 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
create (cognitive 20) firefox-ios/Client/Assets/CC_Script/FieldScanner.sys.mjs:93— create has cognitive complexity 20 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 4, other 2, error handling 1, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
inferFieldInfo (cognitive 20) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:979— inferFieldInfo has cognitive complexity 20 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 5 (nesting depth added 5). Of this number, 18 points are the body's own statements and 2 belong to 3 function literals inside it that branch. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
distance (cognitive 20) firefox-ios/Client/Assets/CC_Script/fathom.mjs:770— distance has cognitive complexity 20 (threshold 15). Drivers by points: if/else 7 (9 pts), ternaries 3 (5 pts), loops 4, boolean chains 2 (nesting depth added 4). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserViewController.viewWillTransition (cognitive 19) focus-ios/Blockzilla/BrowserViewController.swift:1013— BrowserViewController.viewWillTransition has cognitive complexity 19 (threshold 15). Drivers by points: boolean chains 11, if/else 6, ternaries 2. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
UITestAppDelegate.getProfile (cognitive 19) firefox-ios/Client/Application/UITestAppDelegate.swift:27— UITestAppDelegate.getProfile has cognitive complexity 19 (threshold 15). Drivers by points: if/else 18, boolean chains 1. To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
TabManagerImplementation.updateSelectedTabAfterRemovalOf (cognitive 19) firefox-ios/Client/TabManagement/TabManagerImplementation.swift:548— TabManagerImplementation.updateSelectedTabAfterRemovalOf has cognitive complexity 19 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 2, ternaries 1 (2 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
SearchViewController.tableView (cognitive 19) firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:700— SearchViewController.tableView has cognitive complexity 19 (threshold 15). Drivers by points: ternaries 8 (16 pts), if/else 1 (2 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
BrowserViewController.handleURL (cognitive 19) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2561— BrowserViewController.handleURL has cognitive complexity 19 (threshold 15). Drivers by points: if/else 8 (10 pts), boolean chains 9 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
sync_acorn_icons.sort_icons_by_size (cognitive 19) sync_acorn_icons.py:125— sync_acorn_icons.sort_icons_by_size has cognitive complexity 19 (threshold 15). Drivers by points: if/else 5 (15 pts), loops 3 (4 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormAutofillHandler.addressTransformer (cognitive 19) REDACTED:1120— FormAutofillHandler.addressTransformer has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (13 pts), ternaries 1 (3 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
parsePasswordRules (cognitive 19) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:621— parsePasswordRules has cognitive complexity 19 (threshold 15). Drivers by points: if/else 6 (8 pts), ternaries 2 (6 pts), boolean chains 2, match/switch 1 (2 pts), loops 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
MenuTableViewHelper.cellForRowAt (cognitive 18) BrowserKit/Sources/MenuKit/MenuTableViewHelper.swift:54— MenuTableViewHelper.cellForRowAt has cognitive complexity 18 (threshold 15). Drivers by points: if/else 11 (17 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FxAWebViewModel.setupFirstPage (cognitive 18) firefox-ios/RustFxA/FxAWebViewModel.swift:192— FxAWebViewModel.setupFirstPage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (16 pts), match/switch 1 (2 pts) (nesting depth added 11). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserViewController.webController (cognitive 18) focus-ios/Blockzilla/BrowserViewController.swift:1790— BrowserViewController.webController has cognitive complexity 18 (threshold 15). Drivers by points: boolean chains 10, if/else 7, match/switch 1. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
URIFixup.getURL (cognitive 18) focus-ios/Blockzilla/Utilities/URIFixup.swift:8— URIFixup.getURL has cognitive complexity 18 (threshold 15). Drivers by points: if/else 9 (12 pts), boolean chains 5, ternaries 1 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
SensitiveViewController.handleNotifications (cognitive 18) firefox-ios/Client/Frontend/AuthenticationManager/SensitiveViewController.swift:47— SensitiveViewController.handleNotifications has cognitive complexity 18 (threshold 15). Drivers by points: if/else 8 (15 pts), boolean chains 2, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
HomepageHeaderCell.observeQuickAnswersTip (cognitive 18) firefox-ios/Client/Frontend/Home/Homepage/Header/HomepageHeaderCell.swift:178— HomepageHeaderCell.observeQuickAnswersTip has cognitive complexity 18 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, match/switch 1 (2 pts), loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
FormAutofillHandler.telTransformer (cognitive 18) REDACTED:1169— FormAutofillHandler.telTransformer has cognitive complexity 18 (threshold 15). Drivers by points: if/else 12 (16 pts), boolean chains 2 (nesting depth added 4). Of this number, 17 points are the body's own statements and 1 belongs to one function item inside it that branches. To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
fathom.isVisible (cognitive 18) firefox-ios/Client/Assets/CC_Script/fathom.mjs:496— fathom.isVisible has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 4, ternaries 2 (4 pts), loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
acquirePort::onmessage (cognitive 18) REDACTED:5058— acquirePort::onmessage has cognitive complexity 18 (threshold 15). Drivers by points: if/else 6 (11 pts), loops 2 (6 pts), match/switch 1 (nesting depth added 9). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
TabContentBlocker.userContentController (cognitive 17) firefox-ios/Client/ContentBlocker/TabContentBlocker+ContentScript.swift:13— TabContentBlocker.userContentController has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 4, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
BrowserCoordinator.coordinatorHandleWindowEvent (cognitive 17) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1701— BrowserCoordinator.coordinatorHandleWindowEvent has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (14 pts), boolean chains 2, match/switch 1 (nesting depth added 7). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RelayController.generateRelayMask (cognitive 17) firefox-ios/Client/Frontend/Browser/RelayController.swift:237— RelayController.generateRelayMask has cognitive complexity 17 (threshold 15). Drivers by points: if/else 5 (9 pts), boolean chains 4, error handling 2 (4 pts) (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LoginDataSource.tableView (cognitive 17) firefox-ios/Client/Frontend/PasswordManagement/LoginDataSource.swift:48— LoginDataSource.tableView has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (12 pts), boolean chains 3, ternaries 1 (2 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TranslationsMiddleware.handleTappingOnTranslateButton (cognitive 17) firefox-ios/Client/Frontend/Translations/TranslationsMiddleware.swift:192— TranslationsMiddleware.handleTappingOnTranslateButton has cognitive complexity 17 (threshold 15). Drivers by points: if/else 11 (13 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition, and where an else follows a branch that already returns, drop the trailing else and let the rest of the body continue at one level.
PhotonActionSheet.applyTheme (cognitive 17) firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheet.swift:279— PhotonActionSheet.applyTheme has cognitive complexity 17 (threshold 15). Drivers by points: ternaries 5 (9 pts), if/else 7 (8 pts) (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
PhotonActionSheetViewModel.getViewHeader (cognitive 17) firefox-ios/Client/Frontend/Widgets/PhotonActionSheet/PhotonActionSheetViewModel.swift:79— PhotonActionSheetViewModel.getViewHeader has cognitive complexity 17 (threshold 15). Drivers by points: if/else 8 (16 pts), match/switch 1 (nesting depth added 8). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
scrape_plugins.downloadEngines (cognitive 17) REDACTED:77— scrape_plugins.downloadEngines has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (13 pts), loops 2 (3 pts), boolean chains 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
sync_acorn_icons.download_icons_and_save_in_assets (cognitive 17) sync_acorn_icons.py:92— sync_acorn_icons.download_icons_and_save_in_assets has cognitive complexity 17 (threshold 15). Drivers by points: loops 4 (10 pts), if/else 2 (6 pts), boolean chains 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
CreditCardRuleset.sys.isRadioWithCreditCardText (cognitive 17) firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:553— CreditCardRuleset.sys.isRadioWithCreditCardText has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (14 pts), loops 1 (2 pts), boolean chains 1 (nesting depth added 9). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
TranslationsDocument.#prioritizeQueuedContentElements (cognitive 17) REDACTED:3871— TranslationsDocument.#prioritizeQueuedContentElements has cognitive complexity 17 (threshold 15). Drivers by points: if/else 6 (9 pts), loops 3 (5 pts), match/switch 1 (2 pts), boolean chains 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_parseCreditCardExpiryFields (cognitive 17) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:535— _parseCreditCardExpiryFields has cognitive complexity 17 (threshold 15). Drivers by points: if/else 7 (10 pts), boolean chains 4, loops 3 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
DefaultTabDataStore.fetchWindowData (cognitive 16) BrowserKit/Sources/TabDataStore/TabDataStore.swift:55— DefaultTabDataStore.fetchWindowData has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), ternaries 1 (2 pts), error handling 1 (nesting depth added 7). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
LocationView.configureURLTextField (cognitive 16) BrowserKit/Sources/ToolbarKit/AddressToolbar/LocationView/LocationView.swift:536— LocationView.configureURLTextField has cognitive complexity 16 (threshold 15). Drivers by points: if/else 8 (9 pts), boolean chains 4, ternaries 3 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
DefaultWKEngineWebView.setupObservers (cognitive 16) BrowserKit/Sources/WebEngine/WKWebview/WKEngineWebView.swift:204— DefaultWKEngineWebView.setupObservers has cognitive complexity 16 (threshold 15). Drivers by points: boolean chains 8, if/else 8. To reduce it, name the conditions: bind each compound test to a well-named local or a small predicate function, so the body reads as a sequence of named decisions rather than a chain of operators.
BrowserViewController.webView (cognitive 16) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:22— BrowserViewController.webView has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 4 (nesting depth added 2). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
TelemetryWrapper.recordEnteredBackgroundPreferenceMetrics (cognitive 16) firefox-ios/Client/Telemetry/TelemetryWrapper.swift:234— TelemetryWrapper.recordEnteredBackgroundPreferenceMetrics has cognitive complexity 16 (threshold 15). Drivers by points: if/else 14 (15 pts), match/switch 1 (nesting depth added 1). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
MailtoLinkHandler.fetchMailSchemeProviders (cognitive 16) firefox-ios/Client/Frontend/Browser/MailtoLinkHandler.swift:26— MailtoLinkHandler.fetchMailSchemeProviders has cognitive complexity 16 (threshold 15). Drivers by points: if/else 11 (14 pts), boolean chains 2 (nesting depth added 3). To reduce it, split the body: most of this score is breadth rather than depth — checks laid out side by side rather than stacked — so group the statements between the checks into named steps and move each step into its own function. Some of it IS depth: where a check sits inside another whose only job is to reach it, merge the two into one condition.
SettingsTableViewController.dequeueCellFor (cognitive 16) firefox-ios/Client/Frontend/Settings/SettingsTableViewController.swift:1091— SettingsTableViewController.dequeueCellFor has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (15 pts), boolean chains 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ASSearchEngineUtilities.convertASSearchURLToOpenSearchURL (cognitive 16) firefox-ios/Client/Application/RemoteSettings/Application Services/ASSearchEngineUtilities.swift:77— ASSearchEngineUtilities.convertASSearchURLToOpenSearchURL has cognitive complexity 16 (threshold 15). Drivers by points: if/else 10 (12 pts), boolean chains 2, match/switch 1 (2 pts) (nesting depth added 3). To reduce it, split the body: this score is breadth rather than depth — many checks laid out side by side rather than nested inside one another, so inverting conditions into early returns has nothing left to flatten. Group the statements between the checks into named steps and move each step into its own function, so the body reads as a short sequence of named stages.
BrowserViewController.handleNavigation (cognitive 16) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:2801— BrowserViewController.handleNavigation has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (10 pts), boolean chains 5, match/switch 1 (nesting depth added 5). The drivers above price the dispatch low by construction — a dispatch is charged once however many cases it lists, while each branch inside an arm is charged in full — so most of this count is what the case bodies hold, and the arms are where it can be reduced. To reduce it, keep the dispatch but shrink the arms: move each non-trivial case body into its own named function (or onto the value being matched) so the dispatch reads one line per case, and group related cases into a sub-dispatch. Keep every case explicit, and make the behaviour for cases you do not list a deliberate choice rather than an accident.
RustKeychain.swift.deleteKeychainSecClass (cognitive 16) firefox-ios/Storage/RustKeychain.swift:378— RustKeychain.swift.deleteKeychainSecClass has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (12 pts), boolean chains 3, loops 1 (nesting depth added 5). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generate-replace-message-expressions.main (cognitive 16) monorepo-migration/generate-replace-message-expressions.py:34— generate-replace-message-expressions.main has cognitive complexity 16 (threshold 15). Drivers by points: ternaries 2 (8 pts), loops 3 (6 pts), if/else 1 (2 pts) (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
generate_screenshots.set_environment (cognitive 16) taskcluster/ffios_taskgraph/transforms/generate_screenshots.py:32— generate_screenshots.set_environment has cognitive complexity 16 (threshold 15). Drivers by points: loops 4 (12 pts), if/else 1 (3 pts), boolean chains 1 (nesting depth added 10). To reduce it, break up the iteration: give each loop body a named function, and split a multi-phase loop into one function per phase so no single body carries the whole pipeline.
Logic.transformRulesToMap (cognitive 16) firefox-ios/Client/Assets/CC_Script/LoginManager.shared.sys.mjs:363— Logic.transformRulesToMap has cognitive complexity 16 (threshold 15). Drivers by points: if/else 5 (11 pts), loops 2 (4 pts), boolean chains 1 (nesting depth added 8). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
ReaderMode.checkReadability (cognitive 16) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js:30— ReaderMode.checkReadability has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), ternaries 2 (4 pts), boolean chains 3 (nesting depth added 5). None of this is in the body itself: all 16 points belong to one function literal inside it that branches (line 31). The decisions are inside the literal, which nothing outside this body can call, review or test on its own, so splitting the enclosing body is not the move available here. To reduce it, lift the literal's work into a named function or method at the enclosing scope and have the literal call it, then reduce whichever part then reads as the largest.
clearFilledFields (cognitive 16) REDACTED:1278— clearFilledFields has cognitive complexity 16 (threshold 15). Drivers by points: if/else 4 (11 pts), ternaries 1 (4 pts), loops 1 (nesting depth added 10). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_parseAddressFields (cognitive 16) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:484— _parseAddressFields has cognitive complexity 16 (threshold 15). Drivers by points: if/else 7 (13 pts), boolean chains 2, loops 1 (nesting depth added 6). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
_parseCustomCharacterClass (cognitive 16) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:355— _parseCustomCharacterClass has cognitive complexity 16 (threshold 15). Drivers by points: if/else 6 (9 pts), boolean chains 5, loops 2 (nesting depth added 3). To reduce it, split the body into named stages: move each independent step or branch into its own named function so the body reads as a short sequence of named calls rather than one long body.
Change coupling clique: DarkTheme.swift, LightTheme.swift, PrivateModeTheme.swift, TabTrayPanelSwipePalette.swift BrowserKit/Sources/Common/Theming/DarkTheme.swift— 4 files — `BrowserKit/Sources/Common/Theming/DarkTheme.swift`, `BrowserKit/Sources/Common/Theming/LightTheme.swift`, `BrowserKit/Sources/Common/Theming/PrivateModeTheme.swift`, `firefox-ios/Client/Frontend/Browser/Tabs/Views/Animation/TabTrayPanelSwipePalette.swift` — all change together with no explicit dependency: a fully-connected co-change clique, not 6 separate couplings. They share one concern (thin parallel siblings over a common abstraction), so extract the shared part into ONE unit and the whole clique's coupling clears at once — you do not need to break each pair individually.
D4 · Code Duplication· Edited copy of a member (65 corresponding lines) · ×1
Edited copy of a member (65 corresponding lines) firefox-ios/CredentialProvider/CredentialPasscodeRequirementViewController.swift:64— firefox-ios/CredentialProvider/CredentialPasscodeRequirementViewController.swift:64-137 | firefox-ios/CredentialProvider/CredentialWelcomeViewController.swift:76-140 — These two members are one piece of code written twice and then edited apart: 65 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 47+ corresponding lines) · ×1
Edited copies of one member (3 members, 47+ corresponding lines) firefox-ios/Client/Frontend/Browser/Tabs/Views/EmptyPrivateTabsView.swift:82— firefox-ios/Client/Frontend/Browser/Tabs/Views/EmptyPrivateTabsView.swift:82-128 | firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentEmptyPrivateTabsView.swift:86-133 | firefox-ios/Client/Frontend/Browser/Tabs/Views/ExperimentRemoteTabsEmptyView.swift:106-152 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 47 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (48 corresponding lines) · ×1
Edited copy of a member (48 corresponding lines) BrowserKit/Sources/SummarizeKit/UI/InfoViewFormatter.swift:15— BrowserKit/Sources/SummarizeKit/UI/InfoViewFormatter.swift:15-62 | BrowserKit/Sources/SummarizeKit/UI/SummaryFormatter.swift:36-93 — These two members are one piece of code written twice and then edited apart: 48 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 44+ corresponding lines) · ×1
Edited copies of one member (3 members, 44+ corresponding lines) firefox-ios/Client/Telemetry/SearchTelemetry.swift:290— firefox-ios/Client/Telemetry/SearchTelemetry.swift:290-336 | firefox-ios/Client/Telemetry/SearchTelemetry.swift:339-398 | firefox-ios/Client/Telemetry/SearchTelemetry.swift:400-443 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 44 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 40+ corresponding lines) · ×1
Edited copies of one member (6 members, 40+ corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/SyncManager/SyncManagerTelemetry.swift:91— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/SyncManager/SyncManagerTelemetry.swift:91-130 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/SyncManager/SyncManagerTelemetry.swift:132-177 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/SyncManager/SyncManagerTelemetry.swift:179-218 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/SyncManager/SyncManagerTelemetry.swift:220-259 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/SyncManager/SyncManagerTelemetry.swift:261-300 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/SyncManager/SyncManagerTelemetry.swift:302-341 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 40 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (60 corresponding lines) · ×1
Edited copy of a member (60 corresponding lines) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift:179— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift:179-238 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusBuilder.swift:180-242 — These two members are one piece of code written twice and then edited apart: 60 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (41 corresponding lines) · ×1
Edited copy of a member (41 corresponding lines) firefox-ios/Client/Frontend/Settings/HomepageSettings/HomePageSettingViewController.swift:78— firefox-ios/Client/Frontend/Settings/HomepageSettings/HomePageSettingViewController.swift:78-118 | firefox-ios/Client/Frontend/Settings/NewTabContentSettingsViewController.swift:25-78 — These two members are one piece of code written twice and then edited apart: 41 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 26+ corresponding lines) · ×1
Edited copies of one member (3 members, 26+ corresponding lines) firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeMLPAEndpointSetting.swift:21— firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeMLPAEndpointSetting.swift:21-46 | firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeRSServerSetting.swift:20-46 | firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeVPNEndpointSetting.swift:21-46 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 26 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (42 corresponding lines) · ×1
Edited copy of a member (42 corresponding lines) firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift:41— firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/FolderHierarchyFetcher.swift:41-82 | firefox-ios/Client/Frontend/Library/Bookmarks/Utitlity/GroupedFolderHierarchyFetcher.swift:109-150 — These two members are one piece of code written twice and then edited apart: 42 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copy of a member (47 corresponding lines) · ×1
Edited copy of a member (47 corresponding lines) firefox-ios/Client/Helpers/MenuBuilderHelper.swift:42— firefox-ios/Client/Helpers/MenuBuilderHelper.swift:42-88 | firefox-ios/Client/Helpers/MenuBuilderHelper.swift:117-165 — These two members are one piece of code written twice and then edited apart: 47 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 28+ corresponding lines) · ×1
Edited copies of one member (3 members, 28+ corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:86— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:86-113 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:115-153 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:155-194 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 28 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (34 corresponding lines) · ×1
Edited copy of a member (34 corresponding lines) firefox-ios/Client/Frontend/Settings/Main/General/AdBlockerSetting.swift:38— firefox-ios/Client/Frontend/Settings/Main/General/AdBlockerSetting.swift:38-71 | firefox-ios/Client/Frontend/Settings/Main/Support/SendDataSetting.swift:58-91 — These two members are one piece of code written twice and then edited apart: 34 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 21+ corresponding lines) · ×1
Edited copies of one member (3 members, 21+ corresponding lines) MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Sync15/RustSyncTelemetryPing.swift:29— MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Sync15/RustSyncTelemetryPing.swift:29-49 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Sync15/RustSyncTelemetryPing.swift:74-94 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Sync15/RustSyncTelemetryPing.swift:246-268 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 27+ corresponding lines) · ×1
Edited copies of one member (4 members, 27+ corresponding lines) BrowserKit/Sources/ComponentLibrary/BottomSheet/BottomSheetViewController.swift:183— BrowserKit/Sources/ComponentLibrary/BottomSheet/BottomSheetViewController.swift:183-210 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardBottomSheet/CreditCardBottomSheetViewController.swift:421-449 | firefox-ios/Client/Frontend/Components/SaveLoginAlert.swift:187-213 | firefox-ios/Client/Frontend/Onboarding/Views/PrivacyPreferencesViewController.swift:305-333 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 27 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 18+ corresponding lines) · ×1
Edited copies of one member (3 members, 18+ corresponding lines) firefox-ios/Client/Frontend/Settings/ContentBlockerSettingViewController.swift:162— firefox-ios/Client/Frontend/Settings/ContentBlockerSettingViewController.swift:162-190 | firefox-ios/Client/Frontend/Settings/QuickAnswers/QuickAnswersSettingsViewController.swift:60-77 | firefox-ios/Client/Frontend/Settings/RelayMaskSettingsViewController.swift:52-76 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 18 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copy of a member (26 corresponding lines) · ×1
Edited copy of a member (26 corresponding lines) BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/MetadataFetcherHelper.swift:23— BrowserKit/Sources/WebEngine/WKWebview/Scripts/Metadata/MetadataFetcherHelper.swift:23-48 | firefox-ios/Client/Frontend/Browser/MetadataParserHelper.swift:18-43 — These two members are one piece of code written twice and then edited apart: 26 consecutive lines correspond almost exactly, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below — the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain — factor the shared implementation into one the two call with their differences as parameters or as an injected step, or, where the difference is systematic (an extra return value, one transport against another), generate one from the other. Left alone, the next edit has to be made twice and the two will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 15+ corresponding lines) · ×1
Edited copies of one member (4 members, 15+ corresponding lines) BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:259— BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:259-273 | BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:275-289 | BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:291-306 | BrowserKit/Sources/WebCompatReporterKit/WebCompatReportSheetViewController.swift:308-324 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 15 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 21+ corresponding lines) · ×1
Edited copies of one member (5 members, 21+ corresponding lines) BrowserKit/Sources/QuickAnswersKit/UI/QuickAnswersViewConfiguration.swift:42— BrowserKit/Sources/QuickAnswersKit/UI/QuickAnswersViewConfiguration.swift:42-64 | BrowserKit/Sources/QuickAnswersKit/UI/QuickAnswersViewConfiguration.swift:126-148 | BrowserKit/Sources/SummarizeKit/UI/SummarizeViewConfiguration.swift:71-97 | firefox-ios/Storage/Rust/UnencryptedAddressFields.swift:21-41 | focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/TermsOfServiceView.swift:134-156 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 21 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 23+ corresponding lines) · ×1
Edited copies of one member (5 members, 23+ corresponding lines) firefox-ios/Client/Extensions/UIAlertController+Extension.swift:13— firefox-ios/Client/Extensions/UIAlertController+Extension.swift:13-35 | firefox-ios/Client/Extensions/UIAlertController+Extension.swift:37-59 | firefox-ios/Client/Frontend/Browser/ThirdPartySearchAlerts.swift:23-46 | firefox-ios/Client/Frontend/Settings/ClearPrivateDataTableViewController.swift:274-296 | firefox-ios/Client/Frontend/Settings/ClearPrivateDataTableViewController.swift:298-320 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 23 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 11+ corresponding lines) · ×1
Edited copies of one member (4 members, 11+ corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:446— firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:446-457 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:459-469 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:551-561 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:605-621 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 11+ corresponding lines) · ×1
Edited copies of one member (3 members, 11+ corresponding lines) firefox-ios/Client/Frontend/Browser/Event Queue/EventQueue.swift:105— firefox-ios/Client/Frontend/Browser/Event Queue/EventQueue.swift:105-115 | firefox-ios/Client/Frontend/Browser/Event Queue/EventQueue.swift:119-130 | firefox-ios/Client/Frontend/Browser/Event Queue/EventQueue.swift:134-146 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 10+ corresponding lines) · ×1
Edited copies of one member (7 members, 10+ corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:413— firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:413-422 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:424-433 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:471-480 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:482-491 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:504-513 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:515-524 | firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:540-549 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 12+ corresponding lines) · ×1
Edited copies of one member (4 members, 12+ corresponding lines) firefox-ios/Client/Frontend/Browser/SearchEngines/Views/SearchEngineSelectionViewController.swift:31— firefox-ios/Client/Frontend/Browser/SearchEngines/Views/SearchEngineSelectionViewController.swift:31-46 | firefox-ios/Client/Frontend/Library/LibraryViewController/LibraryViewController.swift:61-72 | firefox-ios/Client/Frontend/Settings/AppearanceSettings/WallpaperSettings/v1/WallpaperSettingsViewController.swift:58-69 | firefox-ios/Client/Frontend/TrackingProtection/CertificatesViewController.swift:75-86 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 10+ corresponding lines) · ×1
Edited copies of one member (5 members, 10+ corresponding lines) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardTableViewController.swift:76— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardTableViewController.swift:76-86 | firefox-ios/Client/Frontend/Browser/TermsOfUse/View/TermsOfUseLinkViewController.swift:44-55 | firefox-ios/Client/Frontend/ContextualHint/ContextualHintViewController.swift:38-47 | firefox-ios/Client/Frontend/Onboarding/Views/OnboardingInstructionPopupViewController.swift:58-70 | firefox-ios/Client/Frontend/PasswordManagement/AddCredentialViewController.swift:90-99 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 10 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 12+ corresponding lines) · ×1
Edited copies of one member (3 members, 12+ corresponding lines) focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/CardBannerView.swift:70— focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/CardBannerView.swift:70-81 | focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/DefaultBrowserOnboardingView.swift:79-91 | focus-ios/BlockzillaPackage/Sources/Onboarding/SwiftUI Onboarding/DefaultBrowserOnboardingView.swift:93-106 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 12 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (5 members, 13+ corresponding lines) · ×1
Edited copies of one member (5 members, 13+ corresponding lines) firefox-ios/Client/Frontend/Browser/MainMenu/Views/MainMenuViewController.swift:429— firefox-ios/Client/Frontend/Browser/MainMenu/Views/MainMenuViewController.swift:429-443 | firefox-ios/Client/Frontend/Browser/SearchEngines/Views/SearchEngineSelectionViewController.swift:104-119 | firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportViewController.swift:88-100 | firefox-ios/Client/Frontend/PasswordGenerator/PasswordGeneratorViewController.swift:207-222 | firefox-ios/Client/Frontend/Settings/Translation/TranslationPickerSettingsViewController.swift:126-138 — These 5 members are one piece of code written 5 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 5 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 13+ corresponding lines) · ×1
Edited copies of one member (6 members, 13+ corresponding lines) firefox-ios/Client/Frontend/Settings/Main/General/AIControlsSetting.swift:19— firefox-ios/Client/Frontend/Settings/Main/General/AIControlsSetting.swift:19-31 | firefox-ios/Client/Frontend/Settings/Main/General/BrowsingSetting.swift:19-31 | firefox-ios/Client/Frontend/Settings/Main/General/SummarizeSetting.swift:19-31 | firefox-ios/Client/Frontend/Settings/Main/General/TranslationSetting.swift:30-43 | firefox-ios/Client/Frontend/Settings/Main/Privacy/AutofillPasswordSetting.swift:19-31 | firefox-ios/Client/Frontend/Settings/Main/Privacy/PasswordManagerSetting.swift:19-31 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 13 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (4 members, 9+ corresponding lines) · ×1
Edited copies of one member (4 members, 9+ corresponding lines) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:73— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:73-83 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:85-95 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:119-127 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+KeyCommands.swift:129-139 — These 4 members are one piece of code written 4 times and then edited apart: every two of them correspond over at least 9 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 4 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (6 members, 11+ corresponding lines) · ×1
Edited copies of one member (6 members, 11+ corresponding lines) firefox-ios/Client/Frontend/Home/Homepage/Merino/MerinoMiddleware.swift:62— firefox-ios/Client/Frontend/Home/Homepage/Merino/MerinoMiddleware.swift:62-72 | firefox-ios/Client/Frontend/Home/Homepage/Merino/MerinoMiddleware.swift:74-84 | firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSitesMiddleware.swift:148-158 | firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSitesMiddleware.swift:202-212 | firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSitesMiddleware.swift:235-245 | firefox-ios/Client/Frontend/Home/Homepage/TopSites/TopSitesMiddleware.swift:247-257 — These 6 members are one piece of code written 6 times and then edited apart: every two of them correspond over at least 11 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 6 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (3 members, 7+ corresponding lines) · ×1
Edited copies of one member (3 members, 7+ corresponding lines) firefox-ios/Client/Frontend/Settings/Translation/TranslationAddLanguageCell.swift:19— firefox-ios/Client/Frontend/Settings/Translation/TranslationAddLanguageCell.swift:19-25 | firefox-ios/Client/Frontend/Settings/Translation/TranslationLanguageCell.swift:21-28 | firefox-ios/Client/Frontend/Settings/Translation/TranslationToggleCell.swift:30-37 — These 3 members are one piece of code written 3 times and then edited apart: every two of them correspond over at least 7 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 3 times and the copies will drift further apart.
D4 · Code Duplication· Edited copies of one member (7 members, 4+ corresponding lines) · ×1
Edited copies of one member (7 members, 4+ corresponding lines) SampleComponentLibraryApp/SampleComponentLibraryApp/BottomSheet/BottomSheetChildViewController.swift:29— SampleComponentLibraryApp/SampleComponentLibraryApp/BottomSheet/BottomSheetChildViewController.swift:29-32 | SampleComponentLibraryApp/SampleComponentLibraryApp/Buttons/ButtonsViewController.swift:39-42 | SampleComponentLibraryApp/SampleComponentLibraryApp/CollapsibleCardView/CollapsibleCardViewViewController.swift:27-30 | SampleComponentLibraryApp/SampleComponentLibraryApp/ContextualHintView/ContextualHintViewViewController.swift:22-25 | SampleComponentLibraryApp/SampleComponentLibraryApp/FadeScrollViewComponent/FadeScrollViewViewController.swift:35-38 | SampleComponentLibraryApp/SampleComponentLibraryApp/Headers/HeadersViewViewController.swift:24-27 | SampleComponentLibraryApp/SampleComponentLibraryApp/ShadowCardView/ShadowCardViewViewController.swift:31-34 — These 7 members are one piece of code written 7 times and then edited apart: every two of them correspond over at least 4 lines, broken only by small local edits. Most of that correspondence is NOT reported as duplicated blocks below: the edits cut it into fragments and only the largest of them clear the block floor, so the rows below understate it. The repair is at the members' grain. Factor the shared implementation out once and have all of them call it with their differences as parameters or as an injected step, or, where the difference is systematic, generate them from one template. Left alone, the next edit has to be made 7 times and the copies will drift further apart.
Duplicated block (54–55 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:46— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:46-99 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:46-100 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/ArgumentProcessor.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (52–53 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:101— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:101-152 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/ArgumentProcessor.swift:102-154 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/ArgumentProcessor.swift` as WHOLE FILES: this scan already matched 4 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (38 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:41— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:41-78 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Sysctl.swift:41-78 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Sysctl.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Sysctl.swift` as WHOLE FILES: this scan already matched 3 separate duplicated blocks between them, totalling at least 63 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (35 lines × 2) BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:85— BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:85-119 | focus-ios/Deferred/ReadWriteLock.swift:81-115 — before extracting anything, compare `BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift` and `focus-ios/Deferred/ReadWriteLock.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 87 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (33–35 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:131— BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:131-163 | firefox-ios/Client/Application/WebServerUtil.swift:58-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:131` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (31 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/LayoutManager/TabsSectionManager.swift:96— firefox-ios/Client/Frontend/Browser/Tabs/LayoutManager/TabsSectionManager.swift:96-126 | firefox-ios/Client/Frontend/Browser/Tabs/LayoutManager/TabsSectionManager.swift:159-189 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `firefox-ios/Client/Frontend/Browser/Tabs/LayoutManager/TabsSectionManager.swift:127` calls `leadingInset` and `firefox-ios/Client/Frontend/Browser/Tabs/LayoutManager/TabsSectionManager.swift:190` does not — after which the two agree again for 4 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (29–31 lines × 2) firefox-ios/CredentialProvider/CredentialPasscodeRequirementViewController.swift:74— firefox-ios/CredentialProvider/CredentialPasscodeRequirementViewController.swift:74-102 | firefox-ios/CredentialProvider/CredentialWelcomeViewController.swift:90-120 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just after the matched lines, `firefox-ios/CredentialProvider/CredentialPasscodeRequirementViewController.swift:104` calls `constraint` and `firefox-ios/CredentialProvider/CredentialWelcomeViewController.swift:122` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (28 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/Policy/DataSchemePolicyDecider.swift:31— BrowserKit/Sources/WebEngine/WKWebview/Policy/DataSchemePolicyDecider.swift:31-58 | firefox-ios/Client/Frontend/Browser/WebView/WebViewNavigationHandler.swift:72-99 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (27 lines × 2) firefox-ios/Client/Frontend/HostingTableViewCell.swift:44— firefox-ios/Client/Frontend/HostingTableViewCell.swift:44-70 | firefox-ios/Client/Frontend/HostingTableViewSectionHeader.swift:45-71 — before extracting anything, compare `firefox-ios/Client/Frontend/HostingTableViewCell.swift` and `firefox-ios/Client/Frontend/HostingTableViewSectionHeader.swift` as WHOLE FILES: 91% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (24–26 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift:188— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift:188-213 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusBuilder.swift:193-216 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusBuilder.swift` as WHOLE FILES: 90% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 2 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusBuilder.swift:188` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (24 lines × 2) SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:81— SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift:81-104 | firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift:77-100 — before extracting anything, compare `SampleBrowser/SampleBrowser/UI/Components/PullRefreshView.swift` and `firefox-ios/Client/Frontend/Browser/WebView/PullRefreshView.swift` as WHOLE FILES: this scan already matched 12 separate duplicated blocks between them, totalling at least 164 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (22–23 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:123— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:123-145 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:121-142 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:123` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (22 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:152— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:152-173 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift:165-186 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusCreate.swift` as WHOLE FILES: this scan already matched 10 separate duplicated blocks between them, totalling at least 119 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusCreate.swift:152` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (21–22 lines × 2) firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:47— firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:47-68 | firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:359-379 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift:47` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (21 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReadabilityOperation.swift:81— BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReadabilityOperation.swift:81-101 | firefox-ios/Client/Frontend/Reader/ReadabilityService.swift:68-88 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReadabilityOperation.swift:81` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (19–20 lines × 5) firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1147— firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1147-1166 | firefox-ios/Client/Coordinators/Launch/LaunchCoordinator.swift:335-353 | firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:152-170 | firefox-ios/Client/Coordinators/SettingsCoordinator.swift:302-320 | firefox-ios/Client/Coordinators/TabTray/RemoteTabsCoordinator.swift:74-92 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1147` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `firefox-ios/Client/Coordinators/Browser/BrowserCoordinator.swift:1146` calls `postWindowEvent` and `firefox-ios/Client/Coordinators/Launch/LaunchCoordinator.swift:334` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (18–20 lines × 2) firefox-ios/Storage/Rust/RustLogins.swift:477— firefox-ios/Storage/Rust/RustLogins.swift:477-494 | firefox-ios/Storage/Rust/RustLogins.swift:527-546 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Storage/Rust/RustLogins.swift:477` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (13–19 lines × 2) BrowserKit/Sources/Shared/Functions.swift:248— BrowserKit/Sources/Shared/Functions.swift:248-266 | focus-ios/Blockzilla/UIComponents/AutocompleteTextField.swift:337-349 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `focus-ios/Blockzilla/UIComponents/AutocompleteTextField.swift:337` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 4) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:168— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:168-184 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:173-189 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:146-162 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift:189-205 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:168` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (17 lines × 3) firefox-ios/Client/Telemetry/SearchTelemetry.swift:296— firefox-ios/Client/Telemetry/SearchTelemetry.swift:296-312 | firefox-ios/Client/Telemetry/SearchTelemetry.swift:343-359 | firefox-ios/Client/Telemetry/SearchTelemetry.swift:404-420 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
Duplicated block (16–17 lines × 2) firefox-ios/Client/Frontend/Settings/Main/General/AdBlockerSetting.swift:47— firefox-ios/Client/Frontend/Settings/Main/General/AdBlockerSetting.swift:47-62 | firefox-ios/Client/Frontend/Settings/Main/Support/SendDataSetting.swift:68-84 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Settings/Main/General/AdBlockerSetting.swift:47` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (14–15 lines × 3) firefox-ios/Client/Telemetry/SearchTelemetry.swift:314— firefox-ios/Client/Telemetry/SearchTelemetry.swift:314-327 | firefox-ios/Client/Telemetry/SearchTelemetry.swift:373-386 | firefox-ios/Client/Telemetry/SearchTelemetry.swift:422-436 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Telemetry/SearchTelemetry.swift:314` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `firefox-ios/Client/Telemetry/SearchTelemetry.swift:312` calls `Int32`, `numberOfSearchResults` and `firefox-ios/Client/Telemetry/SearchTelemetry.swift:371` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (8–15 lines × 2) firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:552— firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:552-559 | firefox-ios/Client/Frontend/Settings/NotificationsSettingsViewController.swift:144-158 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift:552` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (14–15 lines × 2) firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksPanelViewModel.swift:306— firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksPanelViewModel.swift:306-319 | firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksPanelViewModel.swift:341-355 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Library/Bookmarks/Legacy/BookmarksPanelViewModel.swift:306` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (9–14 lines × 3) BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:629— BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:629-642 | BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:644-657 | BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:658-666 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/OnboardingKit/Preview/PreviewModel.swift:629` it begins part-way through the construct above it, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–14 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift:162— BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift:162-172 | firefox-ios/Client/Frontend/Reader/ReaderModeHandlers.swift:132-145 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/WebEngine/WKWebview/Scripts/ReaderMode/WKReaderModeHandlers.swift:162` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (12–14 lines × 2) firefox-ios/Client/Frontend/TabContentsScripts/UserScriptManager.swift:59— firefox-ios/Client/Frontend/TabContentsScripts/UserScriptManager.swift:59-72 | firefox-ios/Client/Frontend/TabContentsScripts/UserScriptManager.swift:83-94 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/TabContentsScripts/UserScriptManager.swift:59` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (25 lines × 2) firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:67— firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:67-91 | firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift:51-75 — before extracting anything, compare `firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift` and `firefox-ios/Client/Frontend/Browser/Toasts/PlainToast.swift` as WHOLE FILES: this scan already matched 5 separate duplicated blocks between them, totalling at least 77 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Toasts/ButtonToast.swift:67` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it. Note first that the copies are not typed on the same thing: the declarations holding them bind `viewModel` to `ButtonToastViewModel` in one and `PlainToastViewModel` in another, and the duplicated lines use it. The extracted unit therefore needs a parameter type that fits BOTH — their common supertype where they have one, or a new abstraction over them where they do not — and settling that is the step that comes BEFORE the extraction above. Where the two types are deliberately unrelated, the duplication is the price of that separation and the honest resolution is to record the decision rather than to extract.
Duplicated block (9–13 lines × 2) firefox-ios/Client/Frontend/Translations/TranslationsMiddleware.swift:436— firefox-ios/Client/Frontend/Translations/TranslationsMiddleware.swift:436-444 | firefox-ios/Client/Frontend/Translations/TranslationsMiddleware.swift:456-468 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Translations/TranslationsMiddleware.swift:456` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. Note that the copies do not run to the end of the range shown: their LAST lines are different code, not the same code under different names — the matched region ends inside that line. Extract the lines above it, and read the last line of each site separately.
Duplicated block (11–13 lines × 2) focus-ios/Blockzilla/Siri/SiriShortcuts.swift:61— focus-ios/Blockzilla/Siri/SiriShortcuts.swift:61-73 | focus-ios/Blockzilla/Siri/SiriShortcuts.swift:102-112 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `focus-ios/Blockzilla/Siri/SiriShortcuts.swift:61` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (11 lines × 4) firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:225— firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:225-235 | firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:245-255 | firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:269-279 | firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:293-303 — all 4 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Coordinators/Library/BookmarksCoordinator.swift:225` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it.
Duplicated block (9–11 lines × 2) BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:96— BrowserKit/Sources/WebEngine/WKWebview/WebServer/WKEngineWebServer.swift:96-104 | firefox-ios/Client/Application/WebServer.swift:132-142 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere both call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made twice.
Duplicated block (9–10 lines × 2) firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputViewModel.swift:159— firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputViewModel.swift:159-167 | firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputViewModel.swift:173-182 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/CreditCard/CreditCardSettingsView/CreditCardInputViewModel.swift:159` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (8–9 lines × 3) firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:223— firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:223-231 | firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:236-244 | firefox-ios/Client/Frontend/Home/Homepage/ContextMenu/ContextMenuState.swift:249-256 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited. Each matched range is the entire body of the declaration above it, so the region is already a complete unit: move that whole declaration to the shared location and have each site call it, rather than lifting the lines out of their bodies. Any `return` inside it is the body's own exit and keeps its meaning in the moved unit.
Duplicated block (7–8 lines × 3) SampleComponentLibraryApp/SampleComponentLibraryApp/RootViewController.swift:46— SampleComponentLibraryApp/SampleComponentLibraryApp/RootViewController.swift:46-53 | focus-ios/Blockzilla/Settings/Controller/AutocompleteSettingViewController.swift:36-42 | focus-ios/Blockzilla/Settings/Controller/SearchSettingsViewController.swift:42-49 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 7) firefox-ios/Client/Frontend/Autofill/Address/AddressAutoFillBottomSheetView.swift:37— firefox-ios/Client/Frontend/Autofill/Address/AddressAutoFillBottomSheetView.swift:37-43 | firefox-ios/Client/Frontend/Autofill/Address/AddressScrollView.swift:45-51 | firefox-ios/Client/Frontend/Autofill/AutofillFooterView.swift:47-53 | firefox-ios/Client/Frontend/Autofill/AutofillHeaderView.swift:61-67 | firefox-ios/Client/Frontend/Autofill/LoginAutofillView.swift:37-43 | firefox-ios/Client/Frontend/Autofill/LoginCellView.swift:57-63 | firefox-ios/Client/Frontend/Autofill/LoginListView.swift:38-44 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/Address/AddressAutoFillBottomSheetView.swift:37` it runs out through the closing brace of the declaration holding it — the window is that declaration's tail, not a fragment that begins part-way through something, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `firefox-ios/Client/Frontend/Autofill/LoginListView.swift:37` calls `fetchLogins` and `firefox-ios/Client/Frontend/Autofill/AutofillFooterView.swift:46` does not — after which the two agree again for 2 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6–7 lines × 2) firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:117— firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTrayIpadSelectorView.swift:117-122 | firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTraySelectorView.swift:221-227 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Browser/Tabs/Views/CustomSelectorView/TabTraySelectorView.swift:221` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (5 lines × 5) firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewController.swift:127— firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewController.swift:127-131 | firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:4979-4983 | firefox-ios/Client/Frontend/Settings/AppearanceSettings/WallpaperSettings/v1/WallpaperSettingsViewController.swift:251-255 | firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift:605-609 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:315-319 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 5 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 5 times. Read the line range as the matched WINDOW rather than a finished unit: at `firefox-ios/Client/Frontend/Autofill/Address/AddressAutofillSettingsViewController.swift:127` it does not close everything it opens, so those exact lines cannot be lifted as they stand — widen the region to the smallest complete statement or declaration that contains it, and extract that.
Duplicated block (141 lines × 3) BrowserKit/Sources/Common/Theming/DarkTheme.swift:11— BrowserKit/Sources/Common/Theming/DarkTheme.swift:11-162 | BrowserKit/Sources/Common/Theming/LightTheme.swift:11-151 | BrowserKit/Sources/Common/Theming/PrivateModeTheme.swift:11-153 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/Common/Theming/DarkTheme.swift:11` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (152 lines × 2) BrowserKit/Sources/Common/Theming/NovaDarkTheme.swift:10— BrowserKit/Sources/Common/Theming/NovaDarkTheme.swift:10-174 | BrowserKit/Sources/Common/Theming/NovaLightTheme.swift:10-161 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from both call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/Common/Theming/NovaDarkTheme.swift:10` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (152 lines × 3) BrowserKit/Sources/Common/Theming/NovaDarkTheme.swift:10— BrowserKit/Sources/Common/Theming/NovaDarkTheme.swift:10-174 | BrowserKit/Sources/Common/Theming/NovaLightTheme.swift:10-161 | BrowserKit/Sources/Common/Theming/NovaPrivateTheme.swift:10-161 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 3 call sites, so a change lands once. Read the line range as the matched WINDOW rather than a finished unit: at `BrowserKit/Sources/Common/Theming/NovaDarkTheme.swift:10` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (64 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusMessagingHelpers.swift:49— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusMessagingHelpers.swift:49-112 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusMessagingHelpers.swift:50-113 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusMessagingHelpers.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusMessagingHelpers.swift` as WHOLE FILES: 89% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place. Read the line range as the matched WINDOW rather than a finished unit: at `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/NimbusMessagingHelpers.swift:49` it runs out through the closing brace of the declaration holding it and carries on into the declaration that follows — the window is the tail of one member plus the head of the next, so no call can be substituted for those exact lines, and the smallest declaration that contains all of them is the type they sit in. The repeated unit is the member each site sits in: where those members' bodies are the same, move one whole member to the shared location and have the others delegate to it; where the copies are a run of near-identical overloads or wrappers that differ only in their signatures, the repetition IS the run — a one-line delegation has no helper inside it to lift — so generate the run from the set it enumerates, or accept it and keep each member's own documentation with it.
Duplicated block (39 lines × 2) MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Logger.swift:15— MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Logger.swift:15-53 | MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Logger.swift:15-53 — before extracting anything, compare `MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/Utils/Logger.swift` and `MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/Utils/Logger.swift` as WHOLE FILES: 97% of the shorter file's lines also appear in the other, so this reads as one file having been copied from the other rather than as a helper waiting to be extracted. The 1 duplicated block(s) this scan matched between them are fragments of that copy, not the extent of it — treat the file pair as the unit. The two sit in different directories, so one cannot simply be deleted in favour of the other while both are reached separately: hoist the shared part into a location both already depend on and have each file call it, and retire whichever file turns out to have no caller of its own left. Extracting one helper per block leaves the fork in place.
Duplicated block (9 lines × 4) BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatCategoryMenuCell.swift:54— BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatCategoryMenuCell.swift:54-62 | BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatCheckboxCell.swift:23-31 | BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatPreviewBulletListCell.swift:23-31 | BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatURLCell.swift:68-76 — the copies sit in sibling files of one directory, so a shared home is within easy reach: extract the block into a single shared function the call sites can all reach — a file they already depend on, or a new one alongside them — and call it from all 4 call sites, so a change lands once.
Duplicated block (9 lines × 3) firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsViewController.swift:292— firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsViewController.swift:292-300 | firefox-ios/Client/Frontend/Library/Bookmarks/BookmarksViewController.swift:806-814 | firefox-ios/Client/Frontend/Library/HistoryPanel/HistoryPanel.swift:657-665 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 3 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 3 times.
Duplicated block (7 lines × 4) firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:124— firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift:124-130 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift:129-135 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/EditFolderViewController.swift:113-119 | firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewController.swift:117-123 — before extracting anything, compare `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/EditBookmarkViewController.swift` and `firefox-ios/Client/Frontend/Library/Bookmarks/Edit Bookmark/GroupedEditBookmarkViewController.swift` as WHOLE FILES: this scan already matched 14 separate duplicated blocks between them, totalling at least 154 lines, which is the signature of one file having been copied from the other rather than of a helper waiting to be extracted. If that is what happened, the fix is to keep one copy and have the other call it (or delete it), which resolves this row and its siblings together — extracting one helper per block leaves the fork in place.
Duplicated block (5 lines × 24) firefox-ios/Client/Frontend/Settings/FirefoxSuggestSettingsViewController.swift:62— firefox-ios/Client/Frontend/Settings/FirefoxSuggestSettingsViewController.swift:62-66 | firefox-ios/Client/Frontend/Settings/Main/Account/ChinaSyncServiceSetting.swift:22-26 | firefox-ios/Client/Frontend/Settings/Main/Debug/AppDataUsageReportSetting.swift:9-14 | firefox-ios/Client/Frontend/Settings/Main/Debug/AppReviewPromptSetting.swift:17-23 | firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeMLPAEndpointSetting.swift:14-19 | firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeRSServerSetting.swift:13-18 | firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeToChinaSetting.swift:9-15 | firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeVPNEndpointSetting.swift:14-19 | firefox-ios/Client/Frontend/Settings/Main/Debug/DeleteAppAttestKeySetting.swift:10-16 | firefox-ios/Client/Frontend/Settings/Main/Debug/DeleteAutofillKeysSetting.swift:9-15 | firefox-ios/Client/Frontend/Settings/Main/Debug/DeleteExportedDataSetting.swift:8-15 | firefox-ios/Client/Frontend/Settings/Main/Debug/DeleteLoginsKeysSetting.swift:9-15 | firefox-ios/Client/Frontend/Settings/Main/Debug/ExportBrowserDataSetting.swift:8-15 | firefox-ios/Client/Frontend/Settings/Main/Debug/ExportLogDataSetting.swift:9-16 | firefox-ios/Client/Frontend/Settings/Main/Debug/ForceCrashSetting.swift:8-14 | firefox-ios/Client/Frontend/Settings/Main/Debug/ForceRSSyncSetting.swift:9-14 | firefox-ios/Client/Frontend/Settings/Main/Debug/LaunchPairingFromURLSetting.swift:38-44 | firefox-ios/Client/Frontend/Settings/Main/Debug/OffloadBackgroundWebViewsSetting.swift:18-24 | firefox-ios/Client/Frontend/Settings/Main/Debug/OpenFiftyTabsDebugOption.swift:17-23 | firefox-ios/Client/Frontend/Settings/Main/Debug/ResetContextualHints.swift:13-18 | firefox-ios/Client/Frontend/Settings/Main/Debug/ResetSearchEnginePrefsSetting.swift:9-14 | firefox-ios/Client/Frontend/Settings/Main/Debug/ScreenshotSetting.swift:19-25 | firefox-ios/Client/Frontend/Settings/Main/Debug/TriggerVPNAttestationSetting.swift:204-210 | firefox-ios/Client/Frontend/Settings/Main/Debug/TriggerVPNAttestationSetting.swift:222-228 — there are 24 copies across 23 file(s) — more copies than files, so at least one file holds the block twice. Extract it once into a single shared function every call site can reach and call it from all 24 sites; resolving a subset leaves the remainder to drift apart. The matched lines also transfer control out of the body holding them, which cannot survive a move into a called unit unchanged: have the extracted unit return that decision and let each site act on it. ★ These copies have DRIFTED, and that is worth reading before extracting anything: just before the matched lines, `firefox-ios/Client/Frontend/Settings/Main/Debug/ChangeRSServerSetting.swift:11` calls `resolve` and `firefox-ios/Client/Frontend/Settings/Main/Debug/AppDataUsageReportSetting.swift:8` does not — after which the two agree again for 3 more lines. One of those two behaviours is the intended one and the other is what a copy-paste left behind, so decide which BEFORE unifying them: extracting the shared part will silently settle it, and if the copy that skips the call is the wrong one, that bug is already live.
Duplicated block (6 lines × 7) firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:1046— firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:1046-1052 | firefox-ios/Client/Frontend/Browser/Tabs/Views/RemoteTabsPanel.swift:215-220 | firefox-ios/Client/Frontend/Browser/Tabs/Views/TabTrayViewController.swift:461-466 | firefox-ios/Client/Frontend/Browser/TermsOfUse/View/TermsOfUseViewController.swift:171-177 | firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift:473-480 | firefox-ios/Client/Frontend/Microsurvey/Survey/View/MicrosurveyViewController.swift:174-179 | firefox-ios/Client/Frontend/ShortcutsLibrary/ShortcutsLibraryViewController.swift:157-164 — the copies span different directories, so extracting a shared function means choosing where it lives: put it somewhere all 7 call sites can already reach — a location they all depend on today, or a new shared one if there is none — and call it from each site; until then, every change has to be made 7 times.
Duplication concentrated across 2 sibling directories (5 clone groups) REDACTED:8— 5 of the duplicated blocks reported below have copies in at least two of the sibling directories firefox-ios, focus-ios under the repository root. That concentration is one structural fact, not 5 local ones: the siblings replicate behaviour none of them owns, which is the shape of a missing shared module — a common library every sibling imports — rather than 5 separate extractions. Check first whether the siblings are deliberately standalone deliverables (scaffold templates, demo apps that must stay copy-pasteable); where they are, the duplication is the design and the per-block rows are the ones to act on.
Wholesale file copy (218 identical lines × 2 files) REDACTED:8— REDACTED:8 · REDACTED:29 — these 2 files are line-for-line copies of one another — 218 lines are identical, in the same order, in every one of them — so this is one fact about the file set, not a block to extract. An edit made to one file and not the others changes behaviour silently, which is the failure a wholesale copy guarantees. Pick one file as the single source and derive the others from it (re-export it, spread it into the local overrides each variant genuinely needs, or generate the copies at build time) — the few lines that differ between the files are exactly the part each variant should still own. Check first whether the copies are deliberately standalone deliverables (a translation file seeded from its sibling and waiting to be translated); where they are, the duplication is the design, and the honest move is to mark the seeded file as untranslated rather than to let it pass as done.
Duplicated block (49 lines × 2 locations) REDACTED:4338— REDACTED:4338 · REDACTED:4408 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (47 lines × 2 locations) REDACTED:2805— REDACTED:2805 · REDACTED:3034 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (36 lines × 2 locations) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/Ads.js:11— firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/Ads.js:11 · focus-ios/Blockzilla/Ads.js:14 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (33 lines × 2 locations) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/FullscreenHelper.js:5— firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/FullscreenHelper.js:5 · focus-ios/Blockzilla/FullScreen.js:22 — the 2 copies are spread across 2 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another.
Duplicated block (30 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:427— firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:427 · firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:160 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (29 matched lines × 2 locations) · ×1
Duplicated block with local edits (29 matched lines × 2 locations) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:536— firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:536 · firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:601 — the two spans are one implementation copied and then locally edited — 154 tokens are still identical, in the same order in both spans, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
R10 · Code Duplication· Duplicated block with local edits (27 matched lines × 2 locations) · ×1
Duplicated block with local edits (27 matched lines × 2 locations) firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:594— firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:594 · firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:64 — the two spans are one implementation copied and then locally edited — 157 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (25 lines × 2 locations) REDACTED:2075— REDACTED:2075 · REDACTED:2147 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (21 lines × 6 locations) firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:738— firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:738 · firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:774 · firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:898 · firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:926 · +2 more site(s) not listed — all 6 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (21 lines × 2 locations) REDACTED:2724— REDACTED:2724 · REDACTED:2756 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
Duplicated block (20 lines × 4 locations) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/__firefox__.js:8— firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/__firefox__.js:8 · firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentStart/__firefox__.js:8 · firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/NightModeAtDocumentStart/__firefox__.js:8 · REDACTED:8 — the 4 copies are spread across 4 directories, so the shared home is a decision rather than an obvious spot: check first whether one of them already owns this behaviour, and otherwise put the extracted module somewhere all of the sites already reach rather than making one of them depend on another. There is one copy in each of 4 separate files rather than several in one place, so check first whether these are sibling modules that each declare their own version of one shape — one per entity, per provider, per language. Where they are, no single extracted module collapses them: each module still has to be written, and what recurs is the TEMPLATE. The moves that do collapse a template are to generate these modules from the set they enumerate, or to replace the repeated construction with one factory each site calls with its own values — and where the set is the point, each module pinning one distinct thing, the repetition IS the enumeration and there is nothing to delete.
Duplicated block (19 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1633— firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1633 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1740 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (17 lines × 3 locations) firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:869— firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:869 · firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:922 · firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:1002 — all 3 copies are in the same file, so extract the block into one function there and call it from every one of those sites — resolving only two of them leaves the rest to drift apart the first time one is edited.
R10 · Code Duplication· Duplicated block with local edits (17 matched lines × 2 locations) · ×1
Duplicated block with local edits (17 matched lines × 2 locations) firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:308— firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:308 · firefox-ios/Client/Assets/CC_Script/HeuristicsRegExp.sys.mjs:666 — the two spans are one implementation copied and then locally edited — 95 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (16 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:800— firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:800 · REDACTED:162 — the 2 copies are spread across 2 files, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (14 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:481— firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:481 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:498 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
R10 · Code Duplication· Duplicated block with local edits (14 matched lines × 2 locations) · ×1
Duplicated block with local edits (14 matched lines × 2 locations) firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js:147— firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js:147 · focus-ios/Blockzilla/Lib/TrackingProtection/Assets/preload.js:28 — the two spans are one implementation copied and then locally edited — 102 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (11 lines × 2 locations) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:239— firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:239 · firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:378 — both copies are in the same file, so extract the block into one function there and call it from each site — the copies drift apart the first time only one of them is edited.
R10 · Code Duplication· Duplicated block with local edits (11 matched lines × 2 locations) · ×1
Duplicated block with local edits (11 matched lines × 2 locations) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/LanguageSampleExtractor.js:48— firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/LanguageSampleExtractor.js:48 · firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/Summarizer.js:38 — the two spans are one implementation copied and then locally edited — 55 tokens are still identical, in the same order in both files, with only local edits between them. The copies have already begun to drift, which is this row's finding: an edit made to one and not the other changes behaviour silently. Diff the two spans first to learn what genuinely differs, then extract the shared core into one module both sites use, passing the differences in as parameters — or, if one copy exists only because the other could not be imported from its context, make one of them the single source the other is generated or re-exported from. If one copy is no longer reachable, delete it rather than letting it shadow the live one.
Duplicated block (9 lines × 2 locations) REDACTED:3917— REDACTED:3917 · REDACTED:4038 — all 2 copies are in the same file, and the CITED SPAN is not a self-contained block — it runs from inside one construct into the next (the tail of a branch plus the head of the following one, a run of switch arms, the end of a declaration plus the list that follows it) rather than covering a whole unit. So do not lift these lines literally: no call can be substituted for a half-open construct. Extract the enclosing repeated UNIT instead — the whole function, component or branch these lines sit in — and where the repetition IS the construct (a run of switch arms, a stack of near-identical declarations) replace it with one table or registry looked up by key rather than a helper each arm calls. The copies still drift apart the first time only one of them is edited, which is why this is reported.
Duplicated block (6 lines × 2 locations) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js:53— firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js:53 · firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/Summarizer.js:12 — the 2 copies are spread across 2 files, and the CITED SPAN is a run of DECLARATIONS inside a construct — the members of a type, or the entries of an object or array literal — with no statement anywhere in it. Do not read this as an extract-a-helper row: nothing here executes, so there is no call site, and a call expression cannot stand where a member declaration or a literal's entry was. What repeats is a SHAPE, and which shape decides the move. Where the copies declare the same members, the repetition is a missing common ancestor: give it a base type, an interface both extend, a generic instantiated twice, or — where the copies are a literal's entries rather than a type's members — one shared constant each site spreads or refers to, so the set is written once. Where they declare DIFFERENT members and only the form is shared — a decorator and its options, an annotation, a registration table's keys — the form is prescribed by a framework or a schema rather than copied, and the only collapse available is to generate the declarations from that schema; where you do not own the generator, this is the cost of the framework and there is nothing to extract. Check which of the two it is before acting: these copies still drift apart the first time only one of them is edited, which is why the repetition is reported, but the sentence to act on is not the same in both cases.
Complex function _getFormFields (cyclomatic 34, cognitive 52) firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:622— _getFormFields has cyclomatic complexity 34 and cognitive complexity 52; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _canonicalizedPropertyValues (cyclomatic 30, cognitive 40) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:167— _canonicalizedPropertyValues has cyclomatic complexity 30 and cognitive complexity 40; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function loadBergamot (cyclomatic 28, cognitive 35) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:5— loadBergamot has cyclomatic complexity 28 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _fillForm (cyclomatic 27, cognitive 27) REDACTED:321— _fillForm has cyclomatic complexity 27 and cognitive complexity 27; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function merge (cyclomatic 23, cognitive 46) REDACTED:6101— merge has cyclomatic complexity 23 and cognitive complexity 46; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function findCreditCardSelectOption (cyclomatic 22, cognitive 33) firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:1002— findCreditCardSelectOption has cyclomatic complexity 22 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _parsePhoneFields (cyclomatic 21, cognitive 34) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:244— _parsePhoneFields has cyclomatic complexity 21 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _parseStreetAddressFields (cyclomatic 21, cognitive 34) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:370— _parseStreetAddressFields has cyclomatic complexity 21 and cognitive complexity 34; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isValidSection (cyclomatic 21, cognitive 15) firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs:527— isValidSection has cyclomatic complexity 21 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 20, cognitive 45) REDACTED:1404— (anonymous) has cyclomatic complexity 20 and cognitive complexity 45; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function findAddressSelectOption (cyclomatic 20, cognitive 33) firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:882— findAddressSelectOption has cyclomatic complexity 20 and cognitive complexity 33; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function genericPointerToWireType (cyclomatic 19, cognitive 35) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1659— genericPointerToWireType has cyclomatic complexity 19 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _parseCreditCardNameFields (cyclomatic 18, cognitive 23) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:647— _parseCreditCardNameFields has cyclomatic complexity 18 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function adaptFieldMaxLength (cyclomatic 17, cognitive 32) REDACTED:893— adaptFieldMaxLength has cyclomatic complexity 17 and cognitive complexity 32; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function parsePasswordRules (cyclomatic 17, cognitive 19) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:621— parsePasswordRules has cyclomatic complexity 17 and cognitive complexity 19; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function onFocusIn (cyclomatic 17, cognitive 15) REDACTED:518— onFocusIn has cyclomatic complexity 17 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function create (cyclomatic 16, cognitive 20) firefox-ios/Client/Assets/CC_Script/FieldScanner.sys.mjs:93— create has cyclomatic complexity 16 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function distance (cyclomatic 16, cognitive 20) firefox-ios/Client/Assets/CC_Script/fathom.mjs:770— distance has cyclomatic complexity 16 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _parseCreditCardExpiryFields (cyclomatic 16, cognitive 17) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:535— _parseCreditCardExpiryFields has cyclomatic complexity 16 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isNodeHidden (cyclomatic 16, cognitive 12) REDACTED:5840— isNodeHidden has cyclomatic complexity 16 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function computeFillingValue (cyclomatic 15, cognitive 22) REDACTED:775— computeFillingValue has cyclomatic complexity 15 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function toWireType (cyclomatic 15, cognitive 20) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:2578— toWireType has cyclomatic complexity 15 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _getFormFields (cyclomatic 15, cognitive 20) REDACTED:126— _getFormFields has cyclomatic complexity 15 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function isVisible (cyclomatic 15, cognitive 18) firefox-ios/Client/Assets/CC_Script/fathom.mjs:496— isVisible has cyclomatic complexity 15 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function buildRegionMapIfAvailable (cyclomatic 15, cognitive 15) firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:685— buildRegionMapIfAvailable has cyclomatic complexity 15 and cognitive complexity 15; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 14, cognitive 35) focus-ios/Blockzilla/MetadataHelper.js:28— (anonymous) has cyclomatic complexity 14 and cognitive complexity 35; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function identifyCountryCode (cyclomatic 14, cognitive 23) firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:737— identifyCountryCode has cyclomatic complexity 14 and cognitive complexity 23; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function inferFieldInfo (cyclomatic 14, cognitive 18) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:979— inferFieldInfo has cyclomatic complexity 14 and cognitive complexity 18; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function telTransformer (cyclomatic 14, cognitive 17) REDACTED:1169— telTransformer has cyclomatic complexity 14 and cognitive complexity 17; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _parseCustomCharacterClass (cyclomatic 14, cognitive 16) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:355— _parseCustomCharacterClass has cyclomatic complexity 14 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _parsePasswordRule (cyclomatic 14, cognitive 12) firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:466— _parsePasswordRule has cyclomatic complexity 14 and cognitive complexity 12; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive sits below cyclomatic here, so much of the count is breadth — arms side by side rather than stacked — and splitting per arm would leave a function per arm; group the work between the checks into named steps instead. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function FormatNumber (cyclomatic 13, cognitive 28) REDACTED:145— FormatNumber has cyclomatic complexity 13 and cognitive complexity 28; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function groupFields (cyclomatic 13, cognitive 26) firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs:218— groupFields has cyclomatic complexity 13 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function fillFields (cyclomatic 13, cognitive 21) REDACTED:452— fillFields has cyclomatic complexity 13 and cognitive complexity 21; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function _parseAddressFields (cyclomatic 13, cognitive 16) firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:484— _parseAddressFields has cyclomatic complexity 13 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function ParseNumber (cyclomatic 13, cognitive 14) REDACTED:388— ParseNumber has cyclomatic complexity 13 and cognitive complexity 14; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function generateLabelMap (cyclomatic 12, cognitive 26) firefox-ios/Client/Assets/CC_Script/LabelUtils.sys.mjs:179— generateLabelMap has cyclomatic complexity 12 and cognitive complexity 26; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function stringToUTF8Array (cyclomatic 12, cognitive 22) firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:238— stringToUTF8Array has cyclomatic complexity 12 and cognitive complexity 22; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function #subdivideNodeForContentTranslations (cyclomatic 12, cognitive 20) REDACTED:2503— #subdivideNodeForContentTranslations has cyclomatic complexity 12 and cognitive complexity 20; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
Complex function (anonymous) (cyclomatic 12, cognitive 16) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js:31— (anonymous) has cyclomatic complexity 12 and cognitive complexity 16; this row is raised above a cyclomatic bar of 10. The two numbers answer different questions and the gap between them is what decides whether to act: cyclomatic counts the independent arms through the body, cognitive counts what it costs to hold them in your head, so nesting and mixed boolean chains raise it while a flat run of independent arms does not. Cognitive is at or above cyclomatic here, so the branching is nested or entangled rather than laid out side by side — extracting each decision into its own named function is the change that pays. Measured by this repository's own parse of the file, so a body assembled at runtime, or generated, is counted as written rather than as it executes.
REDACTED: 5984 lines of code REDACTED:1— REDACTED has 5984 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/bergamot-translator.js · ×1
firefox-ios/Client/Assets/CC_Script/bergamot-translator.js: 3326 lines of code firefox-ios/Client/Assets/CC_Script/bergamot-translator.js:1— firefox-ios/Client/Assets/CC_Script/bergamot-translator.js has 3326 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/fathom.mjs · ×1
firefox-ios/Client/Assets/CC_Script/fathom.mjs: 2513 lines of code firefox-ios/Client/Assets/CC_Script/fathom.mjs:1— firefox-ios/Client/Assets/CC_Script/fathom.mjs has 2513 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs: 1383 lines of code firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/FormAutofillUtils.sys.mjs has 1383 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs: 1320 lines of code firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs has 1320 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 1210 lines of code REDACTED:1— REDACTED has 1210 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs: 1141 lines of code firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs has 1141 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs: 852 lines of code firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs has 852 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js · ×1
firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js: 815 lines of code firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:1— firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js has 815 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs: 689 lines of code firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs has 689 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/HeuristicsRegExp.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/HeuristicsRegExp.sys.mjs: 651 lines of code firefox-ios/Client/Assets/CC_Script/HeuristicsRegExp.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/HeuristicsRegExp.sys.mjs has 651 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs: 641 lines of code firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs has 641 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs: 617 lines of code firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs has 617 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs: 604 lines of code firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs has 604 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 547 lines of code REDACTED:1— REDACTED has 547 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/CreditCard.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/CreditCard.sys.mjs: 476 lines of code firefox-ios/Client/Assets/CC_Script/CreditCard.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/CreditCard.sys.mjs has 476 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
REDACTED: 434 lines of code REDACTED:1— REDACTED has 434 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
R3 · Large Files· firefox-ios/Client/Assets/CC_Script/AutofillTelemetry.sys.mjs · ×1
firefox-ios/Client/Assets/CC_Script/AutofillTelemetry.sys.mjs: 405 lines of code firefox-ios/Client/Assets/CC_Script/AutofillTelemetry.sys.mjs:1— firefox-ios/Client/Assets/CC_Script/AutofillTelemetry.sys.mjs has 405 significant lines (blank lines excluded), over the 400-line bar, and contains logic — a file this long is usually several responsibilities in one module.
No lint or typecheck script — test ✓ · lint ✗ · typecheck ✗ — read from this repository's REDACTED scripts and corroborated against its CI workflows. A script counts when its name or command matches the step: `test` for the suite, `lint` or `prettier` for linting, `typecheck`/`type-check`/`tsc` for type checking. ✗ therefore means no script or CI step under those names was found, NOT that the step is absent from your pipeline — a task invoked by a runner this check does not read, or named something else entirely, is not seen and is worth confirming before acting on a cross. A ✓ means the wiring is DECLARED — a script or CI step under those names exists. It is not a statement that the step passes, or that it runs at all: nothing here installs a dependency or executes a suite.
Dead file (~633 LoC) REDACTED— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~395 LoC) REDACTED— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~375 LoC) REDACTED— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~202 LoC) firefox-ios/Client/ContentBlocker/TrackingProtectionStats.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentStart/TrackingProtectionStats.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~142 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/TranslationsEntrypoint.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~135 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AutofillAtDocumentStart/FormAutofillHelper.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~126 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/Summarizer.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~83 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/FullscreenHelper.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~81 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentStart/NoImageModeHelper.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~73 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentStart/DownloadHelper.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~67 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderModeStyles.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~61 LoC) focus-ios/Blockzilla/FullScreen.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~55 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/JSONLD.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), but 2 in-repo import(s) from 2 other file(s) do name it (firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/ReaderMode.js, firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentStart/Summarizer.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~47 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/WebCompatPageContext.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~46 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentEnd/MetadataHelper.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~35 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentEnd/CustomSearchHandler.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~30 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/PopupHelper.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~20 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/NightModeAtDocumentStart/NightModeHelper.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~19 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/NightModeAtDocumentStart/DarkReader.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), but 1 in-repo import(s) from 1 other file(s) do name it (firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/NightModeAtDocumentStart/NightModeHelper.js) — every one of those referrers is itself unreachable, so this file is dead only as a member of that cluster: if any referrer is in fact alive, this row falls with it
Dead file (~14 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentEnd/PrintHandler.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~10 LoC) focus-ios/Blockzilla/Lib/TrackingProtection/Assets/postload.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Dead file (~8 LoC) firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/AtDocumentStart/TrackingProtectionStats.js— no import path from any entry point (50 application, 1 tooling, 10 test roots considered), and no other file in the scanned tree imports it — nothing in-repo names this module at all, which is the strongest form of this claim the import graph can make
Orphaned file MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file firefox-ios/Client/Experiments/Messaging/GleanPlumbMessageManager.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file test-fixtures/generate-test-db.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Sync15/RustSyncTelemetryPing.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file focus-ios/Blockzilla/Menu/Old/PhotonActionSheet.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file firefox-ios/CredentialProvider/CredentialListViewController.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file focus-ios/Blockzilla/Settings/Controller/SearchSettingsViewController.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file SampleComponentLibraryApp/SampleComponentLibraryApp/Buttons/ButtonsViewController.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Bookmark.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file SampleBrowser/SampleBrowser/UI/Browser/BrowserViewController.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/NimbusBuilder.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file focus-ios/Blockzilla/Tracking Protection/TrackingProtectionPageStats.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file focus-ios/Blockzilla/Search/SearchEngine.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file firefox-ios/Client/Frontend/TrackingProtection/TrackingProtectionHelpers/TrackingProtectionConnectionDetailsView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureHolder.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file taskcluster/ffios_taskgraph/release_promotion.py:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file REDACTED:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file focus-ios/Blockzilla/Search/SearchEngineManager.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file MozillaRustComponents/Sources/MozillaRustComponentsWrapper/FxAClient/FxAccountDeviceConstellation.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file firefox-ios/Client/Frontend/PasswordGenerator/View/PasswordGeneratorPasswordFieldView.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file focus-ios/Blockzilla/Utilities/FindInPageBar.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file firefox-ios/Account/FxAPushMessageHandler.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file BrowserKit/Sources/WebEngine/WKWebview/WKNavigationHandler.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file focus-ios/Blockzilla/Extensions/StringExtensions.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Orphaned file BrowserKit/Sources/WebEngine/Utilities/URLFormatter.swift:1— No one still active in this repository holds living knowledge of this file: everyone who made a meaningful change to it has gone quiet, or what the current team did to it (moves, reformatting, log-level or import edits, renames) never needed understanding it. If it breaks, no one currently understands it. Attach the read to the next change that touches it: have a second person review that change, and leave behind a short comment or test recording what the file is for.
Duplicated predicate REDACTED:266— `!argument || iterator(argument) === false` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/FullscreenHelper.js:12— `!isFullScreenEnabled && isFullscreenVideosSupported && !/mobile/i.test(navigator.userAgent)` appears character-identically in 2 files — firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/FullscreenHelper.js, focus-ios/Blockzilla/FullScreen.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:196— `!isTextNodeVisible(originalNode) || originalNode.parentElement.nodeName === "IFRAME"` appears character-identically in 2 files — REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/FullscreenHelper.js:5— `document.fullscreenEnabled || document.webkitFullscreenEnabled || document.mozFullScreenEnabled || document.msFullscreenEnabled` appears character-identically in 2 files — firefox-ios/Client/Frontend/UserContent/UserScripts/AllFrames/WebcompatAtDocumentStart/FullscreenHelper.js, focus-ios/Blockzilla/FullScreen.js. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate REDACTED:5869— `element.offsetWidth || element.offsetHeight || element.getClientRects().length` appears character-identically in 3 files — REDACTED, REDACTED, REDACTED. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:463— `nextElementSibling !== null && nextElementSibling.tagName === "LABEL"` appears character-identically in 2 files — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs, firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:606— `options.length < 12 || options.length > 13` appears character-identically in 2 files — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs, firefox-ios/Client/Assets/CC_Script/FormAutofillHeuristics.sys.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:444— `parentElement.tagName === "DD" && parentElement.previousElementSibling` appears character-identically in 2 files — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs, firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:437— `parentElement.tagName === "TD" && parentElement.parentElement` appears character-identically in 2 files — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs, firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs:456— `previousElementSibling !== null && previousElementSibling.tagName === "LABEL"` appears character-identically in 2 files — firefox-ios/Client/Assets/CC_Script/CreditCardRuleset.sys.mjs, firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Assets/CC_Script/LoginManager.shared.sys.mjs:27— `regex.test(element.id) || regex.test(element.name) || regex.test(element.className)` appears character-identically in 2 files — firefox-ios/Client/Assets/CC_Script/LoginManager.shared.sys.mjs, firefox-ios/Client/Assets/CC_Script/NewPasswordModel.sys.mjs. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate BrowserKit/Sources/ComponentLibrary/Headers/HeaderView.swift:249— `(isHidden && !horizontalLine.isHidden) || (!isHidden && horizontalLine.isHidden)` appears character-identically in 2 files — BrowserKit/Sources/ComponentLibrary/Headers/HeaderView.swift, BrowserKit/Sources/ComponentLibrary/Headers/NavigationHeaderView.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift:791— `(lastContentOffsetY > 0 && contentOffset.y <= 0) || (lastContentOffsetY <= 0 && contentOffset.y > 0)` appears character-identically in 2 files — firefox-ios/Client/Frontend/Browser/TabScrollController/LegacyTabScrollController.swift, firefox-ios/Client/Frontend/Browser/TabScrollController/TabScrollHandler.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift:91— `(state == 0 || state == Masks.WRITER_WAITING_BIT) && OSAtomicCompareAndSwap32Barrier(state, Masks.WRITER_BIT, _state)` appears character-identically in 2 files — BrowserKit/Sources/Shared/Deferred/ReadWriteLock.swift, focus-ios/Deferred/ReadWriteLock.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate BrowserKit/Sources/Shared/Extensions/URLExtensions.swift:135— `AppConstants.isRunningUITests || AppConstants.isRunningPerfTests` appears character-identically in 3 files — BrowserKit/Sources/Shared/Extensions/URLExtensions.swift, firefox-ios/Client/Application/main.swift, firefox-ios/Client/Experiments/Experiments.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/Settings/Main/AppSettingsTableViewController.swift:560— `MOZ_CHANNEL_beta || MOZ_CHANNEL_developer` appears character-identically in 6 files — firefox-ios/Client/Frontend/Settings/Main/AppSettingsTableViewController.swift, firefox-ios/Client/Frontend/Settings/Main/Debug/InstallationDetailsSetting.swift, firefox-ios/Client/Frontend/Settings/Main/Debug/ResetInstallationHistorySetting.swift, firefox-ios/Client/Frontend/Settings/Main/Debug/ResetTipsSetting.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/PasswordManagement/AddCredentialViewController.swift:307— `action == MenuHelperLoginModel.selectorCopy || action == MenuHelperLoginModel.selectorOpenAndFill` appears character-identically in 2 files — firefox-ios/Client/Frontend/PasswordManagement/AddCredentialViewController.swift, firefox-ios/Client/Frontend/Settings/PasswordDetailViewController.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/PasswordManagement/AddCredentialViewController.swift:302— `action == MenuHelperLoginModel.selectorCopy || showRevealOption` appears character-identically in 2 files — firefox-ios/Client/Frontend/PasswordManagement/AddCredentialViewController.swift, firefox-ios/Client/Frontend/Settings/PasswordDetailViewController.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:160— `action.windowUUID == .unavailable || action.windowUUID == state.windowUUID` appears character-identically in 32 files — firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift, firefox-ios/Client/Frontend/Browser/MainMenu/Redux/MainMenuState.swift, firefox-ios/Client/Frontend/Browser/SearchEngines/Redux/SearchEngineSelectionState.swift, firefox-ios/Client/Frontend/Browser/Tabs/State/RemoteTabsPanelState.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift:147— `actionWindowUUID == .unavailable || actionWindowUUID == state.windowUUID` appears character-identically in 2 files — firefox-ios/Client/Frontend/Browser/BrowserViewController/State/BrowserViewControllerState.swift, firefox-ios/Client/Frontend/Browser/Toolbars/Redux/ToolbarState.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/Browser/Tabs/Views/TabDisplayView.swift:93— `collectionView.hasActiveDrag || isLongPressGestureStarted` appears character-identically in 2 files — firefox-ios/Client/Frontend/Browser/Tabs/Views/TabDisplayView.swift, firefox-ios/Client/Frontend/Browser/TopTabDisplayManager.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate BrowserKit/Sources/WebEngine/WKWebview/WKNavigationHandler.swift:165— `error.code == WKError.webContentProcessTerminated.rawValue && error.domain == "WebKitErrorDomain"` appears character-identically in 2 files — BrowserKit/Sources/WebEngine/WKWebview/WKNavigationHandler.swift, firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate BrowserKit/Sources/WebEngine/WKWebview/WKNavigationHandler.swift:108— `error.domain == "WebKitErrorDomain" && error.code == 102` appears character-identically in 2 files — BrowserKit/Sources/WebEngine/WKWebview/WKNavigationHandler.swift, firefox-ios/Client/Frontend/Browser/BrowserViewController/Extensions/BrowserViewController+WebViewDelegates.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift:688— `featureFlagsProvider.isEnabled(.firefoxSuggestFeature) && userPreferences.getPreferenceFor(.firefoxSuggestFeature)` appears character-identically in 3 files — firefox-ios/Client/Frontend/Browser/Search/SearchViewController.swift, firefox-ios/Client/Frontend/Settings/FirefoxSuggestSettingsViewController.swift, firefox-ios/Client/Frontend/Settings/SearchSettingsTableViewController.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
Duplicated predicate firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift:395— `featureFlagsProvider.isEnabled(.homepagePinnedHeader) && featureFlagsProvider.isEnabled(.homepageStoryCategories)` appears character-identically in 3 files — firefox-ios/Client/Frontend/Browser/BrowserViewController/Views/BrowserViewController.swift, firefox-ios/Client/Frontend/Home/Homepage/HomepageViewController.swift, firefox-ios/Client/Frontend/Home/Homepage/Layout/HomepageSectionLayoutProvider.swift. It is one line, so the duplication detector's token window never sees it; the copies drift when only one is corrected. Give the condition a name and one home.
+ 15 more in this group — see findings.md.
P2 · Observability· Console output used as the logging channel · ×31
Console output used as the logging channel focus-ios/Blockzilla/FullScreen.js:18— `focus-ios/Blockzilla/FullScreen.js` reports through `console.*` at line 18 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/FormAutofill.sys.mjs:197— `firefox-ios/Client/Assets/CC_Script/FormAutofill.sys.mjs` reports through `console.*` at line 197 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:363— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 363 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:378— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 378 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:405— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 405 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:420— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 420 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:435— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 435 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:449— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 449 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:457— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 457 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:476— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 476 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:481— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 481 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:486— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 486 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:550— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 550 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:573— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 573 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:587— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 587 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs:612— `firefox-ios/Client/Assets/CC_Script/PasswordRulesParser.sys.mjs` reports through `console.*` at line 612 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:52— `firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 52 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:53— `firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 53 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:54— `firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 54 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:59— `firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 59 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:60— `firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 60 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs:62— `firefox-ios/Client/Assets/CC_Script/TranslationsHelpers.mjs` reports through `console.*` at line 62 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs:602— `firefox-ios/Client/Assets/CC_Script/translations-engine.sys.mjs` reports through `console.*` at line 602 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:28— `firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js` reports through `console.*` at line 28 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Console output used as the logging channel firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js:33— `firefox-ios/Client/Assets/CC_Script/translations-engine.worker.js` reports through `console.*` at line 33 although other files in its module log through a logger. Console lines carry no level, fields or correlation and never reach the log pipeline.
Off-boarding risk: anonymized user #1 — If anonymized user #1 becomes unavailable, 26 significant file(s) lose their only recent owner: BrowserKit/Sources/WebCompatReporterKit/WebCompatTechnicalDataViewController.swift, firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportPayload.swift, BrowserKit/Sources/ComponentLibrary/SwiftUI/PagingCarousel.swift, BrowserKit/Sources/WebCompatReporterKit/WebCompatReportPreviewViewController.swift, firefox-ios/Client/Frontend/Browser/WebCompat/WebCompatReportDataCollector.swift, BrowserKit/Sources/WebCompatReporterKit/WebCompatFullPageScreenshotView.swift, BrowserKit/Sources/WebCompatReporterKit/WebCompatScreenshotRailView.swift, BrowserKit/Sources/WebCompatReporterKit/Cells/WebCompatURLCell.swift (+18 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #2 — If anonymized user #2 becomes unavailable, 20 significant file(s) lose their only recent owner: BrowserKit/Sources/ComponentLibrary/AIBackgroundEffectView.swift, BrowserKit/Sources/QuickAnswersKit/UI/QuickAnswersContentView.swift, BrowserKit/Sources/QuickAnswersKit/UI/QuickAnswersViewController.swift, BrowserKit/Sources/QuickAnswersKit/UI/QuickAnswersSourceView.swift, BrowserKit/Sources/QuickAnswersKit/UI/TranscriptLabel.swift, BrowserKit/Sources/QuickAnswersKit/UI/QuickAnswersEntryPointButton.swift, BrowserKit/Sources/QuickAnswersKit/UI/SourceRevealTransitionAnimator.swift, BrowserKit/Sources/SummarizeKit/UI/SummarizeViewModel.swift (+12 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #3 — If anonymized user #3 becomes unavailable, 10 significant file(s) lose their only recent owner: firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerCategoryRowView.swift, firefox-ios/Client/ContentBlocker/TrackerBlockStats/TrackerBlockStatsStore.swift, firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerSheetState.swift, firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerModuleState.swift, firefox-ios/Providers/Merino/MerinoFeedFetcher.swift, firefox-ios/Client/Frontend/Home/Homepage/Wallpapers/v1/Models/WallpaperCollection.swift, firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerProgressBarView.swift, firefox-ios/Client/Frontend/Home/Homepage/TrackerBlockerModule/TrackerBlockerModuleMiddleware.swift (+2 more). Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #4 — If anonymized user #4 becomes unavailable, 5 significant file(s) lose their only recent owner: firefox-ios/Client/Frontend/Onboarding/OnboardingCardView.swift, firefox-ios/Client/Frontend/Reader/SchemeHandler/PageRoute.swift, firefox-ios/Client/Frontend/Onboarding/OnboardingCardScheduler.swift, firefox-ios/Client/Frontend/Settings/Main/Debug/OnboardingDripDebugSettings.swift, firefox-ios/Client/Frontend/Onboarding/OnboardingCardSchedule.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #5 — If anonymized user #5 becomes unavailable, 5 significant file(s) lose their only recent owner: BrowserKit/Sources/ComponentLibrary/Buttons/ChipButton.swift, firefox-ios/Client/Coordinators/CameraCoordinator.swift, BrowserKit/Sources/ComponentLibrary/ChipPickerView.swift, firefox-ios/Client/Frontend/GoogleLens/GoogleLensRequestBuilder.swift, firefox-ios/Client/Frontend/Home/Homepage/SectionHeader/NewsAffordanceHeaderView.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #6 — If anonymized user #6 becomes unavailable, 5 significant file(s) lose their only recent owner: BrowserKit/Sources/Common/Theming/NovaColors.swift, firefox-ios/Client/Frontend/Browser/TermsOfUse/View/TermsOfUseLinkViewController.swift, firefox-ios/Client/Frontend/Browser/TermsOfUse/ToUExperimentsTracking.swift, BrowserKit/Sources/ComponentLibrary/ShadowCardView.swift, firefox-ios/Client/Frontend/Browser/TermsOfUse/ToUExperiencePointsCalculator.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #7 — If anonymized user #7 becomes unavailable, 4 significant file(s) lose their only recent owner: firefox-ios/Client/Frontend/Browser/Toolbars/Redux/NavigationActionsBuilder.swift, firefox-ios/Client/Frontend/Browser/Toolbars/AddressToolbarContainerLens.swift, firefox-ios/Client/Frontend/Browser/Toolbars/Redux/BrowserActionsBuilder.swift, firefox-ios/Client/Frontend/Browser/Toolbars/Redux/TrailingPageActionsBuilder.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #8 — If anonymized user #8 becomes unavailable, 4 significant file(s) lose their only recent owner: firefox-ios/Client/TabManagement/TabContentScriptManager.swift, firefox-ios/Client/TabManagement/TabRestorer.swift, firefox-ios/Client/Telemetry/SponsoredTileTelemetry.swift, BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #9 — If anonymized user #9 becomes unavailable, 3 significant file(s) lose their only recent owner: firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/FolderSectionHeaderView.swift, firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/FolderTreeCell.swift, firefox-ios/Client/Frontend/Library/Bookmarks/Edit Folder/GroupedEditFolderViewModel.swift. Pair on, review, or document these before any departure.
Off-boarding risk: anonymized user #10 — If anonymized user #10 becomes unavailable, 3 significant file(s) lose their only recent owner: SampleComponentLibraryApp/SampleComponentLibraryApp/Headers/HeadersViewViewController.swift, firefox-ios/WidgetKit/SearchQuickLinksMedium/SearchQuickLinks.swift, firefox-ios/WidgetKit/SearchQuickLinksSmall/SmallQuickLink.swift. Pair on, review, or document these before any departure.
redundant comment REDACTED:770— "Disconnect mutation observer" repeats the code it sits on: 3 of its 3 words (disconnect, mutation, observer) are already in `this.#formMutationObserver.disconnect();`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment firefox-ios/Client/Assets/CC_Script/FormAutofillSection.sys.mjs:283— "Create a new section" repeats the code it sits on: 3 of its 3 words (create, new, section) are already in `sections.push(new FormSection([cur]));`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:230— "Check username and password values match what was filled." repeats the code it sits on: 5 of its 6 words (check, username, password, values, filled) are already in `if (`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:339— "Mask the password field" repeats the code it sits on: 3 of its 3 words (mask, password, field) are already in `this._togglePasswordFieldMasking(passwordField, false);`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment firefox-ios/Client/Assets/CC_Script/LoginFormState.sys.mjs:759— "we have at least the newPasswordField" repeats the code it sits on: 3 of its 3 words (new, password, field) are already in `[newPasswordField, confirmPasswordField] = pwGeneratedFields.map(`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment REDACTED:335— "If the password field is disabled or read-only, there's nothing to do." repeats the code it sits on: 5 of its 6 words (password, field, disabled, read, only) are already in `if (passwordField?.disabled || passwordField?.readOnly)`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment firefox-ios/Client/Frontend/UserContent/UserScripts/MainFrame/AtDocumentEnd/MetadataHelper.js:14— "Set metadata.url to document URL by default" repeats the code it sits on: 4 of its 5 words (set, metadata, url, document) are already in `metadata.url = document.URL;`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment firefox-ios/firefox-ios-tests/Tests/SyncIntegrationTests/test_bookmark.js:21— "sync and verify bookmarks" repeats the code it sits on: 3 of its 3 words (sync, verify, bookmarks) are already in `Phase("phase1", [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment firefox-ios/firefox-ios-tests/Tests/SyncIntegrationTests/test_history.js:23— "sync and verify history" repeats the code it sits on: 3 of its 3 words (sync, verify, history) are already in `Phase("phase1", [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
redundant comment firefox-ios/firefox-ios-tests/Tests/SyncIntegrationTests/test_tabs.js:21— "sync and verify tabs" repeats the code it sits on: 3 of its 3 words (sync, verify, tabs) are already in `Phase("phase1", [`. Delete it, or replace it with what the code cannot say (why it is done here, a constraint, or a consequence).
Silent fallback default in catch BrowserKit/Sources/TabDataStore/TabFileManager.swift:107— `contentsOfDirectory` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch firefox-ios/Client/Application/RemoteSettings/Application Services/ASAIRemoteConfig.swift:62— `decodeConfig` turns every thrown error into `[:]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch firefox-ios/Client/Frontend/Library/Downloads/DownloadFileFetcher.swift:36— `fetchData` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch firefox-ios/Client/Frontend/TrackingProtection/CertificatesHelpers/CertificatesModel.swift:38— `getDNSNamesList` turns every thrown error into `[]` — a data error becomes a silent behavior change with no trail. Log the error or let it propagate (`throws`). If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment at the `catch`, `guard` or `??`, or in the doc comment, and the row stops firing.
Silent fallback default in catch REDACTED:3448— `#matchesDocumentLanguage` swallows every exception into `return false` — a data error becomes a silent behavior change with no trail. Log the failure or let it raise. If that constant is the correct answer rather than a stand-in for a value that could not be read, say so in a comment on the handler or in the docstring, and the row stops firing.
P10 · Library API & versioning· Implementation type on the public API · ×3
Implementation type on the public API BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift:19— 2 public types in `BrowserKit~WebEngine` are marked as implementation by their own namespace, folder or name: `SchemeHandler` (BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift:19, `Internal`), `WKInternalSchemeHandler` (BrowserKit/Sources/WebEngine/WKWebview/Internal/WKInternalSchemeHandler.swift:29, `Internal`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/nimbus.swift:617— 4 public types in `MozillaRustComponents~FocusRustComponentsWrapper` are marked as implementation by their own namespace, folder or name: `GeckoPrefHandlerImpl` (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/nimbus.swift:617, name ends in `Impl`), `MetricsHandlerImpl` (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/nimbus.swift:899, name ends in `Impl`), `RecordedContextImpl` (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/nimbus.swift:2432, name ends in `Impl`), `BackendImpl` (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/viaduct.swift:575, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
Implementation type on the public API MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/db_crypto.swift:569— 7 public types in `MozillaRustComponents~MozillaRustComponentsWrapper` are marked as implementation by their own namespace, folder or name: `EncryptorDecryptorImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/db_crypto.swift:569, name ends in `Impl`), `KeyManagerImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/db_crypto.swift:804, name ends in `Impl`), `GeckoPrefHandlerImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/nimbus.swift:617, name ends in `Impl`), `MetricsHandlerImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/nimbus.swift:899, name ends in `Impl`), `RecordedContextImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/nimbus.swift:2432, name ends in `Impl`), `RemoteSettingsTelemetryImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/remote_settings.swift:1168, name ends in `Impl`), `BackendImpl` (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/viaduct.swift:575, name ends in `Impl`). While they are public, every consumer of the library can bind to them, so changing them is a breaking change for those consumers.
D21 · Naming Consistency· `FfiConverterTypeContextIDComponent` spells `ID` where 232 names in the project spell it `Id` · ×2
`FfiConverterTypeContextIDComponent` spells `ID` where 232 names in the project spell it `Id` MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/context_id.swift:712— 232 of 234 names in project MozillaRustComponents~FocusRustComponentsWrapper spell the token `Id` (232 of 234; unit: names in project MozillaRustComponents~FocusRustComponentsWrapper containing `Id`). Peers: MozAdsPlacementRequest.placementId (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/ads_client.swift:1532); MozAdsPlacementRequest.init(placementId) (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/ads_client.swift:1536); MozAdsPlacementRequestWithCount.placementId (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/ads_client.swift:1591); MozAdsPlacementRequestWithCount.init(placementId) (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/ads_client.swift:1595); MozillaRustComponents~FocusRustComponentsWrapper.ContextIdComponentProtocol (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/context_id.swift:579). Rename to `FfiConverterTypeContextIdComponent`. [rule N6]
`FfiConverterTypeContextIDComponent` spells `ID` where 232 names in the project spell it `Id` MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/context_id.swift:712— 232 of 234 names in project MozillaRustComponents~FocusRustComponentsWrapper spell the token `Id` (232 of 234; unit: names in project MozillaRustComponents~FocusRustComponentsWrapper containing `Id`). Peers: MozAdsPlacementRequest.placementId (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/ads_client.swift:1532); MozAdsPlacementRequest.init(placementId) (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/ads_client.swift:1536); MozAdsPlacementRequestWithCount.placementId (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/ads_client.swift:1591); MozAdsPlacementRequestWithCount.init(placementId) (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/ads_client.swift:1595); MozillaRustComponents~FocusRustComponentsWrapper.ContextIdComponentProtocol (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/context_id.swift:579). Rename to `FfiConverterTypeContextIdComponent`. [rule N6]
D16 · Bus Factor· Further sole-owners (lower concentration) · ×1
Further sole-owners (lower concentration) — 15 other contributor(s) are each the sole owner of a small amount of code below the off-boarding threshold — folded into the bus-factor score and metrics (104 single-owned of 1112 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1112 of the 2156 production source files in this repository met that bar). They are anonymized user #11 (2 file(s)), anonymized user #12 (2 file(s)), anonymized user #13 (2 file(s)), anonymized user #14 (2 file(s)), anonymized user #15 (1 file(s)), anonymized user #16 (1 file(s)) (+9 more) — spread or document their files in the same way, at lower priority than the named off-boarding risks above. The files folded here: scripts/update_release_notes.py, scripts/nightly_testflight_add_group.py, MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/ArgumentProcessor.swift, MozillaRustComponents/Sources/FocusRustComponentsWrapper/Nimbus/ArgumentProcessor.swift, firefox-ios/Client/Frontend/Settings/Main/Debug/LaunchPairingFromURLSetting.swift, firefox-ios/RustFxA/FxAPairingOAuthHandler.swift, BrowserKit/Sources/VPNKit/VPNAppAttestServer.swift, BrowserKit/Sources/VPNKit/VPNAuthService.swift (+11 more).
D20 · ADR Quality· ADR consequences name no cost · ×1
ADR consequences name no cost adr/0013-redux-state-reducers-best-practices-initialization-and-transient-state.md:116— `adr/0013-redux-state-reducers-best-practices-initialization-and-transient-state.md:116` records the good consequences of the decision and leaves the bad ones as a placeholder. State what this decision costs or rules out.
D21 · Naming Consistency· `PlacesAPI` spells `API` where 35 names in the project spell it `Api` · ×1
`PlacesAPI` spells `API` where 35 names in the project spell it `Api` MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Places/Places.swift:26— 35 of 36 names in project MozillaRustComponents~FocusRustComponentsWrapper spell the token `Api` (35 of 36; unit: names in project MozillaRustComponents~FocusRustComponentsWrapper containing `Api`). Peers: MozillaRustComponents~FocusRustComponentsWrapper.MozAdsClientApiError (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/ads_client.swift:2128); MozillaRustComponents~FocusRustComponentsWrapper.FfiConverterTypeMozAdsClientApiError (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/ads_client.swift:2151); MozillaRustComponents~FocusRustComponentsWrapper.FfiConverterTypeApiError (MozillaRustComponents/Sources/FocusRustComponentsWrapper/Generated/context_id.swift:778); MozillaRustComponents~MozillaRustComponentsWrapper.MozAdsClientApiError (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/ads_client.swift:2128); MozillaRustComponents~MozillaRustComponentsWrapper.FfiConverterTypeMozAdsClientApiError (MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Generated/ads_client.swift:2151). Rename to `PlacesApi`. [rule N6]
D21 · Naming Consistency· `generateUuidAndFormatAction` spells `Uuid` where 685 names in the project spell it `UUID` · ×1
`generateUuidAndFormatAction` spells `Uuid` where 685 names in the project spell it `UUID` firefox-ios/Client/Experiments/Messaging/GleanPlumbMessageManager.swift:237— 685 of 686 names in project DangerDependencies spell the token `UUID` (685 of 686; unit: names in project DangerDependencies containing `UUID`). Peers: View.listenToThemeChanges(windowUUID) (BrowserKit/Sources/Common/Theming/ThemeableView.swift:47); RootViewController.currentWindowUUID (SampleBrowser/SampleBrowser/UI/RootViewController.swift:22); RootViewController.init(windowUUID) (SampleBrowser/SampleBrowser/UI/RootViewController.swift:41); AccessoryViewProvider.windowUUID (firefox-ios/Client/AccessoryViewProvider.swift:36); AccessoryViewProvider.init(windowUUID) (firefox-ios/Client/AccessoryViewProvider.swift:215). Rename to `generateUUIDAndFormatAction`. [rule N6]
D26 · Project Cohesion· Projects may be oversized for their cohesion · ×1
Projects may be oversized for their cohesion — 4 of 8 project(s) overshoot their size bounds, lowering Project Cohesion to 0.0/10. The most over is `firefox-ios` (194255 LoC, 2520 module-visible types across 238 directories). Review these for cohesion — draw the boundary inside the module first (group each responsibility into its own package or directory and keep the cross-boundary members non-public), since splitting a published package moves types between packages and breaks consumers.
D34 · Knowledge Freshness· Further orphaned files (smaller) · ×1
Further orphaned files (smaller) — 134 smaller file(s) also have no living knowledge — folded into the freshness score and metrics rather than raised one row each — most significant first: MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Nimbus/FeatureVariables.swift, test-fixtures/generate-test-db.py, MozillaRustComponents/Sources/MozillaRustComponentsWrapper/Sync15/RustSyncTelemetryPing.swift, focus-ios/Blockzilla/Menu/Old/PhotonActionSheet.swift, firefox-ios/CredentialProvider/CredentialListViewController.swift, focus-ios/Blockzilla/Settings/Controller/SearchSettingsViewController.swift, SampleComponentLibraryApp/SampleComponentLibraryApp/Buttons/ButtonsViewController.swift, firefox-ios/Client/Experiments/Messaging/GleanPlumbMessageManager.swift (and 126 more) (135 orphaned of 1115 analysed files in total, counted over production source files of roughly 2,400 bytes or more, excluding vendored, generated, example/demo and scaffolding-template trees and test files identified by path convention, largest first; 1115 of the 2156 production source files in this repository met that bar). Attach the read to the next change that touches one of them: have a second person review that change, and leave behind a short comment or test recording what the file is for, so the knowledge comes back at the cost of a change you were making anyway.
Logging is not universal — Only 7/9 runnable modules use logging (modules with no entry point or server are excluded — they are libraries a runnable module hosts). Silent: `SampleBrowser`, `SampleComponentLibraryApp`.
No SAST .github/workflows/assign-tech-lead-review.yml:4— No static application security testing detected. For this repository's stack, add CodeQL's Swift pack (Swift/Xcode) (or `semgrep --config=auto`, which runs on any language) as a CI step. What was searched, so you can tell an absence from a miss: the 33 CI workflow file(s) in this repository, and the scanner and linter configuration checked in beside them. A scan that runs outside CI, one configured in your forge's web UI rather than in a committed file, or a tool whose name is none of those this check carries, is not seen — if that is your case the row is wrong, and saying so is more useful than adding a second scanner.
No dependency-update automation REDACTED:15— `REDACTED` declares packages, and nothing in the repository keeps them current: no Dependabot or Renovate configuration that schedules updates, and no dependency-review gate on pull requests. A pinned dependency stays at the version it was added at until someone notices — including after an advisory is published against it. Add a `.github/dependabot.yml` with one `package-ecosystem` entry per ecosystem the tree uses (or an enabled `renovate.json`), and gate pull requests with `actions/dependency-review-action`.
No changelog — No CHANGELOG/HISTORY/RELEASES file — what shipped when isn't easy to reconstruct for support or audit. (Versioning/tagging makes releases traceable, but a changelog records the what.)
X5 · Nullable reference types· Ruby's type checker does not check nil everywhere · ×1
Ruby's type checker does not check nil everywhere — This repository commits no Sorbet configuration (`sorbet/config`) and no `Steepfile`, so nothing type-checks its 1 Ruby product file(s): a nilable value reaches a method call silently and raises `NoMethodError: undefined method … for nil` the first time it is nil. A `# typed:` sigil does nothing without a `sorbet/config` beside the code; a Steep run configured only on a command line is not something this check can read.
Outdated: kingfisher — `kingfisher` is resolved at 8.15.0, but 8.16.0 is the newest release tagged on https://github.com/onevcat/Kingfisher.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update kingfisher` reaches this one with no change to Package.swift.
Outdated: sentry-cocoa — `sentry-cocoa` is resolved at 9.32.0, but 9.34.0 is the newest release tagged on https://github.com/getsentry/sentry-cocoa.git within the same major. SwiftPM resolves from git tags, and a `from:` requirement admits every release below the next major — so `swift package update sentry-cocoa` reaches this one with no change to Package.swift.
doc comments repeat the names firefox-ios/Client/Assets/CC_Script/FieldScanner.sys.mjs:260— 3 of 256 documented parameters and 5 of 628 summaries in `@mozilla/firefox-ios` only repeat the member or parameter name (e.g. "The new name of the field" for `fieldName`). Delete the restating tags, or add what the name does not say.
Appendix B — Reproduction & audit trail
Every external tool invocation behind a deep-scan dimension — the tool, its captured version, the exact command, how many findings it yielded, and a link to the retained raw output. To reproduce any finding: check out the same commit and run the command shown (repo-relative — never an absolute scratch path). The complete raw scanner output is retained verbatim under artifacts/raw/ (indexed in artifacts/raw/index.json); per-invocation exit codes and wall-clock durations are in sidecar.json — kept out of this table so the rendered report stays byte-identical across runs of the same commit.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; network egress policy is a cluster-native control that may live at the platform/firewall layer, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; seccomp/AppArmor/SELinux confinement is a workload-level control, so there is nothing to assess here.
runtime-hardening: not applicable — No Kubernetes/orchestration workloads found in the repository manifests; runtime threat-detection and admission-control policy are cluster-level controls, so there is nothing to assess here.
Run 01a1d961-5950-7705-83d9-80789a9e4aa1 · every finding is also locatable in findings.md, and the complete scoring record (with exit codes + durations) in sidecar.json.
Issues: 53 · Warnings: 2306 · Recommendations: 263 · Info: 3 — Appendix A · all findings · full markdown report.
Generated by the Canine Code Analyzer: deterministic code-health analysis. 14-11-2026 @ 09:26 UTC.
Downloadable artifacts
Machine-readable and reproducible from this commit + frozen rubric — drop them straight into a contract appendix, a CRA dossier, or a downstream SCA / VEX tool.