Unable to use the Sandbox on Chrome <= 28

[fcduarte]

The Sandbox project is not working on Chrome Beta (version 27.0.1453.81 beta) .. I wasn't able to execute any operation (drag components, view/edit code) and the console shows no errors.

[dfreedm]

Probably the result of this bug that I filed on the spec: https://www.w3.org/Bugs/Public/show_bug.cgi?id=21404
There was a brief period where the event order was incorrect in Chrome. I'm sad that made it to beta channel :(.

[dfreedm]

Filed a bug on Chrome to merge in the correct event path for Shadow DOM: https://code.google.com/p/chromium/issues/detail?id=241859

[dfreedm]

This was marked as WontFix in Chrome, and is working in 28.

[aeosynth]

The sandbox tab crashes for me on Chrome 28 stable, OSX 10.7.5, polymer-all stable [20130711].

edit: many examples crash my tab, not just the sandbox

[totrash]

Same situation as for "aeosynth" Chromium Version 28.0.1500.71 (209842). Sandbox crash and many examples too.....

[dfreedm]

@aeosynth @totrash Do either of you have "Enable Experimantal WebKit Features" or "Enable Experimental Javascript features" flags turned on in Chrome stable? If so, I suggest turning those off.

[totrash]

I have both flags disabled (With "Enable Experimental JavaScript" it doesn`t work at all I have some js errors)

The problems occur after "some" time and this time is not static sometimes after few seconds.
The longest time I spend in Sandbox was about 1 minute.

There is no any js errors only tab crash ....
It doesn`t crash on firefox for example .....

I could attach some debug logs, only tell me how to do it .......

[dfreedm]

@totrash Can you update to polymer-all 20130808 and try?

[aeosynth]

Neither flag enabled, crashes with 20130808, crashes with today's stable commit (Polymer/polymer-all@4a9813fc6a602ec7fa2f082371bc2f1950413095).

[dfreedm]

Are there any crash ids you can give me? chrome://crashes.

[aeosynth]

Crash ID da4248f3cd5e7aa7

Occurred Monday, August 12, 2013 3:02:51 PM

[dfreedm]

Aw man, this chrome bug finally reared its ugly head: https://code.google.com/p/chromium/issues/detail?id=240082

Basically, events through ShadowDOM are slightly busted in Chrome 28. Looks like we'll have to force shadowdom polyfill in Chrome <= 28.

[dfreedm]

Until Chrome 29 is stable, you can run with the shadow flag.

http://path/to/Sandbox/?shadow or <script src="polymer.js" shadow>

[totrash]

Working well with shadow flag. Thanks

[Splaktar]

Yes, thank you. It was crashing on me constantly, but the shadow flag allowed me to do quite a lot of interesting things with it and not get any crashes on Chromium 28.

[dfreedm]

Closing because Chrome Apps Sandbox mode is deprecated. Instead, the regular build + vulcanizer should allow for use in the CSP environment.