HTMLImports fails silently on Chrome 28.0.1500.95 (Debian , 64bit)

[kaosat-dev]

None of demos/ examples work, and neither do some of my experiments hosted locally : they all fail silently without any errors in the dev console.

I added some console.log debug messages to the "ready" callback , that don't get displayed either. (works fine on Firefox-Aurora).

Perhaps a hint? Even with "Show Shadow DOM" enabled, the custom elements are "empty" so to say.

[cfsghost]

It doesn't work on my environment(Debian Sid, 32-bit) as well. Chrome and Firefox both have the same HTMLImports problem.

[dfreedm]

By "hosted locally", do you mean that you're loading the html pages with "file://" urls?

[kaosat-dev]

@azakus , no, I am using a simple web server , trying python's simplehttpServer and a Node Js one: http-server (https://github.com/nodeapps/http-server). Same result, sadly!

Edit: perhaps this might help as well :
If I enable logging of XMLHttpRequests , I can see all elements being loaded successfully, but no element is instantiated.

[dfreedm]

Can you give me a bit more information to try and reproduce? Top level directory that is being served and example directory structure would be great :)

[kaosat-dev]

@azakus yeah, these "no error " bugs are tricky :) But no problem, give me a few minutes please, I'll push a simple example structure to github:)

[sjmiles]

"Page is blank" bugs are the worst!

[kaosat-dev]

@sjmiles indeed: )

Ok , here is the repo : https://github.com/kaosat-dev/polymer-bugs
(barebones, just the "visitor-creds" example from the official site + polymer.min)

[dfreedm]

Seems to work for me.

Here's my setup

• Root folder: inside polymer-bugs
• python -m SimpleHTTPServer and localhost:8000
• node node_modules/http-server/bin/http-server and localhost:8080
• Chrome 28.0.1500.95 on Mac OS X 10.8.4

Both load "Hello my name is Scott2 Show:" with an abs-pos checkbox.

I don't think there's anything that would resolve differently w.r.t case sensitivity (the only big difference I can think of with using a Mac).

[kaosat-dev]

Hmm yeah case sensitivity should not be an issue, and wow this is really strange, just tried it on another machine (also Debian Stable, 64bit) with chrome 28.0.1500.52 and it works fine!
Just trying to find what is different about the system where I am running into the problem: normally the "Enable Experimental JavaScript" and "Enable experimental WebKit features" flags should not cause issues with Polymer , right ? (Those are the only two enabled flags)

[dfreedm]

Well, Polymer does use a lot of the features enabled by those flags. However, nothing you've included in that test case strikes me as something that would be affected by the existence of Object.observe or WeakMap...

Thanks for noting the use of those flags!

[kaosat-dev]

Bingo !
It is reproducible: it is indeed "caused" by the "Enable experimental WebKit features" flag !

[dfreedm]

Funky. I'm trying to remember what was even behind that flag in 28. Anyway, now that you've found the culprit, I'll close this bug. Thanks for the simple test case!

[kaosat-dev]

Thank you @azakus !
Hope I did not waste too much of your time on this one :)