Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Keep the order of scoped and scopeless nodes in polyfilled browsers. #44

Merged
merged 1 commit into from
Jan 3, 2018

Conversation

tomalec
Copy link
Member

@tomalec tomalec commented Jan 3, 2018

Problem: Scopeless nodes - like declarative-shadow-dom with default slot for merged partial view - were stamped before, scoped nodes - like declarative-shadow-dom with default compositions for apps.
That was resulting in non-slotted elements to appear on top instead of bottom (as in browsers with native HTML Imports)

Related:
https://github.com/Starcounter/KitchenSink/issues/219
Starcounter/starcounter-include#69

@tomalec tomalec added the bug label Jan 3, 2018
Problem: Scopeless nodes - like declarative-shadow-dom with default slot for merged partial view - were stamped before, scoped nodes - like declarative-shadow-dom with default compositions for apps.
That was resulting in non-slotted elements to appear on top instead of bottom (as in browsers with native HTML Imports)

Related:
https://github.com/Starcounter/KitchenSink/issues/219
Starcounter/starcounter-include#69
@tomalec tomalec force-pushed the keep-scoped-and-scopeless-order branch from 01e6192 to 101e0f6 Compare January 3, 2018 17:32
Copy link
Contributor

@warpech warpech left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Lgtm.

If anyone wonders what's happening here. The previous code was concating two nodeLists, which affected the order. The current code filters a single nodeList, preserving the order.

@tomalec tomalec merged commit a2ee9ea into master Jan 3, 2018
@warpech
Copy link
Contributor

warpech commented Jan 9, 2018

Setting as “Finished” because it is:

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants