Better support for Tree Style Tab 4.0 and later #38
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
|
Looks like the dev hasn't been responsive. Any tips how to install from your fork, or is this something built into TST already now? |
|
Sadly this is not (and cannot) built into TST itself. You need to clone the branch https://github.com/piroor/tst-search/tree/support-tst-4 to your PC and build it with the |
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.
TST 4.0 and later is built on a virtual scrolling implementation and it generates HTML elements only near the viewport, so showing/hiding search results with a CSS hack is not effective anymore. Moreover, the virtual scrolling implementation expects all tab elements have same height, so the "shrink unmatched tabs" option breaks the result.
This PR introduces:
How about this change?