* PM-14445: TS strict for Key Management Biometrics
* formatting
* callbacks not null expectations
* state nullability expectations updates
* unit tests fix
* secure channel naming, explicit null check on messageId
* KM-14445: TS strict for Key Management, Keys and Lock component
* conflicts resolution, new strict check failures
* null simplifications
* migrate legacy encryption when no active user throw error instead of hiding it
* throw instead of return
* Exposes URI property from the cipher form.
* Updates credential generator to accept the URI using a `website` attribute
---------
Co-authored-by: ✨ Audrey ✨ <audrey@audreyality.com>
* pm-18084 -initial structure and functions implemented
* update stories to match new args
* change handleSave name
* include new login button for save
* fix stories
* Use new <bit-form-field> component in Excluded domains settings.
Changing to new <bit-form-field> component necessitates modifying form to use ReactiveForms conventions. To handle this change, the deletable/uneditable domain state and new form control state are managed separately, including clearing the form state on save. Fields which compute vaules from the former state should now compute both values (see domain count); [formGroup], formArrayName, formControlName all necessary directives/properties on form and children.
* Disables margin; Removes OnInit in favor of protected member (fixes lint, and type checks).
* Ensure excludedDomain-based IDs are offset by the fieldsEditThreshold for form controls existing outside of stored values.
* Remove unnecessary chaining.
Don't reuse a global mock for this spec entitled autofillFieldData with username data modified to have a password "type". Instead create a new passwordFieldData, satisfying the conditions of a failing test caused by new inline field qualification service.
* Add way to convert TaskSchedulerService to RX Scheduler
* Add docs to `toScheduler`
* Rollback combined subscription change.
* Move to barrel file
* Expand `toScheduler` documentation
* Add TaskName to Doc Example
* Ensure register is called on service worker start
* add browser extension prompt page with initial loading state
* add browser extension icon
* move browser extension prompt to state
* add installation link for error state
* automatically open extension when possible for browser-reprompt-page
* refactor browser tabs query into a standalone method
* add success message state for auto-opening browsers
* Refactor `VaultOnboardingMessages` to `VaultMessages` to be more generic
* add auto-open extension messages to `VaultMessages` enum
* add bitwarden icon
* Add manual error state for firefox users
* add extension prompt routing
* fix incorrect imports
* add mobile screen for browser prompt
* remove comment
* fix typo in code comment
* update key for `checkBwInstalled` method
* add check for safari before attempting to send a message
* break translation for manual opening into two parts
Angular CKD LiveAnnouncer depends on some css logic to hide announcements from being displayed.
This imports the required CSS to ensure the text is hidden from regular view.
* Changes for the existing users
* Remove the complicated method
* add the column after the patch value
* Revert removal of plan query params
* Resolve the non blocking issue
- Add recovery code enum and feature flag
- Update recovery code text and warning messages
- Log user in and redirect to two-factor settings page on valid recovery code
- Run full sync and handle login errors silently
- Move updated messaging behind feature flag
PM-15534
* update main context menu handler to skip creating menu entries which do not pass blocked uri checks
* refactor to remove menu entries which do not pass blocked uri checks
* allow context menu autofill items without a password if they have other autofillable attributes
* include ciphers without passwords in autofill context menu options and track context menu state
* Migrate export from generator-legacy to generator-core
* Remove unused platformUtilsService
* Wire up password generation within ngOnInit
---------
Co-authored-by: Daniel James Smith <djsmith85@users.noreply.github.com>
Angular 6 changed the default to not preserve whitespaces. We've continued to opt into this pattern for backwards compatibility but we're experiencing issues with the new control flow syntax and would therefore like to switch and not preserve whitespace any longer.
