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

[5.x]: Header section layout on smaller devices looks broken #16532

Open
JayBox325 opened this issue Jan 26, 2025 · 3 comments
Open

[5.x]: Header section layout on smaller devices looks broken #16532

JayBox325 opened this issue Jan 26, 2025 · 3 comments
Labels

Comments

@JayBox325
Copy link
Contributor

JayBox325 commented Jan 26, 2025

What happened?

Description

The layout of the header sections on mobile or smaller tablets looks broken with how the layout has been styled. See here:

Image Image

Steps to reproduce

  1. Create an entry type
  2. Create an entry
  3. View on smaller viewports

Expected behavior

I'd expect the buttons and title to stack much smarter than they currently do. I have achieved this by editing the markup in the Inspector by just using the three-dots "more" button to hide more of the options, as these buttons are utility actions that could be hidden at this size, but also aligning the actions to the left to match the title.

One of the problematic elements is the .activity-container div which throws extra gap spacing in at the start when it's empty.

Image

Actual behavior

As per the screenshot in the Description.

Craft CMS version

5.6.0.2

PHP version

No response

Operating system and version

No response

Database type and version

No response

Image driver and version

No response

Installed plugins and versions

@JayBox325 JayBox325 added the bug label Jan 26, 2025
@brandonkelly
Copy link
Member

Related: #16524

@JayBox325
Copy link
Contributor Author

Hah, sorry @brandonkelly, they're both mine! I can combine them into one ticket if that's easier?

@brandonkelly
Copy link
Member

@JayBox325 It’s fine, they’re both slightly different issues, but could probably be tackled together.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

2 participants