Eric Bidelman

I believe the goal was to get quic + h2 push working this quarter, but now update (yet) on the GAE side of things.

@ciampo you don't need this module to do h2 push on GAE. That's a feature that the core service supports. Just construct the link preload header. All this module does...

> Google Cloud team to implement server push fully It should be everywhere on Google's infrastructure. What service are you using that you're not seeing pushed results?

Ah yes, that's https://github.com/GoogleChrome/http2push-gae/issues/20#issuecomment-227648157. It's supposed to be fixed this quarter :\ I believe https://bugs.chromium.org/p/chromium/issues/detail?id=622043 is the issue to follow. FWIW, I'm seeing "h2" request on that demo page, not...

It's possible Chrome is still running experiments for different users. You can change the behavior in `about:flags` to enable/disable it. Mine is set to "default" in stable.

Take a look at `chrome://net-internals/#http2` to very what push promises are being recv'd and accepted.

What do you see on https://shop.polymer-project.org/? I see `h2` requests. @paulirish might know from the Devtools side.

The chrome error LG.

Agreed, the docs for these elements could definitely be better but there are a couple of things wrong with your bin: - you have a dom-module and import defined outside...

Is this https://github.com/GoogleWebComponents/firebase-element/pull/115?