cmd-c and cmd-v don't work under fizz-mach
Reporter: Please always add your build ID -> Keyboard navigation
No build ID (no official builds of fizz-mach yet). built from Nov 14 (PM) tree.
is this limited to fizz-mach? if yes, then qa contact should go to zach [till verif bits become available for me to test]... however, lemme know if this is also seen on the usual os x bits available...
do any other cmd keys work? did you try control-v and control-c?
no ctrl-v and ctrl-c do not work. Under certain circumstances (not sure which) I can get cmd-v to work in the URLBar, but in general it (and cmd-c) seem broken.
*** Bug 111796 has been marked as a duplicate of this bug. ***
the problem is that key shortcuts don't work until after the menu has been opened once. Once you do that, they work just fine and dandy. I'm not sure why this is the case, given that we generally don't use the shortcut mechanism provided by the OS....and then, why would this be different from carbon? these binding should be handled by XBL, right saari? could something not be installed correctly? Does that ring a bell dbaron?
here's the problem: when dispatching the key event, the view manager thinks that the x/y position is in one of the views (nsView::PointIsInside() returns true because the view clipRect has a width/height). On CFM, this cliprect has a 0,0 width/height so the event goes on down into the presShell. Any ideas as to why we'd have a sized clipRect on mach-o but not cfm? it's gotta be more ifdef-fu. Thoughts as to where? I didn't find any in the view manager.
*** Bug 118285 has been marked as a duplicate of this bug. ***
Additional info: For me (Build 2002040403) I have to actually choose the menu entry before that particular kbd-shortcut will work. So, if I want to use cmd-c, the first time, I want to copy something, I have to go to the Edit menu and pick it there. After that cmd-c works, but none of the other shortcuts work. They each have to be 'activated', but choosing them in the menu once, and then the shortcut works. Pasting is the same thing. Is this planned for 1.0? Doesn't look like it, but it's a major hassle, and seems like a completeness issue to me.
This now works... with my 20020721 build... and has worked for a few weeks... I am not applying any patches. Just a straight pull and build. This bug should be closed.
resolve as worksforme per comment 11