* Don't reference the notification levels by colour
We're about to change what colours they are so either we'd have to rename
a bunch of constants. We may as well make things not reference what colour
anything is in the actual UI. Hopefully these constants are clear enough.
* Rename NotificationColor -> NotificationLevel
* Red -> Highlight
* Grey -> Notification
* Bold -> Activity
* Anywhere else that calls it 'color' -> 'level'
Also fixes some weird mixes of US & UK English.
It turns out this is referenced in... quite a lot of places, so this is
quite a large PR. It can't really be much smaller, sorry.
* One test rename & some hiding due to ts-ignore
* More hiding behind ts-ignore
* Damn you, @ts-ignore...
* Fix test CSS values
* Missed some colour -> level
Co-authored-by: Florian Duros <florianduros@element.io>
* Change other instances of variables renamed in suggestion
* Update new test for renames
---------
Co-authored-by: Florian Duros <florianduros@element.io>
* Update dependency @vector-im/compound-web to v2
* Update Tooltip props
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Include TooltipProvider in MatrixChat
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Fix pillify & tooltipify
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Update tests to use TooltipProvider where necessary
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Fix tooltips in Modals, ContextMenus, PersistedElements, Spoiler, HtmlExport
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Update tests
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* delint
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Update tests
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Fix tooltips in HTMLExport
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Don't pass mountAsChild to DOM
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* prettier
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
* Stabilise test
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
---------
Signed-off-by: Michael Telatynski <7t3chguy@gmail.com>
Co-authored-by: renovate[bot] <29139614+renovate[bot]@users.noreply.github.com>
Co-authored-by: Michael Telatynski <7t3chguy@gmail.com>
* Gracefully hand rate limit response when attempting to Sign in with QR
* Don't cancel after rate limit
* Update src/components/views/auth/LoginWithQR.tsx
Co-authored-by: Michael Telatynski <7t3chguy@gmail.com>
* Add missing import
* Fix mock of error
---------
Co-authored-by: Michael Telatynski <7t3chguy@gmail.com>
* inline call to `SettingsStore.isEnabled`
* Remove confusing `SettingsStore.isEnabled`
This was basically the same as `SettingsStore.canSetValue` only more confusing,
so let's get rid of it.
* Add `configDisablesSetting` value for Settings
The current magic where this only works for features (but not beta features!)
is, well, magical. And I need more flexibility here.
* Remove redundant levels constant `LEVELS_FEATURE`
I don't know if this was ever intended to have different semantics to
`LEVELS_DEVICE_ONLY_SETTINGS_WITH_CONFIG`, but if it was, those semantics
shuold have been written down. They now seem to be used entirely
interchangably.
* Ensure backup settings in playwright
* Fix verification by pass causing backup reset
* fix force backup setup by default
* fix test
* clarify when we need to bootstrap
* jslint
* post merge fix
* post rebase missing files
* fix bad merge
* update test
* Fix import
* test user forgot passkey
* better usage of locator
* fix snapshot
* remove getDialogByTitle
* Update src/async-components/views/dialogs/security/CreateKeyBackupDialog.tsx
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
* unneeded permission
* code review
* cleaning
---------
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
