Polymer killing an Angular directive?

111 views
Skip to first unread message

scotty...@gmail.com

unread,
Sep 11, 2014, 5:51:58 PM9/11/14
to polym...@googlegroups.com
http://plnkr.co/edit/4Up7rlCNja9CGVdVO9Bu?p=preview

If you remove the platform.js script, it renders correctly... Any thoughts on this?

scotty...@gmail.com

unread,
Sep 11, 2014, 5:52:47 PM9/11/14
to polym...@googlegroups.com, scotty...@gmail.com
BTW, works perfectly on Chrome, just not on Safari or Firefox...

Sébastien Cevey

unread,
Sep 12, 2014, 5:20:41 AM9/12/14
to scotty...@gmail.com, polym...@googlegroups.com
Hi,

I'm also having problems using platform.js (specifically the polyfills that power it in FF) and Angular. I've opened an issue to track this here: https://github.com/angular/angular.js/issues/8598

It may not be the exact same condition, but might be symptoms from the same root cause (use of a live NodeList which breaks due to polyfill)?

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 polymer-dev...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/96436016-780a-4c21-a843-03fd5c35b147%40googlegroups.com.

For more options, visit https://groups.google.com/d/optout.



--
Sébastien Cevey
Software Developer


Visit theguardian.com. On your mobile and tablet, download the Guardian iPhone and Android apps theguardian.com/guardianapp and our tablet editions theguardian.com/editions.  Save up to 57% by subscribing to the Guardian and Observer - choose the papers you want and get full digital access.  Visit subscribe.theguardian.com

This e-mail and all attachments are confidential and may also be privileged. If you are not the named recipient, please notify the sender and delete the e-mail and all attachments immediately. Do not disclose the contents to another person. You may not use the information for any purpose, or store, or copy, it in any way.  Guardian News & Media Limited is not liable for any computer viruses or other material transmitted with or as part of this e-mail. You should employ virus checking software.
 
Guardian News & Media Limited is a member of Guardian Media Group plc. Registered Office: PO Box 68164, Kings Place, 90 York Way, London, N1P 2AP.  Registered in England Number 908396


scotty...@gmail.com

unread,
Sep 12, 2014, 9:27:31 AM9/12/14
to polym...@googlegroups.com, scotty...@gmail.com
Thanks, Sébastien! Looks like a related issue. Unfortunately for my project, I might have to pull out of Polymer and reimplement without web components since this issue seems to have hit a wall. :(

Arthur Evans

unread,
Sep 12, 2014, 2:20:21 PM9/12/14
to scotty...@gmail.com, polymer-dev
Hi,

I tried your code on Firefox and I noticed that it appears to be using an old version of platform.js (0.3.4) from a CDN. When I replaced it with the latest version (0.4.0), it seems to work fine:


It doesn't look like you're actually using Polymer in here, and I'm not seeing the custom elements, either -- I didn't see a polymer-element or a call to document.registerElement. Is there some magic Angular API to create a custom element?

Thanks,
Arthur



scotty...@gmail.com

unread,
Sep 12, 2014, 5:03:42 PM9/12/14
to polym...@googlegroups.com, scotty...@gmail.com
Excellent! I realize that there were no polymer elements in that Plunker, I was just trying to demonstrate that simply including platform.js on the page broke that angular directive. :)

Unfortunately, that was my sad attempt to reproduce my problem with the fewest lines possible, but I'm using 0.4.0, so I know that's not the actual solution to my issue. I'll try to make a simple Plunker that reproduces my problem. Not easy since my app has a lot of moving parts (ui-router, loading templates from templateCache, etc.), so it'll take me some effort to figure out which part is the real culprit. Maybe it's instructive that the plunker in 0.3.4 acts precisely how my project is acting with 0.4.0...

Thanks again for the sleuthing, and I hope we can get to the real cause.
Reply all
Reply to author
Forward
0 new messages