Open Bug 87593 Opened 24 years ago Updated 6 months ago

dirviewer focus issues

Categories

(Core :: XUL, defect, P3)

x86
Windows NT
defect

Tracking

()

mozilla1.2alpha

People

(Reporter: vda, Unassigned)

References

Details

(Whiteboard: [xul dirviewer])

Open any local folder (type C:<enter> in address input field) 1. Arrow keys don't move cursor (even pressing <tab> does not help) You have to click on something with a mouse first. 2. Now, press <tab> once. Cursor grays out, but what have got focus now? Cursor keys do not have any effect. Press <tab> again. Now we are at address input field. ok. Press <tab> several times and try to understand where you are... a little bit weird, eh? :-) 3. Try to hold down <donw arrow> while in dir listing. Cursor movement is sluggish even on PIII 600... 4. Navigate to some *.htm[l] file and press Enter. Nothing. Mozilla isn't my default browser, but it is clear that I wanted it to be opened! Mouse doubleclick works.
Please file these as 4 separate bugs. ALso, check for duplicates -- I'm pretty sure that #2 is already filed, and others may be too.
Summary: Keyboard navigation is not friendly → Keyboard focus/navigation messed up in local directory view
#4 is a dup of a bug i had filed [originally for the linux file picker, though], bug 80373.
i think this will belong to widgets/trees eventually if there is a bug left when we're done complaining about dupes.
#2 is due to lack of focus feebback in outliners and trees (without items selected). I've posted a fix (with r=) at 64076
getting off unconfirmed.
Status: UNCONFIRMED → NEW
Ever confirmed: true
over to default keyboard owner
Assignee: alecf → aaronl
-> bbaetz, directory view stuff
Assignee: aaronl → bbaetz
Priority: -- → P3
Target Milestone: --- → mozilla1.1
-> 0.9.7 for dirviewer rewrite.
Target Milestone: mozilla1.1 → mozilla0.9.7
Actually, keyboard navigation is bug 29030. Updating summary.
Summary: Keyboard focus/navigation messed up in local directory view → [xul direviewer] focus messed up
Given the <tree>-><listbox> changes, which mean that <tree> will become <outliner> automatically (and my current time constraints), I'm going to push this off for the moment. 0.9.8 is out for me, so that means 0.9.9 The bugs being changed this way either require <outliner> support, or would be a lot easier with such support
Target Milestone: mozilla0.9.7 → mozilla0.9.9
OK, moving all XUL dirviewer bugs to post 1.0. I don't want to be doing this, but there are only so many hours in the day. These will be taken earlier if someone submits a patch, or I find time.
Target Milestone: mozilla0.9.9 → mozilla1.0.1
Following the roadmap, 1.0.1 is a maintenance release, so pushing off features (xul direviewer) to 1.1
Target Milestone: mozilla1.0.1 → mozilla1.1
xul dirviewer bugs -> 1.2. I have no time..
Target Milestone: mozilla1.1alpha → mozilla1.2alpha
Summary: [xul direviewer] focus messed up → dirviewer focus issues
Whiteboard: [xul dirviewer]
Blocks: 140346
QA Contact: bugzilla → keyboard.navigation
Component: Keyboard: Navigation → User events and focus handling

The bug assignee didn't login in Bugzilla in the last 7 months, so the assignee is being reset.

Assignee: bbaetz → nobody
Severity: minor → S4

This must be issues of how dir listing is implemented.

Component: DOM: UI Events & Focus Handling → DOM: Networking
Whiteboard: [xul dirviewer] → [xul dirviewer][necko-triaged]

Clicking isn't needed anymore.
Tab will let you tab through the items. Arrows don't work.
Return will open the selected item

Moving to XUL, this isn't a networking issue

Component: DOM: Networking → XUL
Whiteboard: [xul dirviewer][necko-triaged] → [xul dirviewer]
You need to log in before you can comment on or make changes to this bug.