Canary is now up to v41. It seems like they have some other fix in place, as it was it terrible shape post-revert, but now seems to be functioning pretty well. The only kink is that if you bring a game up in the browser while it's windowed, the vsync fails...until you resize the window. After resizing it, canary will sync very well, whether windowed or maximized.
Haven't tried 39 stable yet...I'm updating to it now.
Honestly, at this point I'm not that worried about chrome, though I'd hate to have to use a version of node-webkit based on v38. The real problem is Firefox. It's just abysmal, even on simple games. It jerks, halts, drops frames, and screen tears (sometimes horizontally, which is a new one on me). Project Silk appears to address this...but what's going on with it? I may be wrong, but it looks like Silk has been getting less and less attention over the last couple months.
Firefox never quite matched chrome's performance, but I don't know how it got this bad, and I don't know why this isn't higher on their todo list...you can see all these things on webpages as much as with gaming. I'm going to dl the developer and nightly versions tonight and see if there are any improvements in the pipeline for this (though looking at the feature lists, my hopes aren't very high).