Has anyone run into these same issues with async calls on Firefox?  Am I in 
fact using async correctly in the example shown on SO?

Kelly  

On Tuesday, 9 December 2014 11:25:46 UTC-8, Kelly St. John wrote:
>
> pps:  I have updated the stack overflow description to reflect that the 
> function is in fact being called, just not asynchronously in Firefox as one 
> would expect (and as it is handled in Chrome).
>
>
> On Tuesday, 9 December 2014 11:23:08 UTC-8, Kelly St. John wrote:
>>
>> ps:  To add further clarity, 'this.bugs' and 'this.snakes' are variables 
>> bound to exposed attributes of the snakesDS and bugsDS (i.e. custom polymer 
>> datasource elements).  The datasource elements are returning those values 
>> appropriately following processing the expected responses from core-ajax, 
>> the problem here is the timing of the call to 'populateLocalStorage' 
>> function in Firefox.
>>  
>>
>> On Tuesday, 9 December 2014 11:14:12 UTC-8, Kelly St. John wrote:
>>>
>>> Hello Ian.  The javascript namespace is defined only as a best practice 
>>> to manage local storage variables in an encapsulated fashion.  It is 
>>> defined in an external js file loaded by index.html.  I've done some 
>>> further testing and it appears 'populateLocalStorage' is in fact being 
>>> called, but not asynchronously in FireFox.  It is being called before the 
>>> datasource elements have received their ajax responses and handled them 
>>> accordingly.  I'll restate that this is working as is in Chrome, but not in 
>>> Firefox version 33.1.1 or 34.0.5.
>>>
>>> Cheers
>>> Kelly
>>>
>>> On Tuesday, 9 December 2014 10:59:46 UTC-8, Ian MacLeod wrote:
>>>>
>>>> Hmm, the current behavior for async (without a timeout) is to just 
>>>> call requestAnimationFrame 
>>>> <https://github.com/Polymer/polymer/blob/master/src/instance/utils.js#L40-41>.
>>>>  
>>>> Should be getting called
>>>>
>>>> However, in your stack overflow post, where are you defining the 
>>>> namespace variable?
>>>>
>>>> On Mon Dec 08 2014 at 2:58:50 PM Kelly St. John <[email protected]> wrote:
>>>>
>>>>> Has anyone been running into problems using polymer's `async` in 
>>>>> FireFox?
>>>>>
>>>>> I've posted the issue I'm running into on Stack Overflow for your 
>>>>> reference:  
>>>>> http://stackoverflow.com/questions/27368519/polymer-async-not-working-in-firefox
>>>>>
>>>>>
>>>>>  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/96aa4fb0-acb2-464d-959c-08bd017ee5d8%40googlegroups.com
>>>>>  
>>>>> <https://groups.google.com/d/msgid/polymer-dev/96aa4fb0-acb2-464d-959c-08bd017ee5d8%40googlegroups.com?utm_medium=email&utm_source=footer>
>>>>> .
>>>>> For more options, visit https://groups.google.com/d/optout.
>>>>>
>>>>

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/fbf5f1de-53c5-441f-9177-c078f424228b%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to