Firefox and cross-platform advice?

[Eric Eslinger]

Heya polymer-friends.

I'm in the process of doing cross-browser QA for our polymer app, and there's a lot of work to do. Some of this seems to be just may be plain "doesn't work yet". As an example, firefox with webcomponents on doesn't seem to work at all (but webcomponents is a flag anyway, so turn it off).

Are there any basic guidelines or top-ten-gotchas for getting this to work right? I think the key issue we're running into is getting styling selectors to work; there are a lot of places where the default paper/core styling is coming through (core-header-panels in blue again).

e

[Peng Kim]

i am facing the same problem,my site uses core/paper anywhere,but just worked fine on chrome,but on firefox, safari, and IE,some of them even not display,or data-binding not work well.

[Eric Eslinger]

A few things I definitely figured out:

The vulcanized form (where you just import paper-elements) is bad to do. I knew it was inefficient for production, but it seems like there are two bugs in 0.5.5 that cause problems. The first bug is that core-doc has a google font that is explicitly loaded over http, which is a bummer on https sites. The second bug is that core-tooltip (or maybe paper-tooltip) has an error in its vulcanized form which will crash polymer on startup on firefox (it is looking for Polymer.mixin2, which doesn't exist). That bug causes firefox to crash out of the polymer bootstrap process, leaving unstyled content (or nothing if you use unresolved) on the screen. I wasn't actually using these elements, so manually going through to find the elements I was using and importing them specifically solved a lot of problems.

The other problems were in how we were getting styling to apply in the shadow dom. There's definitely ways you can do selectors and classes that work in chrome and not in other browsers, so it was just a matter of going back to the docs and figuring out how to use ::shadow and stuff properly.

e

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/dd13f720-c7a8-4a73-98f4-960a6901eb2e%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

[Peng Kim]

I have no problem with compatibility ,my site www.moonmoonbird.com  has worked great with chrome,firefox,opera,safari,and IE11,except some small places need to be improved,and i am struggling with IE browser on window phone about animation and data-binding in styling,everything seems all good.i used many features as i can which provided by polymer,and i use vulcanize to compress my static files and reduce request as much as i can,before used vulcanize my home page has 95 requests ,after compressed,it reduce to only 3 requests.and my site is very fast and less bandwidth,so ,i don't consider it to be a problem which you meet!

[Peng Kim]

Here is what i do to vulcanize the elements,maybe it can help you:http://www.moonmoonbird.com/article/Polymer/how-to-vulcanize-elements-and-use-it-in-polymer

On Wednesday, April 22, 2015 at 11:59:38 PM UTC+8, Eric Eslinger wrote: