Kevin Schaaf

Suggested text: Note: One exception is made for binding to built-in case-sensitive attributes like ``'s `viewBox` attribute. For built-in case-sensitive attributes, bindings should not include the `$` normally required for...

@arthurevans Correct, the first doc is indeed correct, describing what Polymer 2.0 supports and is framed correctly from my reading. @renfeng This is the key from the readme: > For...

Status: This has been fixed in the `lit-next` branch, but is still an open bug on `master` (lit-element 2.x).

This was fixed in https://github.com/lit/lit-element/pull/1171, but that change failed to add `decorators.js` to `package.json`'s `files`, so it was not published in 2.5.1.

Now that we have [development build runtime warnings](https://lit.dev/docs/tools/development/#development-build-runtime-warnings), we should ensure errors thrown out of e.g. attribute parsing have good warnings.

Some trusted types types show up in the lit-html public interface, and thus need to be dependencies, not dev dependencies. Closing as WAI.

@justinfagnani This is the bug I mentioned yesterday, added to your sprint. The solution is hopefully as simple as flipping the `addController()` and `attachListeners()` lines. > What's the use case...

> make ContextProvider able to listen for a dynamic set of multiple context keys @justinfagnani We should explore that, but I think we should also just fix this, since it's...

@usergenic Can you determine a priority and change status to Triaged?

So it sounds like the problem isn't actually that lit-ssr is depending on commonjs modules, it's that we're depending on built-in node modules? We don't do this much fwict, other...