Fix/css support #2177
Closed
Fix/css support #2177
Conversation
This file contains hidden or 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
…st window:resize), inspired by swimlane#1040
…inor performance optimization
…rendered when using virtual scroll)
…r appears if it was previously hidden) -fix: glitching column resizing when pushed to table edges -further fixed & improved column size calculation in 'force' mode
…eir original width
… its visibility -TableColumn.$$id renamed to id (can be assigned by user as well) -renamed resetOriginalColumnStates to resetColumnStates
- Feature: added default column reordering marker - Fix: reordering columns when some columns are hidden
…polyfill causes unneccessary change detections)
…nt to correctly detect also all vertical size changes
…n the body as well (scrollbars may appear)
-Bumped version to 20.0.3
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 participants
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 kind of change does this PR introduce? (check one with "x")
What is the current behavior? (You can also link to an open issue here)
What is the new behavior?
Does this PR introduce a breaking change? (check one with "x")
If this PR contains a breaking change, please describe the impact and migration path for existing applications: ...
Other information: