On 19 December 2014 at 10:19, <[email protected]> wrote:
>
> hello Arthur,
>
> first, thanks alot for answring.
>
> sorry for the syntax error, i wrote it fast and didn't notice.
>
> let me clear my question.
>
> i've edited the jsbin
> http://jsbin.com/zuqojokamo/2/edit
>
> lets say we have another javascript file.
>
> and that getCardIndexedName calls app.getCardIndexedName with the card
> item and the index.
> app.getCardIndexedName returns a string.
>
> the thing is when i call app.getCardIndexedName the index is undefined for
> the first 2 times. (there are 4 calls for some reason)
>
> i think it happens because the index is not yet defined because the
> polymer isn't yet ready.
>
> but still the thing is that there are 4 calls(2 before polymer ready, and
> 2 after). my question is why? and how can i fix this issue.
>
> thanks again.
>

I believe the reason for doubling up is the first two are fired when the
element is created but the data hasn't propagated yet, and the second two
are fired when the data is identified as changed and applied to the
template.

(NOTE: I'm not a core polymer dev, just a watcher and sometime consumer,
and therefore my theory above may be invalid.)

-- 
Daniel Llewellyn
Bang Communications Limited
t: 01256 370 952

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/CABtuYwceOVAb8a5q6-XWHSeFut%2ByiHE%3DxOe1S405rnn1hNwr7w%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to