Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

URI / language conflict in item metadata #2249

Open
allanaaa opened this issue Dec 12, 2024 · 9 comments
Open

URI / language conflict in item metadata #2249

allanaaa opened this issue Dec 12, 2024 · 9 comments

Comments

@allanaaa
Copy link

While testing #2248, I noticed that some value-content spans have an extra empty line of space on the bottom. This is actually a bit of margin-right that gets added when the value is a not-only-child.

I'm not clear on what this is intended to do (i.e. what could come after the value-content), but this will apply to a dereferenceable URI when a language tag is included at the top left. The bumping of this little margin onto a new line seems to be an unintended interaction when the URI dereferencer is on and it loads an empty "uri-dereferencer-container" container.

So, the top two values (Contributor and Spatial Coverage) have an extra line, where the multiple entries under Author do not.

Screenshot 2024-12-12 at 15 17 45

I think the only thing that loads after value-content is the annotations:

Screenshot 2024-12-12 at 15 36 51

So, the annotations end up on a new line when we usually want them inline with the value.

It's clear that not-only-child isn't the right selector for this.

This is probably related to #2038 and getting a definitive order & logic for all potential elements in the item metadata.

@kimisgold
Copy link
Member

Quick question, which browser were you using for these screenshots? I'm no seeing this spacing in Firefox, but I see it in Chrome. Does this line up with your what you're seeing?

@allanaaa
Copy link
Author

I'm seeing it in both Firefox and Chrome:

Screenshot 2024-12-17 at 14 03 24

http://dev.omeka.org/amayer/amayer-s/omeka-s/s/my-omeka-s-site/item/24030#lg=1&slide=0

@kimisgold
Copy link
Member

On my end, it looks like there's an empty container for URI dereferencer content that's taking up space. Once the URI dereferencer toggle is activated, that container is populated. When the toggle is used again to collapse the content, that container is hidden and the extra space goes away. On values that have annotations, the annotation toggle becomes inline after the URI dereferencer content appears at least once. If that's the case, it might be that URI dereferencer needs to adjust how it manages its content container visibility.

kimisgold added a commit to omeka-s-themes/cozy that referenced this issue Dec 18, 2024
This is intended to target metadata browse links, but 'only-child'
does not take language tags into consideration. See
omeka/omeka-s#2249
@kimisgold
Copy link
Member

I'm not clear on what this is intended to do (i.e. what could come after the value-content)

Metadata browse links ("See all items with this value").

I noticed that this seems to be a style specific to the cozy theme, so I've adjusted the css rule to only provide the right margin if the value content is the last child in its container. If you spot this in any other themes, let me know.

@allanaaa
Copy link
Author

allanaaa commented Jan 10, 2025

I'm not clear on what this is intended to do (i.e. what could come after the value-content)

Metadata browse links ("See all items with this value").

No, the MB browse links are inside the value-content span.

Screenshot 2025-01-10 at 12 52 58

I've just updated all my themes. This is in The Daily.

@allanaaa
Copy link
Author

Also, the thumbnail next to the linked resource "National Mall Items" is messing with the line height, so the MB browse link is off-kilter, in both Cozy and Daily:

Screenshot 2025-01-10 at 12 58 08 Screenshot 2025-01-10 at 12 58 42

@allanaaa
Copy link
Author

Both problems are also in Center Row:

Screenshot 2025-01-10 at 13 04 08

@allanaaa
Copy link
Author

Separate problem with the URI Dereferencer collapsed container in Freedom and Lively - they are displaying as empty boxes with borders rather than being hidden until the toggle is clicked.

Screenshot 2025-01-10 at 13 05 56 Screenshot 2025-01-10 at 13 06 15

I'm starting to think there is a module-based solution to all these problems, as you said above @kimisgold:

it might be that URI dereferencer needs to adjust how it manages its content container visibility.

If not, we can tag Nelson in to look at these two themes.

@kimisgold
Copy link
Member

I think I'm going to draft a solution in UriDereferencer. I'll open an issue there and tag this thread.

kimisgold added a commit to omeka-s-modules/UriDereferencer that referenced this issue Jan 13, 2025
* Manage dereferencer content visibility with css class instead of
  inline styles. (Addresses omeka/omeka-s#2249)
* Condense fetch and toggle into single button. It toggles the content
  and only fetches on the first click.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants