-
Notifications
You must be signed in to change notification settings - Fork 62
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
paper-checkbox fails to render properly in Ember #151
Comments
All works perfectly: Because of shadow DOM nature, you have to put everything you need into a Polymer component and initialize it: |
Close issue, @robdodson |
But, paper-checkbox and paper-radio-button is already a Polymer component. Why can't I use it as is? paper-button and paper-input works fine if used directly. This still looks like an issue, in that case. |
But, Im glad this workaround works. |
Updated above example with two more wrapper components for May be this is related to below issue: |
Is this issue and #3706 just waiting for Polymer 2.0? Is going to fix this? |
Description
paper-checkbox and paper-radio-button fails to render properly when transitioning between routes (navigate between 'index' and 'about' routes). Initially the components render fine, but after transitioning to another route and coming back, the components are broken. Here's the working example where you can see the issue.
http://codepen.io/jaichandra/pen/jrOpab?editors=1010
I am raising this issue here because paper-button and paper-input are working fine. Also, if I switch to Shadow DOM, the components work.
If you look at the rendered paper-checkbox dom, it get re-rendered inside one of its own nodes (after route transition), causing it to render two checkboxes and break. Same is the case with paper-radio-button.
Expected outcome
paper-checkbox should render correctly
Actual outcome
paper-checkbox ui breaks after transitioning between 'index' and 'about' routes
Live Demo
http://codepen.io/jaichandra/pen/jrOpab?editors=1010
Steps to reproduce
In the above example,
Browsers Affected
The text was updated successfully, but these errors were encountered: