On Tue, Dec 8, 2009 at 2:31 AM, Mark Wubben <[email protected]> wrote: > On Dec 7, 2009, at 23:27 , Aaron Boodman wrote: >> Extension support is temporarily disabled on mac. It should be >> re-enabled in the next dev channel release. > > I realize we're using a developer channel, but disabling extensions all > together is rather unexpected. Why this move and is there any way I could > have found out earlier?
It was an accident. Right before betas, we always use the dev channel as a proving ground for the new beta. So we recently branched for beta and started releasing devs from that branch, fixing bugs and stabilizing for launch. The changes to enable popups on the mac were made on trunk *after* the branch was cut, but they weren't merged over to the branch. The reason for this was because we weren't planning on enable extensions on mac beta, so we didn't think the changes related to them needed to go to the branch. But we didn't think about the fact that we would be releasing more dev channels from that branch and it would in fact be a regression from that point of view. By the time we figured this out, we were too far into the testing cycle to change it -- it would have been an unacceptably large risk to the overall mac release. Sorry for the trouble. There should be a new mac dev channel release sometime this week that fixes this. Also, you can always use the Chromium nightlies as a temporary workaround when the dev channel goes pear-shaped. - 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.
