Of course, we'd all like to have bug free versions at our fingertips, the dev version isn't supposed to be that version. Technically, its main purpose isn't to facilitate casually surfing the web, but to allow the testing of ideas which may or may not completely break things.
The solution provided by dhhwai is the correct one in that if you want something that works, you should be using a stable release. I can understand where you're coming from, but it just doesn't make sense considering the purposes of the releases. It makes less sense considering the predicted once a week predicted release schedule for the dev channel. Erek On Jan 31, 5:37 am, PJC <[email protected]> wrote: > 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 --~--~---------~--~----~------------~-------~--~----~ Chromium Discussion mailing list: [email protected] View archives, change email options, or unsubscribe: http://groups.google.com/group/chromium-discuss -~----------~----~----~----~------~----~------~--~---
