Tomasz Pluskiewicz

Hi @nicholsn. Thank you for your interest in my work and kind words. The playground is exactly what it is, an app itself, and not the simplest possible so that...

Yes, apparently it is a limitation of the webcomponents.dev page itself. It does some magic to get up and running and the only way to run an example as-is is...

Superseded by #301

Hi @saumier. Thank you for your generous offer. I would be very much interested! In the past I attempted live demos but it had trouble bundling. Maybe it's better now....

@saumier I refined my wcd sandbox today and added a Getting Started page: https://forms.hypermedia.app/#/getting-started I will work on more advanced scenarios soon but hopefully you have something tangible to work...

Another way is to exclude load page elements lazily with `this.importHref` or [`lazy-imports`](https://github.com/Polymer/lazy-imports)

I just found the same problem. Did you find any workaround @phani1kumar?

Okay, here's what you can do for the time being. Whenever the value of `_calculatePageVisibility(user)` changes you have to make two calls on your `iron-pages`: 1. `_updateItems()` to discover items...

Setting the value is easy. What I wanted more is actually showcasing the values. See the screenshot in my PR. I added an additional `marked-element` which renders the dom-bind's model.

Having bumped into such a mismatch a few times already, I think I would appreciate a fallback which does indeed replace the server-side DOM when it occurs. Obviously, that should...