Sommario quotidiano (5:00 UTC)

Notizie ed Eventi Riassunti del forum
802

Today on meta.discourse.org…

Key Stats

Interesting Topics

#customization:theme-component

  • NateDhaliwal published “Highlight to Search”, a theme component that lets users highlight text inside a post and instantly search for it (either via Discourse search or an external engine) — a neat “micro-productivity” win for readers and moderators alike read more. For setup references, see theme/component install instructions and the themes beginner guide.

  • nathank released “Upcoming Events Extra Buttons”, adding configurable Subscribe and (optionally) Create event buttons to /upcoming-events, aimed at reducing friction for event-heavy communities read more. Related background: discussion around event UX expectations continues in calendar threads like closed events visibility and broader event workflow ideas read more.

  • The long-running Kanban Board component got another round of “is it broken on Horizon?” testing: Lew_Grothe reported it not working, Arkshine suggested basic checks (component attachment + console errors), and nathank shared CSS to widen the Kanban layout under Horizon’s tighter center column read more.

  • In Discourse Lucide Icons, cuo_wu hit an issue where the calendar-heart icon wouldn’t render even after adding it to custom SVGs, and nathank clarified that the “extra icons” mechanism is Font Awesome 6-oriented—Lucide additions should follow the custom SVG replacement approach read more, with the canonical how-to here: Replace default SVG icons in a theme.

  • User Field Prompt got a documentation/UI mismatch callout: Moin noted the first-post screenshot is now misleading because the field title/description display differs from what admins see in preferences, suggesting an update for less surprise read more.

  • Banner Featured Links support continued in French: gilles wanted the buttons shown beyond the homepage, and Arkshine pointed to selecting the right plugin outlet (and checking “URL must contain”), recommending the Developer Toolbar to discover outlet placement read more. The referenced helper tool: Introducing Discourse Developer Toolbar.

bug

  • A fresh RTL regression report: topic title input stays LTR on RTL sites. Nima1 described how dir="auto" causes empty inputs to render LTR (cursor/selection/placeholder feel wrong), and sam confirmed it’s not solvable with CSS alone—proposing a markup behavior change (default RTL until typing begins, then switch to auto) with a linked PR read more. Cross-reference: sam noted this also covers older reports like “Titles placeholder in New topic is not RTL” read more.

  • The composer cursor “jumping around” thread resurfaced with a video showing the editor snapping position during longer edits; renato suspected it was actually the Markdown split-preview composer (not ProseMirror) and asked for cross-instance reproduction steps to narrow it down read more.

  • Cooked error after translate: cuo_wu reported that translating content (with SC language enabled) seemed to trigger cooked/format issues; Moin traced at least one culprit to malformed table pipes—tweaking the English source fixed the German translation output too, suggesting translation pipelines can be less forgiving than the main renderer read more.

ux

  • On mobile, Canapin suggested the share modal should place the Copy button on the same line as the URL input (better thumb reach, less wasted vertical space) read more. This fits neatly alongside other Meta-mobile layout nits being tracked in the ongoing theme work (e.g. leaderboard overflow on mobile) read more.

  • Closed events don’t display in the upcoming-events calendar: Ethsim2 argued that “Close event” has become a practical way to hide items without BBCode hacks, and asked that closed events remain visible—or alternatively that Discourse add a separate “Delete event” (or rebrand “Close” to “Hide”) to clarify intent read more. Adjacent calendar discussions keep circling back to workflow and visibility: recurring-event topic creation expectations read more and “Add to calendar” integration requests read more.

  • Notification count persistence: sixty4bit described the current behavior (count clears after opening the avatar menu) as actively harmful for low-volume-but-critical PM workflows (e.g. support inboxes), arguing it causes missed follow-ups and extra clicks read more.

Support

#customization:plugin

  • Topic Ratings Plugin got a practical compatibility win: Arkshine explained a merged PR that removes legacy widget references so the plugin works again, and confirmed updating the plugin should resolve the errors for affected sites read more.

  • In Telegram Notifications Plugin, scavin asked the key maintenance question—whether the plugin is still actively supported—flagging an evergreen concern for production admins weighing long-lived integrations read more.

Activity by the @team Group

  • sam focused on fixing RTL title-field directionality by explaining why HTML dir="auto" yields LTR when the input is empty, proposing a behavior change (default RTL until the first character, then switch to auto), and linking an implementation PR for review read more. sam also connected the fix to prior RTL UX reports so it lands as a comprehensive improvement rather than a one-off patch read more.

  • renato investigated a renewed report of the composer/editor “jumping” issue, noting the captured behavior appeared to be in the Markdown split-preview composer (not ProseMirror) and requesting reproduction confirmation across multiple Discourse instances to isolate scope and cause read more.

If today’s Meta had a theme, it’d be: highlight it, copy it, and make sure it doesn’t accidentally turn LTR while you weren’t looking.