silly question about jittering Chromium

If Google knows about this issue, then when it will be fixed?

2015?

2016?

beyond? <img src="{SMILIES_PATH}/icon_e_smile.gif" alt=":)" title="Smile">

p.s. I have found this:

http://blog.chromium.org/2012/11/build- ... hrome.html

and Chromium team e-mail:

chrome.cordova@gmail.com

This is a very hot topic in other posts, and has been for a long time.

We are talking about Google here... They break something and then fix it when, they, are ready (or at least we hope they will). Hopefully the fix will come early 2015.

The question is: How long till they break it again, and how long till they fix it again.... and again....and again....

szymek that Timeline feature looks interesting. Anyone who knows more than me know if that would be useful in diagnosing the current janking problems?

I don't know how far they progressed to with it - I just note that the blog was from 2012 - and it appears that they have forgotten their own ideals...

The problem started with Chrome 38 so based on their 6-week cycle I'd guess it will be fixed somewhere around Chrome 40-42 in a few months, but it depends on if they've fixed it already.

The best thing to do is to star the bug report and voice your concern in the comments. The main bug report for the issue appears to be this one: https://code.google.com/p/chromium/issues/detail?id=422000 (Google are closing other reports as duplicates of this one)

Hmmmmm.......

Most people rely on chrome for c2 games.

Chrome is broken, for some months already. This means for most people, that c2 is broken because chrome is broken. And the best we can do is wait a few more months for chrome to be fixed so that c2 is no longer broken!

That is of course if the next chrome release fixes it.

This is of course - as noted in other related topics - becoming a familiar scenario.

There is a song you may be familiar with: video killed the radio star.

Our song could be: chrome killed the video game star (c2).

This not a good way to start 2015....