-
Notifications
You must be signed in to change notification settings - Fork 2k
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
<content> not being displayed if too deep. #283
Comments
https://github.com/Polymer/ShadowDOM/issues/259 |
Duplicate of Polymer/ShadowDOM/issues/259 |
@peterwmwong The link to the issue is private. I am getting a 404. I have been told it's been fixed, can you share a link to the fix please? |
@yattias no idea man, its been 2 years and they rewrote Polymer since I commented on this issue. |
Yeah, I have no idea what the current status is too. |
This is long fixed. The shadow DOM bug isn't private; the link is broken because the polyfills were combined into to a single repo and moved to https://github.com/webcomponents/webcomponentsjs. I took a look at the list of closed issues that mentioned "content" and nothing's leaping out at me. AFAIKT, the original jsfiddle listed above now works fine. And here's a version of the original bug repro in modern polymer, which also doesn't show the described symptoms: http://jsbin.com/dupine/edit?html,console,output So, short answer—bug fixed in 2013. If you're seeing something that you think is the same problem, it probably isn't. |
Is there a limitation to how
<content>
is inserted into a polymer element's<template>
?If I put the
<content>
in something like<div><span><content></content></span></div>
it doesn't show.Here is a jsfiddle demonstrating the problem: http://jsfiddle.net/dannyfritz/vqCFw/6/
I'm on Chrome 29.
The text was updated successfully, but these errors were encountered: