This bug is for tracking what needs to be done in order to turn on Cocoa widgets on the trunk. If you want to know why we're doing this, read this: http://weblogs.mozillazine.org/josh/archives/2005/12/why_cocoa_widgets.html
*** Bug 111230 has been marked as a duplicate of this bug. ***
Created attachment 233282 [details] [diff] [review] make cocoa default, v1.0 I think this is all we need.
Comment on attachment 233282 [details] [diff] [review] make cocoa default, v1.0 lets turn this on.
This has broken at least SeaMonkey. Cmd+l doesn't focus the URL bar any longer (I get a system beep instead), I can't D&D e-mails into other folders (the folders don't highlight, and letting go doesn't drop them in), and the context menu stops highlighting the items I'm over after a second or two (though if I click anyway the item under the cursor does get executed). Going back from "cocoa" to "mac" in my local build fixes those things for me.
Drag'n'drop is pretty much the biggest regression in Cocoa widgets right now, and I have that fixed in my own tree. The patch should make it to the trunk soon. As for the rest of the bugs, please file them individually so I can fix them.
Ok, so I get why we want to switch to cocoa, but why not wait with switching the default until you've fixed the bugs you're aware of?
they're being fixed quickly -- it is the trunk... there are bound to be bugs. We need a wider set of people testing these builds to find issues we _don't_ know about so that we can turn cocoa-cairo on asap.
I guess I feel you could've waited till some of the more blatant bugs were fixed, but I agree with your strategy to get this out there so we can flush out the bugs we don't know about. Is there a bug for the D&D issue?
Bug 332913 is drag'n'drop. I have a patch for it but I want the Cocoa clipboard to land first.