Skip to content

Conversation

KatherineInCode
Copy link
Contributor

🎟️ Tracking

https://bitwarden.atlassian.net/browse/PM-25859

📔 Objective

This updates the Generator screen on iOS 26 to remove the gray background, and also uses a native Segmented Picker instead of a custom one in order to better handle colors and glass transparency.

📸 Screenshots

Simulator Screenshot - iPhone 16 Pro - 2025-09-18 at 12 31 44

⏰ Reminders before review

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

🦮 Reviewer guidelines

  • 👍 (:+1:) or similar for great changes
  • 📝 (:memo:) or ℹ️ (:information_source:) for notes or general info
  • ❓ (:question:) for questions
  • 🤔 (:thinking:) or 💭 (:thought_balloon:) for more open inquiry that's not quite a confirmed issue and could potentially benefit from discussion
  • 🎨 (:art:) for suggestions / improvements
  • ❌ (:x:) or ⚠️ (:warning:) for more significant problems or concerns needing attention
  • 🌱 (:seedling:) or ♻️ (:recycle:) for future improvements or indications of technical debt
  • ⛏ (:pick:) for minor or nitpick changes

Copy link
Contributor

github-actions bot commented Sep 18, 2025

Logo
Checkmarx One – Scan Summary & Detailsa79e43aa-15c0-4308-85f8-416b5106a0d8

Great job! No new security vulnerabilities introduced in this pull request

@KatherineInCode KatherineInCode marked this pull request as ready for review September 18, 2025 17:47
Copy link

codecov bot commented Sep 18, 2025

Codecov Report

❌ Patch coverage is 85.07463% with 20 lines in your changes missing coverage. Please review.
✅ Project coverage is 88.64%. Comparing base (6d83b12) to head (41c3529).

Files with missing lines Patch % Lines
.../Application/Views/BitwardenSegmentedControl.swift 73.17% 11 Missing ⚠️
...d/UI/Tools/Generator/Generator/GeneratorView.swift 91.86% 7 Missing ⚠️
...latform/Application/Extensions/View+Backport.swift 71.42% 2 Missing ⚠️
Additional details and impacted files
@@            Coverage Diff             @@
##             main    #1952      +/-   ##
==========================================
- Coverage   88.67%   88.64%   -0.04%     
==========================================
  Files         822      822              
  Lines       51767    51820      +53     
==========================================
+ Hits        45905    45936      +31     
- Misses       5862     5884      +22     

☔ View full report in Codecov by Sentry.
📢 Have feedback on the report? Share it here.

🚀 New features to boost your workflow:
  • ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

Comment on lines +23 to 30
if #available(iOS 26, *) {
ZStack(alignment: .top) {
internalView(geometry: geometry)
}
} else {
VStack(spacing: 0) {
internalView(geometry: geometry)
}
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

🤔 Can we use ZStack in both versions? or does it look weird when the same stack is used pre-post iOS 26?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

If you do it with a ZStack older than iOS 26, it would still need to do the VStack in iOS 16 and 15, because some of the necessary APIs to make the ZStack look right (onGeometryChange, contentMargins) don't go back that far. It therefore seemed more logical to me to differentiate at iOS 26 itself, and try to preserve how we did it pre-26 as closely as possible.

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

Successfully merging this pull request may close these issues.

2 participants