* Use `getShowSasCallbacks()` and `getShowQrCodeCallbacks()`
... instead of type-casting
* Update method names
These methods got renamed in the js-sdk PR
* Fix strict typing errors
* Use CSS custom properties on _LeftPanel.pcss
* Use CSS custom properties on _SpacePanel.pcss
* Use CSS custom properties on _SpaceRoomView.pcss
* Use CSS custom properties on _ImageView.pcss
* Use CSS custom properties on _EventTile.pcss
* Remove a CSS custom properties on _SpaceCreateMenu.pcss
Used only on one instance
* Revert "Use CSS custom properties on _ImageView.pcss"
This reverts commit 0210659f94fcf1107adabecf1bce443fc970a31b.
* Revert "Use CSS custom properties on _EventTile.pcss"
This reverts commit 83cf824a57b174e62935bb9a4433aadcd8f8164f.
* Run prettier
* Inline `VerificationRequest.{invalid,ready,started,done,cancelled}`
These methods are all just shortcuts for checks on `phase`, so let's get rid of
them
* update test
* Add some more tests
* even more coverage
* fix tests
* Inhibit interactions on forward dialog message previews
and improve inhibiting of video message body
* Consolidate prop types
* Iterate
* Update src/components/views/messages/IBodyProps.ts
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
---------
Co-authored-by: Richard van der Hoff <1389908+richvdh@users.noreply.github.com>
* When joining room in sub-space join the parents too
* Fix joined state not updating on sync
* Add membership check
* Update tests
* Improve coverage
* Make TS happier
* Make TS happier
* Remove STIXGeneral from the font stack
STIXGeneral was originally added to our font stack to work around a bug in Chrome (https://bugs.chromium.org/p/chromium/issues/detail?id=591346) which caused some obscure combining marks to render as tofu. However, because STIXGeneral unexpectedly has glyphs for a handful of common Japanese characters, it's ended up making Japanese text in Element look patchy. I previously attempted to fix this by prioritizing sans-serif over STIXGeneral, but as is evident from our screenshot tests and user reports, this is still not enough on some systems to get Chrome to pick a consistent font for Japanese. On the basis that i18n is more important than supporting a few mathematical diacritics, I propose we remove the font. STIXGeneral is deprecated anyways, so if we want to get these diacritics back there's always the option of looking at its successor, STIXTwo.
* Remove STIXGeneral installation from Cypress workflow
* add aria-label to default homeserver checkbox
* test ServerPickerDialog
* remove debug
* strict fixes
* dont validate unselected server field on ServerPickerDialog
* i18n
