I suspect shadowrun was actually hoping to get the later .160 build, that supposedly fixes our issue.
What's quite frustrating is that there seems to be such a long delay in getting a new build out to the dev channel, when there's an acknowledged major bug in the current (.159) build that has already been *fixed* in later builds... -PJC On Jan 30, 9:37 pm, dhhwai <[email protected]> wrote: > @Shadowrun, the Chrome Dev channel details explains your situation > (http://dev.chromium.org/getting-involved/dev-channel): > > "Going Back to a More Stable Channel: > If you decide to switch from Dev to Beta or from Beta to Stable, the > new channel will be on an earlier version of Google Chrome. You > *won't* get automatic updates on that channel until it reaches a > version later than what you're already running. > > You can uninstall Google Chrome and re-install > fromhttp://www.google.com/chrome > to go back to an earlier version. (If you want to be on the Beta > channel, you have to run the channel changer again after re- > installing)." > > On Jan 30, 4:25 am, Shadowrun <[email protected]> wrote: > > > > > Yes, PJC, me too. I guess they haven't sent .160 to public. > > > I changed the update channel to beta and official, and still my > > Chrome keeps with 2.0.159. :( :( --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
