-
-
Notifications
You must be signed in to change notification settings - Fork 2.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Fix extensions panel style #29273
base: develop
Are you sure you want to change the base?
Fix extensions panel style #29273
Conversation
Changes LGTM 👍 |
await viewRoomSummaryByName(page, app, ROOM_NAME); | ||
|
||
await page.getByRole("menuitem", { name: "Extensions" }).click(); | ||
await expect(page.locator(".mx_RightPanel")).toMatchScreenshot("with-extensions.png"); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Can we use an accessible role instead of a css class as selector?
top: -76px; | ||
} | ||
|
||
.mx_EmptyState { | ||
/* Stop empty state scrolling */ | ||
height: calc(100% - 76px); |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Maybe declare a CSS variable with -76px
value and use it in the _ExtensionsCard.pcss
file
As a part of design review in https://github.com/element-hq/wat-internal/issues/242
What does this PR do?
What does it looks like?
Before

After
