Skip to content
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

Move style rules of MatrixChat_useCompactLayout from _GroupLayout.scss #22434

Closed
luixxiul opened this issue Jun 3, 2022 · 0 comments · Fixed by matrix-org/matrix-react-sdk#8766
Labels
Help Wanted Extra attention is needed O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Task Tasks for the team like planning

Comments

@luixxiul
Copy link

luixxiul commented Jun 3, 2022

Steps to reproduce

Technically, .mx_MatrixChat_useCompactLayout .mx_EventTile is not relevant to _GroupLayout.scss so it could be moved to a corresponding SASS file, but moving the block from there to _EventTile.scss has broken the compact layout somehow. After the incident the rule structure was analyzed and it was found out that it was due to cascading order.

See: matrix-org/matrix-react-sdk#8725

Outcome

What did you expect?

The style block .mx_MatrixChat_useCompactLayout .mx_EventTile should not belong to _GroupLayout.scss as the block is not included in .mx_GroupLayout selector, which was removed recently.

What happened instead?

Moving the block from _GroupLayout.scss to _EventTile.scss has broken the compact layout because of cascading order.

Operating system

No response

Browser information

No response

URL for webapp

No response

Application version

develop branch

Homeserver

No response

Will you send logs?

No

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Help Wanted Extra attention is needed O-Occasional Affects or can be seen by some users regularly or most users rarely S-Minor Impairs non-critical functionality or suitable workarounds exist T-Task Tasks for the team like planning
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants