Closed
Bug 2674
Opened 26 years ago
Closed 25 years ago
[FEATURE] Partial keyboard navigation
Categories
(SeaMonkey :: UI Design, defect, P1)
SeaMonkey
UI Design
Tracking
(Not tracked)
VERIFIED
FIXED
M16
People
(Reporter: mdatt, Assigned: mcafee)
References
Details
(Whiteboard: [PDT-]cut is already working)
Attachments
(2 files)
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.)
Comment 2•26 years ago
|
||
per leger, assigning QA contacts to all open bugs without QA contacts according
to list at http://bugzilla.mozilla.org/describecomponents.cgi?product=Browser
Updated•26 years ago
|
Assignee: joki → saari
Comment 4•26 years ago
|
||
This is a hotkey/accelerator thing. Chris, I believe you owned this last.
Updated•26 years ago
|
QA Contact: 4130 → 4137
Comment 5•26 years ago
|
||
setting QAC to correct owner and adding myself to cc list
Updated•26 years ago
|
Assignee: saari → sdagley
Comment 6•26 years ago
|
||
Actually Steve Dagley is officially handling keybinding these days
Updated•26 years ago
|
Status: NEW → ASSIGNED
Comment 7•26 years ago
|
||
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
Updated•26 years ago
|
Target Milestone: M5 → M6
Comment 8•26 years ago
|
||
Pushing back to M6 when we expect the blocking issues to be resolved
Updated•26 years ago
|
Target Milestone: M6 → M8
Comment 9•26 years ago
|
||
Key binding is now an M8 task
Updated•26 years ago
|
Assignee: sdagley → saari
Status: ASSIGNED → NEW
Comment 10•26 years ago
|
||
and on saari's plate.
Updated•26 years ago
|
Assignee: saari → don
Comment 11•26 years ago
|
||
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
Comment 12•26 years ago
|
||
Moving to M9 until I decide whom to doom with this and when ...
Comment 13•26 years ago
|
||
OK, move to M10 until I find a warm body ...
Assignee: don → mcafee
Whiteboard: Need to find an owner for this -- mcafee?
Target Milestone: M11 → M13
Comment 14•25 years ago
|
||
Chris, let's get together and figure out exactly how much work is in this
sucker.
Comment 15•25 years ago
|
||
Isn't bug #12654 a duplicate of this? Just a Guess.
Comment 16•25 years ago
|
||
*** Bug 12654 has been marked as a duplicate of this bug. ***
Comment 17•25 years ago
|
||
Move to M14.
Comment 18•25 years ago
|
||
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
Comment 19•25 years ago
|
||
Renamed partial keyboard navigation.
Comment 20•25 years ago
|
||
*** Bug 24961 has been marked as a duplicate of this bug. ***
Comment 21•25 years ago
|
||
Basic keyboard navigation (cut, copy, paste, new, new message, etc.) should work
for beta. Setting beta-1 keyword
Keywords: beta1
Comment 22•25 years ago
|
||
pdt would like to know which keyboard navigation features do not work
Comment 23•25 years ago
|
||
PDT needs more info please.
QA Contact: cpratt → paulmac
Whiteboard: [NEED INFO]
Comment 24•25 years ago
|
||
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
Comment 26•25 years ago
|
||
wait a sec --i can add that doc as an attachment...which am gonna do right
now...
Comment 27•25 years ago
|
||
Comment 28•25 years ago
|
||
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.
Comment 29•25 years ago
|
||
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.
Comment 31•25 years ago
|
||
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
Comment 32•25 years ago
|
||
We're marking this - because cut is fixed.
Whiteboard: cut is already working → [PDT-]cut is already working
Comment 34•25 years ago
|
||
Comment 36•25 years ago
|
||
per Don, marking this fixed. Sounds like any remaining issues should be separate
bugs
Status: NEW → RESOLVED
Closed: 25 years ago
Resolution: --- → FIXED
Updated•20 years ago
|
Product: Core → Mozilla Application Suite
You need to log in
before you can comment on or make changes to this bug.
Description
•