* Initial org filter work
* update jslib
* Move filter to below cipher length check
* don't show vault filter in personal or org folder
* Use family icon for families org
* jslib and auth guard updates
* lint fixes
* rename GroupingsComponent to VaultFilterComponent
* fix no folder showing all items
* Add checks for PersonalOwnership policy
* update css class names
* lint fixes
* cleanup
* Some final cleanup
* import order lint fix
* remove unused import
* Use smaller icon for chevron
* Update src/popup/vault/organization-filter.component.ts
Co-authored-by: Addison Beck <addisonbeck1@gmail.com>
* Update src/popup/vault/organization-filter.component.ts
Co-authored-by: Addison Beck <addisonbeck1@gmail.com>
* fix lint error
* remove extra localizations
* rename orgFilter -> vaultSelect
* Rename orgFilterService to VaultSelectService
* lint fixes
* combine vault select service with vault filter service
* Use base vault filter service methods
* Use VaultFilter model and other small fixes
* lint fixes
* Final restructuring pass
* Update jslib and remove extra function
* Remove extra imports
* remove space
* Remove vaultFilterService from background services
* Update jslib to latest on feature branch
* merge fix
* update jslib
* [feat] Implement EUVR for desktop
Should contain only https://github.com/bitwarden/desktop/pull/1487, with merge resolutions and style fixes
* [fix] Delete unused GroupingsComponentTemplate
* [dep] Update jslib
Co-authored-by: Addison Beck <addisonbeck1@gmail.com>
* Change send list controls to buttons
make them keyboard focusable/operable
* Fix width/display of sends
* Make `.row-btn.disabled` also apply to natively `disabled` buttons without need for class
* Change accessible name for send group to use the send's name, not generic "Edit item" title
* Update publish settings to use S3
* Fix formatting
* Added endpoint with new domain
* Updated S3 publisher config
* added npm CD commands for workflow later.
* Updated release workflow to publish to S3
* testing release
* Reduce aws cli output
* Remove test
* Finalize release workflow
- Reverted back testing logic
- Removed dry run check for GH release since it creates it as a draf anyways
- Removed artifact_url env as it's no longer needed.
* Remove testing values
* Merge Master
* Added endpoint in config
* Change links to buttons, expose `aria-pressed` for toggles
- also make existing `<a routerLink...>` type controls keyboard focusable with the addition of `tabindex="0"`
* Correctly set aria-pressed
now that I have a working build environment, could verify correct way to set this with my limited Angular knowledge
* Change more links to buttons, initial style changes
* Fix layout of <button> elements with .box-content-row
* Update jslib submodule
* Add `aria-expanded` to the send view's "Show options" expand/collapse control
* Fix position of "Edit" pencil when hovering over folders
* Update jslib
* Change sends list links to buttons
* Add `aria-pressed` to vault and send list buttons
Programmatically denote which of the buttons is currently active/shown in the right-most panel
* Fix incorrect "Options" expand/collapse button in add-edit view
Currently, that buttons lacks an accName because the "Options" text is outside of it.
* Add `aria-pressed` to the send left-hand column filters
* Simplify base, list, and vault styles
Since links are now buttons, no need to double up selectors for both types of elements. No need to double-up theming in base, as this also causes incorrect "x" in toasts.
* Remove unnecessary `position:relative`
Fixes issue with cut-off focus outlines, has no other adverse effect
* Fix styling for last child of action buttons
Old approach of making right padding smaller results in unsightly, off-center icon (noticeable when focus outline is visible). This visually remains the same, but reduces right-hand margin instead.
* Make <content> element explicitly non-focusable
Some browsers (Firefox, upcoming versions of Chrome https://bugs.chromium.org/p/chromium/issues/detail?id=585413) make containers with `overflow: auto` / `overflow: scroll` (and the `-x` / `-y` variants) keyboard-focusable. This leads to a very awkward experience for assistive technology users navigating through the extension window, as for every view, the entire `<content>` container receives focus (and screen readers try to announce all its content in one go) before you reach the actual first control. To counteract this behaviour, this adds an explicit `tabindex="-1"` to these elements.
* Change `<content>` to `<main>`
More semantically accurate. See https://github.com/bitwarden/browser/pull/2245#issuecomment-1104553312
* Update scss to target `main` instead of `content`
* Change the previously existing `<main>` to generic `<div>`, tweak styles accordingly
Can't have two separate `<main>` elements, especially not nested ones. The original `<main>` was really just a handy wrapper for the component, but semantically should be neutral
