IQSS/11053 - Metadata Style fixes #11106
Open
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
What this PR does / why we need it: Simple CSS rules to address spacing issues noted in the two issues, along with a slight change to apply ORCID/ROR icon styling regardless of which field they are enabled on.
Which issue(s) this PR closes:
Special notes for your reviewer:
Suggestions on how to test this: Changes are currently live on demo as part of a custom stylesheet Should be able to see that with the changes the spacing issues in the two issues are gone and see that ORCID/ROR icons in other fields are aligned the same way as in the author field. (Currently I think ROR is configured on the Funder Agency field on demo.)
Does this PR introduce a user interface change? If mockups are available, please link/include them here:
Is there a release notes update needed for this change?:
Additional documentation: