Skip to content

Conversation

@stevenferey
Copy link
Contributor

Which issue(s) this PR closes:

Copy link
Member

@qqmyers qqmyers left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This looks fine. I can confirm it works on the provided example (which only overflows when I narrow the window enough.)
FWIW: It looks like word-break:normal;overflow-wrap:anywhere is a newer/better alternative to the word-break:break-all we use in other places.

I also noted that table.metadata applies both to the metadata pane and to the ubove-the-fold summary area - we probably do want both.

Adding to Ready for Triage - assuming it's accepted, it can go directly to Ready for QA (post v6.8).

@qqmyers qqmyers moved this to Ready for Triage in IQSS Dataverse Project Sep 17, 2025
@qqmyers qqmyers added the Size: 0.5 A percentage of a sprint. 0.35 hours label Sep 17, 2025
@ofahimIQSS ofahimIQSS moved this from Ready for Triage to Ready for Review ⏩ in IQSS Dataverse Project Sep 23, 2025
@ofahimIQSS ofahimIQSS moved this from Ready for Review ⏩ to Reviewed but Frozen ❄️ in IQSS Dataverse Project Sep 23, 2025
@cmbz cmbz added FY26 Sprint 6 FY26 Sprint 6 (2025-09-10 - 2025-09-24) FY26 Sprint 7 FY26 Sprint 7 (2025-09-24 - 2025-10-08) labels Sep 24, 2025
@pdurbin pdurbin moved this from Reviewed but behind develop ⬅️ to Ready for QA ⏩ in IQSS Dataverse Project Sep 26, 2025
@cmbz cmbz added the FY26 Sprint 8 FY26 Sprint 8 (2025-10-08 - 2025-10-22) label Oct 8, 2025
@ofahimIQSS ofahimIQSS self-assigned this Oct 9, 2025
@ofahimIQSS ofahimIQSS moved this from Ready for QA ⏩ to QA ✅ in IQSS Dataverse Project Oct 9, 2025
@ofahimIQSS
Copy link
Contributor

I'm still seeing the issue
internal:
image
image

local:
image
image

@qqmyers
Copy link
Member

qqmyers commented Oct 9, 2025

The issue was only about the layout in the metadata table, which I think is fixed in the example dataset in the images.

That said, does it make sense to move the css statements in the PR up to

so they affect the default for all fields. From a quick test, I think resolves all of these issues at once/ may be a better approach than just adding them to specific elements as we've been doing. @stevenferey - do you want to adjust your PR to do that?

@ofahimIQSS
Copy link
Contributor

I like this approach

@ofahimIQSS ofahimIQSS assigned ofahimIQSS and unassigned ofahimIQSS Oct 14, 2025
@ofahimIQSS
Copy link
Contributor

thanks, looks good from my end - merging

@ofahimIQSS ofahimIQSS merged commit 94fa2fb into IQSS:develop Oct 14, 2025
7 checks passed
@github-project-automation github-project-automation bot moved this from QA ✅ to Merged 🚀 in IQSS Dataverse Project Oct 14, 2025
@ofahimIQSS ofahimIQSS removed their assignment Oct 14, 2025
@jeromeroucou jeromeroucou deleted the 11824-long-metadata-values-break-the-table-layout branch October 15, 2025 08:01
@pdurbin pdurbin added this to the 6.9 milestone Oct 15, 2025
@scolapasta scolapasta moved this from Merged 🚀 to Done 🧹 in IQSS Dataverse Project Oct 15, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

FY26 Sprint 6 FY26 Sprint 6 (2025-09-10 - 2025-09-24) FY26 Sprint 7 FY26 Sprint 7 (2025-09-24 - 2025-10-08) FY26 Sprint 8 FY26 Sprint 8 (2025-10-08 - 2025-10-22) Size: 0.5 A percentage of a sprint. 0.35 hours

Projects

Status: Done 🧹

Development

Successfully merging this pull request may close these issues.

Very long metadata values break the table layout

5 participants