Fix UI on RDF import page for Google Chrome browsers for GraphDB 9 #1268
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
|
Can one of the admins verify this patch? |
ww-jermaine
force-pushed
the
fix-ui-chrome-v1.11.1
branch
from
8b70825 to
5644ae7
Compare
ww-jermaine
force-pushed
the
fix-ui-chrome-v1.11.1
branch
from
5644ae7 to
5a4fdfd
Compare
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
When I navigate to the RDF import section of the GraphDB interface, the styling does not appear as expected. It seems that the CSS is broken, which impacts the usability of the page. This happens when using Chrome browser and the GraphDB version is 9.
Why
The styling might be messing up the layout.
How
I added a fix adjusting the sizes and spacing of each buttons.