… does anyone know the reason to deprecate “starts with”, “regular expression” and “never” as default URI match detection settings? (
main ← PM-22162-remove-starts-with-never-and-regular-expression-options-from-the-autofill-global-settings
opened 05:45PM - 04 Jun 25 UTC
## 🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-22162
## 📔 Object… ive
Deprecate the use of `starts with`, `regular expression` and `never` for global match strategy settings
## 📸 Screenshots
## ⏰ 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
I don’t know if I ever would use “never” or “regular expression” - but to lose “starts with” as an option, is a bit unfortunate for me…
PS: I chose “app:all”, because I guess this change will affect the browser extensions, mobile app and the future desktop app.
PPS: Those who use this setting, will eventually see a “migration message” - whenever this will get implemented:
main ← PM-22164-migrate-existing-users-with-starts-with-and-regular-expression-set-as-the-global-autofill-option-to-base-domain
opened 04:29PM - 04 Jun 25 UTC
## 🎟️ Tracking
https://bitwarden.atlassian.net/browse/PM-22164
## 📔 Object… ive
When a user has `Starts with` or `regular expression` as their default global URI matching strategy, when the user hits the vault view, they will be prompted with a dialog which will not disappear until acknowledged which will set their global setting to `Base`.
## 📸 Screenshots
https://github.com/user-attachments/assets/97050587-6e41-46c3-a7a7-7ee0b2505155
## ⏰ 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
1 Like
this change seems to be about the global/default setting only – as I understand it, it will still be possible to set these for individual URIs in login items!)