Closed
Bug 167682
Opened 23 years ago
Closed 21 years ago
Save dialog has problems when choosing directory
Categories
(Core :: XUL, defect)
Tracking
()
VERIFIED
DUPLICATE
of bug 130477
People
(Reporter: nospam, Assigned: janv)
References
Details
User-Agent: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827
Build Identifier: Mozilla/5.0 (X11; U; Linux i686; en-US; rv:1.1) Gecko/20020827
When you want to save i.e. a page as a file and in the "Save As" window
double-click the folder at the very bottom of the current view, Mozilla falsely
identifies your double-click as 2 separate mouse clicks. It then scrolls the
view and then enters a completely different directory as a result of the second
click.
Reproducible: Always
Steps to Reproduce:
This bug repeats since Mozila 0.99 as far as i remember.
Actual Results:
as explained in details
Expected Results:
Mozilla should definitely enter the directory you double-click at regardless of
the folder orientation in the current view.
Comment 1•23 years ago
|
||
Confirmed on Linux (Build ID: #2002090922)
On the second click, the dialog actually recognizes *both* the single and double
click. It recognizes the single click by highlighting the next entry in the
list, THEN it recognizes the double-click by actually entering that directory.
Note: You need to be browsing a directory tree that requires you to scroll. Try /.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Summary: save as file dialog has problems when choosing directory → Save dialog has problems when choosing directory
| Reporter | ||
Comment 2•23 years ago
|
||
Correct. In fact what is happening, is that a single mouse click forcing the
directory browser to scroll down has a precedence over the double-click.
The functions should be swapped in their order: FIRST to distinguish whether
we've to deal with a double-click, if YES, then go and enter the selected directory.
If NO, scroll the view down.
Comment 3•23 years ago
|
||
-> File Handling
Assignee: asa → law
Component: Browser-General → File Handling
QA Contact: asa → sairuh
Updated•23 years ago
|
QA Contact: sairuh → petersen
| Reporter | ||
Comment 4•21 years ago
|
||
Just gave it a try and reproduced exactly on Mozilla/5.0 (X11; U; Linux i686;
en-US; rv:1.6) Gecko/20040113
Comment 5•21 years ago
|
||
*** Bug 199861 has been marked as a duplicate of this bug. ***
Comment 6•21 years ago
|
||
Neil, any way to make this happier? Can this be done in the filepicker, or does
the tree code need fixing?
Assignee: law → jag
Component: File Handling → XP Apps
QA Contact: chrispetersen → pawyskoczka
Comment 7•21 years ago
|
||
The tree click code likes to make the clicked-on row visible, so if it's
partially obscured it will scroll the row up. I tried it with my custom tree
demo, and if I double-click the obscured row it is in fact the row below that
will expand, so the tree's internal double-click handler has the same bug.
Jan, I suggest a) clickcount="1" on the treebody mousedown/click handlers and b)
using currentIndex in the tree's own doubleclick handler, does that sound OK?
Assignee: jag → varga
Component: XP Apps → XP Toolkit/Widgets: Trees
QA Contact: pawyskoczka → shrir
| Assignee | ||
Comment 8•21 years ago
|
||
Sounds like bug 130477
| Reporter | ||
Comment 9•21 years ago
|
||
Correct, this is a dupe of Bug 130477
Sorry for not originally finding it.
Besides, what Boris in #7 says, is to my opinion the best approach. Since we
won't have to let any timeouts to pass. If the click is just single, file picker
scrolls immediately. If it's followed by another click thus becoming a
double-click the previously highlighted and scrolled-up dir is entered immediately.
The only issue here could be a flicker this scroll-up followed by a complete
folder view redraw might produce. Something as described in Bug 143663
*** This bug has been marked as a duplicate of 130477 ***
Status: NEW → RESOLVED
Closed: 21 years ago
Resolution: --- → DUPLICATE
Comment 10•21 years ago
|
||
Verified, I guess.... I'd left this open because it had more info than bug 130477...
And Neil's the one that made comment 7.
Status: RESOLVED → VERIFIED
Component: XP Toolkit/Widgets: Trees → XUL
QA Contact: shrir → xptoolkit.widgets
You need to log in
before you can comment on or make changes to this bug.
Description
•