You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Message previews truncate at 100 characters despite available column space #461
Message previews are cut to 100 characters even when the Message column has room to show more text.
On develop cde6d1b, syslog_message_button() calls title_trim((string) $message, 100) before sending the preview to the browser. The existing .syslogMessageOpen CSS already uses overflow: hidden, white-space: nowrap and text-overflow: ellipsis, so the server-side cut leaves unused space on wider screens.
To reproduce, open System Logs with a message longer than 100 characters and widen the browser. The preview still ends at the same character limit. Clicking it opens the complete message in the details pane.
The preview should receive the full escaped message and fill the available column width. Ellipsis should appear only when the rendered text exceeds that width. Keep the existing single-line layout, escaping and full-message details behavior. No stored-message or schema changes are needed.
Proposed fix: #462. The preview now receives the full escaped message and uses the existing CSS ellipsis to fit the column. Regression tests cover long ASCII, Unicode and HTML-like messages; the workspace browser checks cover wide and narrow layouts and the full-message details pane.
Activity
somethingwithproof commentedon Nov 17, 2026
Proposed fix: #462. The preview now receives the full escaped message and uses the existing CSS ellipsis to fit the column. Regression tests cover long ASCII, Unicode and HTML-like messages; the workspace browser checks cover wide and narrow layouts and the full-message details pane.