Justin Fagnani

This is true, the live site is very old now, but I've been resisting taking it down so that people still have access to their old projects. Maybe it's not...

@aomarks that's right. cc @usergenic

Unfortunately we're not supporting the version of designer that's hosted anymore. All of our work is being done on a new version ("Designer 2"). The old version is kept up...

@katejeffreys I'll try to add some detail here... > Type: constructor (one of Boolean, Date, Number, String, Array or Object) is a little misleading. Those are they types which Polymer...

I think it's a pretty general request: given an app with a front-end written in Polymer and a specific app server, how do we perform tests of user workflows, presumably...

Oops, good catch. I wonder if it's worth adding `lit-element/decorators.js` to a 2.5.2 release at this point.

This issue isn't about what we think the API should look like, only about making our feature detection more robust in case it changes in a backward-incompatible way.

Closing for the related lit/lit issue (which we may re-open): https://github.com/lit/lit/issues/1977

`updated()` runs after an update, so any change of a reactive property or call to `requestUpdate()` will necessarily enqueue another asynchronous update. If you want to compute values _before_ an...

@hadriann lit-virtualizer mostly _is_ that for LitElement. We've decided to factor things to keep the core as small as possible w/ no keyed repeat at all. Then add keyed repeat...