Closed Bug 2674 Opened 26 years ago Closed 24 years ago

[FEATURE] Partial keyboard navigation

Categories

(SeaMonkey :: UI Design, defect, P1)

Product:
SeaMonkey
Component:
UI Design
Type:
defect

Tracking

(Not tracked)

Status:
VERIFIED FIXED

People

(Reporter: mdatt, Assigned: mcafee)

References

Details

(Whiteboard: [PDT-]cut is already working)

Attachments

(2 files)

Status of keyboard shortcuts/navigation
6.54 KB, text/html
Details
latest status of keyboard shortcuts
6.27 KB, text/html
Details 
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: 4015 → 4130
QA contact re-assigned to UI Navigation owner.
Assignee: joki → saari
This is a hotkey/accelerator thing.  Chris, I believe you owned this last.
QA Contact: 4130 → 4137
setting QAC to correct owner and adding myself to cc list
Assignee: saari → sdagley
Actually Steve Dagley is officially handling keybinding these days
Status: NEW → ASSIGNED
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.
Target Milestone: M4 → M5
Target Milestone: M5 → M6
Pushing back to M6 when we expect the blocking issues to be resolved
Target Milestone: M6 → M8
Key binding is now an M8 task
Assignee: sdagley → saari
Status: ASSIGNED → NEW
and on saari's plate.
Assignee: saari → don
Keybinding is in, so I'm tossing this over the wall to XPApps.

Fire in the hole don!
Component: Event Handling → XPApps
OS: Windows 98 → All
Priority: P2 → P1
Hardware: PC → All
Summary: cant use keyboard to navigate → [FEATURE] Keyboard navigation
Target Milestone: M8 → M9
Moving to M9 until I decide whom to doom with this and when ...
Target Milestone: M9 → M10
OK, move to M10 until I find a warm body ...
Blocks: 10575
Target Milestone: M10 → M11
Whiteboard: Need to find an owner for this -- mcafee?
Assignee: don → mcafee
Whiteboard: Need to find an owner for this -- mcafee?
Target Milestone: M11 → M13
Chris, let's get together and figure out exactly how much work is in this
sucker.
Blocks: 3593
Isn't bug #12654 a duplicate of this? Just a Guess.
Target Milestone: M13 → M14
*** Bug 12654 has been marked as a duplicate of this bug. ***
Move to M14.
No longer blocks: 10575
We need to scope the amount of work we're doing for beta 1.
Summary: [FEATURE] Keyboard navigation → [FEATURE] Partial keyboard navigation
Target Milestone: M14 → M13
Renamed partial keyboard navigation.
Target Milestone: M13 → M14
*** 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
Keywords: beta1
pdt would like to know which keyboard navigation features do not work
PDT needs more info please.
QA Contact: cpratt → paulmac
Whiteboard: [NEED INFO]
Sairuh, can you give pdt team quick rundown on this or just point team to the 
doc you made a little while back?
QA Contact: paulmac → sairuh
good place to look at now is bug 22529.
Depends on: 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.
Whiteboard: [NEED INFO] → [PDT+]
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.
Whiteboard: [PDT+] → cut is already working
We're marking this - because cut is fixed.
Whiteboard: cut is already working → [PDT-]cut is already working
m15
Target Milestone: M14 → M15
Move to M16 for now ...
Target Milestone: M15 → M16
per Don, marking this fixed. Sounds like any remaining issues should be separate 
bugs
Status: NEW → RESOLVED
Closed: 24 years ago
Resolution: --- → FIXED
'k. verif.
Status: RESOLVED → VERIFIED
Product: Core → Mozilla Application Suite
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Creator:
Created:
Updated:
Size: