Skip to content

Styling bug after navigation (padding + border element) #110

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

Closed
matt4446 opened this issue Mar 14, 2016 · 1 comment
Closed

Styling bug after navigation (padding + border element) #110

matt4446 opened this issue Mar 14, 2016 · 1 comment
Assignees

Comments

@matt4446
Copy link

@vakrilov

So it seems to only apply to the <Border> element, which I believe is/has become obsolete now (I'll be removing the border element anyway) so it is not so much of a big deal.

As previously mentioned in the routing and navigation issue #18 ...

But more specifically the issue appears to be with the border element (and only as part of an additional component from the page component). When the page loads the padding from a CSS file it is not applied, but after navigation the padding is applied (see the two images below):

Ignore the action bar - I started adding my own.

before-nav_20160314015641
after-nav

I've added the same view component for both the start & test page so the collection of elements should be identical. After navigation, one would expect equal states of the components. The padding

I've branched my project here

The inconsistent component
Changing Border -> StackPanel loads the padding correctly.

I expected part of the template to act in the same way as the component above, but it didn't, which leads to a conclusion that it only does this when it is part of a component.

This effect (not loading the CSS) isn't appearing anywhere else in my pages / components I don't think.

@vakrilov vakrilov self-assigned this Mar 18, 2016
@vakrilov
Copy link
Contributor

Thanks for the sample and the explanations.
Indeed, I managed to reproduce it. However, as you said, only with the Border element. It is possible that this is a bug in the Border element layout logic, but since it is obsoleted it is not worth investigating it further.
I'm closing the issue for now - if it reappears again with other element we will reopen and investigate.

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

No branches or pull requests

2 participants