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

fix(regression): bad post actions alignment introduced in #3540 #3619

Merged
merged 3 commits into from
Sep 3, 2022

Conversation

SychO9
Copy link
Member

@SychO9 SychO9 commented Aug 26, 2022

Fixes a regression introduced in #3540

Changes proposed in this pull request:

Screenshot
Screenshot from 2022-08-26 13-51-25

Necessity

  • Has the problem that is being solved here been clearly explained?
  • If applicable, have various options for solving this problem been considered?
  • For core PRs, does this need to be in core, or could it be in an extension?
  • Are we willing to maintain this for years / potentially forever?

Confirmed

  • Frontend changes: tested on a local Flarum installation.
  • Backend changes: tests are green (run composer test).
  • Core developer confirmed locally this works as intended.
  • Tests have been added, or are not appropriate here.

@SychO9 SychO9 changed the title fix: bad post actions alignment introduced in #3540 fix(regression): bad post actions alignment introduced in #3540 Aug 26, 2022
@davwheat
Copy link
Member

davwheat commented Aug 26, 2022

Could we investigate the idea of using flex/grid instead of float for the stream/nav elements? This should let us reimplement the clearfix, while not affecting the height of the first post.

This (obviously implemented with a media query in core):
image

Plus removing the margin-right on the stream seems to do the trick.

We can then add back clearfix:

image

And then actions show correctly:

image

@SychO9
Copy link
Member Author

SychO9 commented Sep 1, 2022

@davwheat I'm worried it might easily break any existing custom styling, I think it would make more sense to do that in 2.0 when we refactor it all?

@davwheat
Copy link
Member

davwheat commented Sep 1, 2022

I'm somewhat of the opinion that custom theming should be done with the new Less extenders we have to override files. In this case, as there are no DOM changes, there's no issue here.

Doing full rethemes without overriding the Less source results in even more CSS bloat than we currently have, which is an issue imo.

We've also done other Flex/Grid refactors in 1.x (Notifications List in 1.3, for example)

Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
@SychO9 SychO9 force-pushed the sm/post-actions-align-regression branch from 125ad9b to 5d745ab Compare September 2, 2022 17:50
@SychO9 SychO9 requested a review from davwheat September 2, 2022 17:57
Signed-off-by: Sami Mazouz <sychocouldy@gmail.com>
@SychO9 SychO9 requested a review from davwheat September 3, 2022 11:33
@SychO9 SychO9 self-assigned this Sep 3, 2022
@SychO9 SychO9 merged commit 31f1ffd into main Sep 3, 2022
@SychO9 SychO9 deleted the sm/post-actions-align-regression branch September 3, 2022 12:30
@SychO9 SychO9 added this to the 1.5 milestone Sep 3, 2022
@luceos luceos mentioned this pull request Sep 8, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants