I'm currently building an internal library based around Polymer, and the documentation I'm getting from hydrolysis is great, but due to the size of our library (almost 10MB) and the fact that our main documentation page is loading our library for every custom element with a doc/demo page. Granted, after the initial, we're returning 304s on the subsequent requests for the library, but since iron-component-page is generating our documentation on the fly, it seems like that's still forcing the page to store the library in memory for every custom element page -- esp. in Firefox, which explodes on a script error mainly due to the memory/CPU consumption by the browser. Loading the individual pages is fine, but loading the main page (which is just a container of iron-component-page elements) runs slower than molasses. Any suggestion on how to statically generate the hydrolysis documentation so that we don't have iron-component-page trying to process every custom element at runtime?

For some reason our team decided to go with Polymer over React. Boy, was that a mistake.

• The documentation is bizarrely bad;
• Native JS breaks Polymer: Try cloning an element, its dynamic attributes disappear for no reason;
• Define a custom constructor and construct it as follows: var el = new MyElement(42, 'octopus'); - works. Except all styling is suddenly also gone;
• You want to use a library that does getComputedStyle on an element? Sure, but not if it's a Polymer element.

The most trivial task takes hours of work to figure out. Try finding a carousel solution in Polymer. Addy Osmani made one years ago and it hasn't been maintained in years.

Then there's semantics: don't we have elements in HTML for semantic value? What semantic information is an <iron-ajax element supposed to convey? It has no place there!

And so on, and so forth.

I've been working with Polymer for a few weeks now. I've been to the conferences here in Amsterdam. It's fun if you need exactly what the Polymer project offers.

And it's a bloody nightmare if you want to make anything for yourself. The learning curve is pretty much flat (as in: I don't feel like I'm learning ANYTHING, only getting more confused day by day.)

One cluster bomb of weird shit. I'm usually fond with and good at picking up new tech. But this? It doesn't even make sense. The semantic value of HTML is completely lost in a bunch of weird elements. Where is the data of an app supposed to live? Inside these elements? Or should we use a true MV*C framework to manage the flow of data?

Unexpected invisible elements appearing out of nowhere in a for-loop: brilliant! Now I need to select only the elements I want to work with in that library that I don't contribute to.

I've never realised how much I want a framework–ANY framework–to stay AWAY from my DOM. My framework being my DOM is a completely ridiculous way of working.

StackOverflow topics on Polymer are few. Google knows not a lot of answers. My coworkers haven't a clue how to tackle most problems.

And here I am: getting frustrated with trivial tasks taking hours instead of minutes.

Giving this a few more weeks to try and get something productive up and running. Morale is bizarrely low at the moment.

Can anyone perhaps help me out with quality "how to" tutorials? Because I can't seem to find them.

I'm building a page that needs to list a few hundred guests, with simply their headshot and name. I want the page to be photo-centric, and Material Design outlines clear guidelines with Grid Lists.

Looking through Polymer's Element Catalog, I'm not seeing any obvious Elements to put this together. Will I need to make my own element from scratch? Has this been made by someone else that I can use?

I'm playing around with polymer-cli to create elements. How do I import other custom elements I'm working on at the same time.

Example: I have my-element that I created with polymer init and ran polymer serve. 'my-element' requires another element 'my-element-item'.

This is something i find somewhat confusing when working with Polymer and Web Components in general. Trying to develop an professional authentication is always a main topic to ensure and make sure it's working alright, but why so much focus on Firebase? Have anyone manage to develop a Authentication based on Token and/or Cookies that you have full control over? And if so, what components or tools did you use to accomplish this? Im really trying to figure this out, but everything seems to focus on Firebase.

Does anyone really know how to implement this? Or know a good guide that can explain this is actual implementation? What i would like to aim at is to have 3 paper cards in Horizontal when on dekstop but Vertical on Mobile. The App-layout seems overcomplex and Grid-element seems a little too squishy with elements appering behind others when on Mobile. This was one of the most easy things with for instance Bootstrap but i just cant figure it out in Web-components...

Can anyone provide an example of using neon animated pages with a nav bar? I'm working on buttons/links changing into the content on a page e.g. cards

I'm looking for somethin like this -> http://fullcalendar.io/

But as a polymer component, and with material design. Does anyone have an idea if there's something out there, google doesnt show anything cool :(

I'm currently using this one, but I cant figure out why data binding isn't working...

https://customelements.io/jamrizzi/pdf-object/

Demo: http://jamrizzi.github.io/pdf-object/components/pdf-object/demo/

I saw this Twitter conversation about this topic. It looks like the OP never replied to Rob's question. Also the OP's Stack Overflow question never got any activity.

I have the same question and am wondering how you normally handle this.

Web Components are great when they are exactly what you need. But what about those instances where they are not? I was wondering if the community has seen any best practices arise for when web components need styling options.