Import components top down instead of bottom up #135
Merged
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.
Fix #134
See root cause of the issue and possible solutions in the issue #134
This PR:
As mentioned in issue #134 , a better (though more involved fix) will be to implement
table-stacked
as a reactive property that works regardless of the order of component definition, although I plan to do that as a followup since it will require a bit more time. This PR unblocks use of the table elements in production.Testing
demo.issue.134
demo/demo-page-defer.html
table-stacked
class is present on the table row incod-table-row
shadow DOM