Marquee / Scrolling Text Component #4456
alrescha79-cmd
started this conversation in
Ideas / feature requests
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
-
I would like to propose adding a Marquee (scrolling text) component to DaisyUI.
This component allows text or inline content to automatically scroll when the content width exceeds the available space. It can be particularly useful in responsive interfaces, dashboards, and compact UI elements where long text must remain readable without breaking layout.
Although this can be implemented with custom CSS animations, a built-in DaisyUI component would make it easier to reuse and maintain consistent behavior across different interfaces.
Use Cases
Limited Space UI Elements
Many UI components have fixed or constrained widths such as badges, chips, tabs, or labels. When text exceeds the available width, it may be truncated or overflow the layout. A marquee component allows the full content to remain visible without expanding the component size.
Example:
Mobile View With Limited Screen Space
On mobile devices, screen width is significantly smaller. Long text inside headers, navigation bars, or cards often becomes truncated. A scrolling text component can help preserve readability while maintaining a clean layout.
Example:
Navigation Bars or Page Titles
Page titles or navigation labels sometimes exceed available space, especially in responsive layouts.
Example:
Table Cells With Long Content
Tables often contain long identifiers such as filenames, transaction IDs, hashes, or descriptions that do not fit inside a cell.
Example:
Notification or Announcement Banners
Announcements, alerts, or system messages may contain longer messages than the container width.
Example:
Dashboard Widgets or Monitoring Panels
Monitoring dashboards or status panels sometimes display long system messages, logs, or status descriptions within a small widget area.
Example:
Compact Components (Badges, Chips, Tags)
Compact UI elements often have strict width constraints but may still need to display dynamic content.
Example:
Information Tickers or Data Streams
Some interfaces display continuously updating information such as messages, statistics, or updates.
Example:
Proposed API
Basic usage:
Possible Variants
Benefits
Alternative Approaches
This behavior can currently be implemented using custom CSS animations. However, having an official DaisyUI component would improve consistency and developer experience across projects.
If this idea aligns with the project goals, I would be happy to contribute the implementation and open a pull request.
Beta Was this translation helpful? Give feedback.
All reactions