Reintroduce content-visibility: auto
#1737
Closed
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
djahandarie
added
kind/enhancement
|
Not sure why master screenshots were missing a popup for test9 but the results for this branch are correct |
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.
For the performance reasons stated in #1487 , reintroduce
content-visibility: autowhich provides massive benefits when the popup has a lot of content.But this time modify the hover image in compact glossary mode to open upwards instead of downwards to avoid it getting cutoff at the bottom when it exceeds the boundary of
.entry(becausecontent-visibility: autoprevents painting outside of the element bounds). This avoids the issue in #1705