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

Size of metadata field does not adjust to content #3882

Closed
andre-hohmann opened this issue Jul 31, 2020 · 3 comments
Closed

Size of metadata field does not adjust to content #3882

andre-hohmann opened this issue Jul 31, 2020 · 3 comments

Comments

@andre-hohmann
Copy link
Collaborator

Problem

If a metadata field contains a long content, it is adjusted in the height to the content.
If the metadata area is expanded, the height remains, although only one line is needed.
This leads to more scrolling, ...

Solution

The metadata field should be adjusted to the content - also the height.

Examples

metadatafield01

metadatafield02

@matthias-ronge
Copy link
Collaborator

The distinction, whether it is a one-line text field or a multi-line text field, can be set in the ruleset with the <setting multiline="false"/> or <setting multiline="true"/>. In the generated HTML, these are two different elements, <input type="text"> or <textarea>. A dynamic height adjustment only makes sense for the second, but there should also be a larger height from the start so that you can visually distinguish which type of input field it is. Please note that this produces very long fields for very long text content (e.g. abstracts). Is it wanted like that?

@andre-hohmann
Copy link
Collaborator Author

I do not want to change the type of the field - it is absolutely fine as it is. I just wander, if the height of the field could be adjusted to the content of the field.

If, for example, the area of the metadata is widened before the metadata field with much text is shown, the field is adjusted to the content of the field.
If this adjustment is not possible, there should be no other changes and this issue can be closed.

metadatafield01

@andre-hohmann
Copy link
Collaborator Author

The problem can be solved, when the current structure element (here: Heft/Ausgabe) is selected again.
The issue will be closed.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants