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

[bug]: No property available to stack date and time picker fields vertically [column instead of row] #1853

Open
TMSchipper opened this issue Feb 6, 2025 · 0 comments
Labels
issue: bug Issue reporting a bug status: pending reproduction Waiting for free time to reproduce the issue, or more information

Comments

@TMSchipper
Copy link

What version of design-system are you using?

"@strapi/strapi": "^5.2.0",
"@strapi/design-system": "2.0.0-rc.11",

What's Wrong?

The date and time picker components in the Strapi Design System currently render in a single row, with no available property or option to display them stacked vertically. This causes layout issues, particularly in narrow side panels (such as the content manager sidebar), where the elements overflow beyond the container.

Image

To Reproduce

Use the component in a small container (e.g., a sidebar).
Notice that the date and time fields are displayed inline (horizontally), leading to overflow issues.
There is no documented property to switch to a vertical layout.

Expected Behaviour

There should be a property (e.g., stacked or layout="vertical") to allow developers to control whether the date and time fields are displayed:

Horizontally (default behavior)
Vertically (one field below the other)
This would improve usability and allow for better responsive layouts.

@TMSchipper TMSchipper added issue: bug Issue reporting a bug status: pending reproduction Waiting for free time to reproduce the issue, or more information labels Feb 6, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
issue: bug Issue reporting a bug status: pending reproduction Waiting for free time to reproduce the issue, or more information
Projects
None yet
Development

No branches or pull requests

1 participant