I assume this is just an unimplemented feature as of yet, but I figured I'd report it just in case it is. Cant use keyboard for navigation (i.e. i usually use alt+<- for back and alt+-> for forward etc.)

Setting all current Open/Normal to M4.

per leger, assigning QA contacts to all open bugs without QA contacts according to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser

QA contact re-assigned to UI Navigation owner.

This is a hotkey/accelerator thing. Chris, I believe you owned this last.

setting QAC to correct owner and adding myself to cc list

Actually Steve Dagley is officially handling keybinding these days

The KeyBind manager is checked in but there are some issues with the event model on Windows that are blocking its use. Pushing this bug back to M5.

Pushing back to M6 when we expect the blocking issues to be resolved

Key binding is now an M8 task

and on saari's plate.

Keybinding is in, so I'm tossing this over the wall to XPApps. Fire in the hole don!

Moving to M9 until I decide whom to doom with this and when ...

OK, move to M10 until I find a warm body ...

Chris, let's get together and figure out exactly how much work is in this sucker.

Isn't bug #12654 a duplicate of this? Just a Guess.

*** Bug 12654 has been marked as a duplicate of this bug. ***

Move to M14.

We need to scope the amount of work we're doing for beta 1.

Renamed partial keyboard navigation.

*** Bug 24961 has been marked as a duplicate of this bug. ***

Basic keyboard navigation (cut, copy, paste, new, new message, etc.) should work for beta. Setting beta-1 keyword

pdt would like to know which keyboard navigation features do not work

PDT needs more info please.

Sairuh, can you give pdt team quick rundown on this or just point team to the doc you made a little while back?

good place to look at now is bug 22529.

wait a sec --i can add that doc as an attachment...which am gonna do right now...

PDT says we would like product marketing to review and make recommendation for whether or not this should be a beta1 PDT+. Thanks. We can look at this on Wednesday at the PDT if the review is done by then. Thanks.

Looking at Sairuh's doc, I think the only thing left that I'd want for beta is cut to work. I can live with everything else.

Putting on PDT+ radar for cut only.

Cut meaning type ^X when the focus is in the urlbar or in a text field/area inside the content window, right? Well, that works now (subject to various focus bugs which saari and hyatt are working on). If that's the only issue, then this bug should be marked PDT+ or closed. I'm not closing it because I'm not clear whether it covers the other accelerators which aren't hooked in the browser, e.g. ^F for find. Removing PDT designation to get on radar to see if this was really the only PDT+ issue.

We're marking this - because cut is fixed.

m15

Move to M16 for now ...

per Don, marking this fixed. Sounds like any remaining issues should be separate bugs

'k. verif.