Fixed outputTimeTable and outputTimeTableTotals markup #51
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
The `<div>` element is not closed correctly right now. This causes the browser to do a bit of error-correction. The error-correction process itself is a bit buggy, and in this case it creates a hierarchy of tables instead of putting tables side-by-side. That causes performance issues when large amount of data is loaded. This change should fix: Jorriss#34
Contributor
|
This is awesome, thanks! Hope Richie finds some time to merge these outstanding pull requests, I've had a few waiting for months... |
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.
The
<div>element is not closed correctly right now. This causes the browser to do a bit of error-correction. The error-correction process itself is a bit buggy, and in this case it creates a hierarchy of tables instead of putting tables side-by-side. That causes performance issues when large amount of data is loaded.This change should fix: #34