Thoght I'd be brave an update without waiting for any feedback ...

2 updates in a day - where's the harm ?

Well for me (and anyone else) using Chrome Gestures it no longer works ...

Guess that'll teach me to stick to my instincts in future !!

Oh yeah and Sticky Notes was screwed as well !!

Also toon theme, AdSweep still working i think but as you said gestures dont

They apparently removed the contentWindow object. And trying to use an undefined variable in anyway throws an error, rather than just treating as being "undefined".
That's one hell of a screw-up. :/

Lets hope they put it right quickly otherwise I'ii be on 195.4 for a while ;-)

I think this release is cool, as soon as I figure out how "moles" work!

@Waha

Is there anything that can be done to get CG to work with the latest versions of Chrome Dev or have we got to wait for them to fix this issue if we want to use CG ?

@Steve

There is a fixed version on the code site, download the latest ChromeGestures.user.js file to resolve the problem, be warned that tabs open in a new window, not tab and are blocked by default by the popup blocker.

When one of us are less busy we'll get around to updating CG with Chrome API and stuff.
But yeah, Aaron said they took out contentWindow as a security thing, luckily CG didn't really need it.
However I have to update all the rest of my extensions now. x.x;

@Kryptyx

Wouldn't have had a problem with the Tab in a new Window, after all could always 'drag' it the the open session ...

Bit concerned about it being blocked, does this mean you've got to unblock it before it opens ...

Originally Posted by StevePaul

@Kryptyx

Wouldn't have had a problem with the Tab in a new Window, after all could always 'drag' it the the open session ...

Bit concerned about it being blocked, does this mean you've got to unblock it before it opens ...

Currently yes. This will of course be fixed after we start using the Chrome API in a background page.