Looks like it is still broken in dev channel, I'm on 4.0.249.11 When will the fix arrive on dev channel?
-- Sibil Mohammed On Nov 14, 12:56 am, Aaron Boodman <[email protected]> wrote: > We did not want to release it with this bug either, and I'm really > sorry for the inconvenience. > > Chromium is a huge project with many different constraints, and it > isn't always easy to make everyone happy. In this case, we are > simultaneously trying to push for a new beta candidate without > breaking the dev channel too badly, and this time, getting the beta > done won. > > We need to push dev releases to validate how close we are getting to > beta, and it takes time to create them. If we stop for every bug, it > slows down our progress toward the bigger picture. > > In general the dev channel of Chromium is pretty crazy. There is an > average of about 100 commits per day. Even with lots of automated > testing, things break. Life on the dev channel frequently reminds me > of the saying: "You don't complain the dogs sings badly, it's amazing > the dog sings at all!"[1]. > > It's going to be really nice to get extensions to the beta channel, > where the rate of change is much less frantic. > > [1] I think I mangled that quote, I don't find any hits for it on the web. > > - a -- You received this message because you are subscribed to the Google Groups "Chromium-extensions" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/chromium-extensions?hl=en.
