Moved to 
stackoverflow: 
http://stackoverflow.com/questions/22855083/accessing-an-attribute-on-a-child-thats-set-with-a-data-binding

On Thursday, April 3, 2014 11:21:29 PM UTC-7, Rob Dodson wrote:
>
> I have a little bit of markup that looks like this:
>
> <polymer-element name="blog-post" noscript>
>       <template>
>         
>         <mark-down>
>           <textarea value="{{post}}"></textarea>
>         </mark-down>
>
>         <polymer-localstorage name="my-blog-editor" value="{{post}}">
>         </polymer-localstorage>
>       </template>
> </polymer-element>
>
> I'd like the mark-down tag to be able to see the value of the textarea but 
> I'm having a hard time knowing when to query for it.
>
> Inside of mark-down my code looks something like this:
>
>       attached: function() {
>           this.textarea = this.$.textareaContent.getDistributedNodes()[0]; 
>  // this grabs the textarea element
>
>           // create an observer instance
>           var observer = new MutationObserver(function(mutations) {
>             mutations.forEach(function(mutation) {
>               console.log(mutation);
>             });
>           });
>            
>           // pass in the target node, as well as the observer options
>           observer.observe(this.textarea, { attributes: true });
>       }
>
> Unfortunately the mutation observer never fires. I've tried checking for 
> the value of textarea directly in attached and domReady but it's always 
> null. The only success I've had is to use a setTimeout to check for the 
> value asynchronously.
>

Follow Polymer on Google+: plus.google.com/107187849809354688692
--- 
You received this message because you are subscribed to the Google Groups 
"Polymer" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
To view this discussion on the web visit 
https://groups.google.com/d/msgid/polymer-dev/6d343f4a-b8fd-43df-8c18-d62072bcbc34%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to