UVE: Clamp contentlet titles to two lines in the palette

[Copilot]

longer-text.mp4

Proposed Changes

• Replace single-line truncation in the Page Editor palette with a two-line clamp so more of each contentlet title is visible without allowing rows to grow indefinitely
• Keep the fixed row height, move the hover affordance to a PrimeNG tooltip on the clamped title text only, and update the focused component spec to cover the new title styling and tooltip behavior

Checklist

• Tests
• Translations
• Security Implications Contemplated (UI-only styling and spec updates; no new security impact)

Additional Info

This PR now uses a two-line truncated title instead of fully wrapping contentlet names. That keeps similarly prefixed items easier to distinguish while preserving the existing row layout.

The full title is now exposed through the PrimeNG tooltip directive on the clamped text itself rather than through the browser-default tooltip on the whole contentlet box.

Validated with:

• npx nx lint portlets-edit-ema-portlet
• npx nx test portlets-edit-ema-portlet

Screenshots

Original	Updated
** original screenshot **	** updated screenshot **

This PR fixes: #35876

[KevinDavilaDotCMS]

Can we add the same tooltip to the URL in uve iframe?
Now is only truncated

Not related to ticket, but are the same tailwind classes, so 2x1 😅

[claude]

Claude finished @fmontes's task in 1m 5s —— View job

---

Code Review

• Read changed files
• Analyze changes
• Post review

---

Two things worth flagging:

1. Tooltip fires unconditionally — noise for short titles

In dot-uve-palette-contentlet.component.html:23, [pTooltip]="contentlet.title" is bound unconditionally. If the title fits within two lines, hovering the text pops up a tooltip that just repeats what's already fully visible. This is a common pragmatic tradeoff, but it's technically incorrect — the tooltip should only appear when line-clamp is actually truncating. A signal-based isTruncated approach (comparing scrollHeight > clientHeight) would be more precise, but adds complexity. Worth a deliberate decision either way.

2. tooltipPosition="top" has no auto-flip fallback declared

For items near the top of the palette list, tooltipPosition="top" will try to render above the element, potentially off-screen. PrimeNG's tooltip directive does attempt auto-repositioning internally, but explicitly passing [tooltipOptions]="{ autoHide: false }" or a different default position (right or bottom) would be safer for top-of-list rows.

Otherwise clean. The removal of the host title attribute, scoping pTooltip to the title element only, and the line-clamp-2 wrap-break-word combination are all correct. The spec covers the key behaviors (class presence, tooltip directive binding, no native title on host).