Site content doesn't load in Chrome 33.0.1736.2 dev

[delfuego]

When trying to view the Chromium Dashboard in 33.0.1736.2 dev on OS X (10.9.1), I get the site's frame (header, "Web Platform Features (157)", etc., but the central content box never changes from "loading..."

In the console, I get the following emitted by polymer-element.js:

Uncaught TypeError: Object #<g> has no method 'registerWhenReady'

I do see the XHR request for the features, which loads successfully — so this appears to be an issue with rendering the features in that central box.

Of note, and unrelated, I also get the following error showing that one font you're loading won't load because of a CORS denial:

XMLHttpRequest cannot load http://fonts.googleapis.com/css?family=Open+Sans:300,300italic,600,800|Source+Code+Pro:400,600. No 'Access-Control-Allow-Origin' header is present on the requested resource. Origin 'http://www.chromestatus.com' is therefore not allowed access.

[delfuego]

Of note, loading in Firefox 24 ESR works fine — this appears to be limited to Chrome 33.0.1736.2 dev for me.

[ebidel]

Do you have the "Enable web platform features" flag on in about:flags? This can happen on older versions
of Polymer where that flag is not enabled, native Shadow DOM is not available but native custom elements is.

I've just pushed an update that rev's polymer. Can you try it again.

[delfuego]

I do NOT have that flag on — should I?

I also am not seeing the site as fixed; will it take a bit for the change to be reflected on the public site? (I even tried in an incognito window to make sure it wasn't a cache thing, although I guess there could be an intermediate cache I'm hitting...)

[ebidel]

Hmmm. Then we didn't fix the issue in the last Polymer release like I thought. If you turn that flag on, this error will go away.

[delfuego]

OK -- but I guess I wonder whether I should be turning on an experimental flag in order to view this one site, vs. just using another browser. I generally fall into the camp of not wanting to turn flags on that I'll forget about unless it's critically important to something I need to do...

Thanks for the info, though!

[ebidel]

The upstream issue is here: Polymer/polymer#360

Marking this as WontFix.

[ebidel]

Tracked this done. Should be fixed now. Give http://www.chromestatus.com/features a try without the flag.

[delfuego]

Perfect now!