UI spacing regression on ds-generic-item-page-field (extra spaces around metadata values) in v10.x

[eulereadgbe]

Describe the bug

In DSpace version 10.0 and 10.1, metadata fields rendered via ds-generic-item-page-field (specifically observed with dc.subject) display extra spaces before and after the values when comma-separated ([separator]="', '"). Even though no space is explicitly defined in the separator configuration, a gap or extra spacing appears in the rendered UI around the links.

Testing confirms this issue affects multiple entity types (reproduced on both untyped items and publication entities, including verification against the public DSpace test environment at sandbox.dspace.org).

To Reproduce

Steps to reproduce the behavior:

1. Configure an item page component (e.g., untyped-item.component.html or publication component) with a custom separator (e.g., changing the comma to a semicolon to verify the separator value is accepted, while checking spacing):
   <ds-generic-item-page-field [item]="object"
[fields]="['dc.subject']"
[separator]="';'"
[label]="'item.page.subject'">
</ds-generic-item-page-field>
2. View an item with multiple subjects on a DSpace instance (8x or 9x) (observe correct tight spacing).
3. View the same item configuration on a DSpace 10.0 or 10.1 instance (or via sandbox.dspace.org).
4. Check the UI: Notice that while the component respects the separator change (e.g., using the semicolon), unwanted spacing is still incorrectly injected around the metadata link elements before/after the separator.

Expected behavior

The separator should follow the text tightly based on the exact string provided in [separator], without unexpected padding, margins, or flex gaps injected around the metadata link elements, matching the behavior in DSpace 7–9.

Screenshots

DSpace 8.5 and 9.4

DSpace 10.0 and 10.1

Additional Context

Impact & Importance: While spacing may seem like a minor detail, repository administrators frequently work with strict client-mandated style guides and meticulous stakeholders ("pixel-perfect" requirements). Unwanted gaps breaking tight punctuation formatting create noticeable visual inconsistencies across item records.

Related work

Link to any related tickets or PRs here.

[lgeggleston]

Hi @eulereadgbe, thanks for submitting this ticket with details & context! Added to a project board for volunteer developer to pick up.

It's possible this small UX change may have been related to this fix to the keyword links in 10.0 - @guillermo-escire, would you be interested in taking a quick look into this by chance?