Closed
Bug 101153
Opened 23 years ago
Closed 20 years ago
Search messages window has no intrinsic way of closing itself.
Categories
(SeaMonkey :: MailNews: Message Display, defect)
SeaMonkey
MailNews: Message Display
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: bzbarsky, Assigned: mscott)
References
Details
(Keywords: access, fixed-aviary1.0)
Attachments
(1 file, 3 obsolete files)
3.65 KB,
patch
|
Details | Diff | Splinter Review |
Build: linux 2001-09-19-08 nightly. Steps to reproduce: 1) Open mailnews 2) Select Search > Search Messages 3) Try to close the resulting search window Expected results: A button, a menu, or a keyboard shortcut that will close the window. Actual results: have to use the windowmanager's window decorations or menus to close the window.
Reporter | ||
Comment 1•23 years ago
|
||
mpt sez no menu/button, but add a ctrl-w shortcut. Over to mailwindow front end.
Assignee: mpt → sspitzer
Component: User Interface Design → Mail Window Front End
Product: Browser → MailNews
QA Contact: zach → esther
Reporter | ||
Comment 2•23 years ago
|
||
Reporter | ||
Comment 4•23 years ago
|
||
Comment on attachment 50469 [details] [diff] [review] Patch to add a keyboard shortcut Working on a better approach (focus first textfield instead of vbox)
Attachment #50469 -
Attachment is obsolete: true
Reporter | ||
Comment 5•23 years ago
|
||
Updated•23 years ago
|
OS: Linux → All
Hardware: PC → All
Comment 6•23 years ago
|
||
Comment on attachment 50490 [details] [diff] [review] Better patch (I'm starting to like xbl... :) ) This code looks good. r=hwaara
Attachment #50490 -
Flags: review+
Comment 7•23 years ago
|
||
some comments: how do these changes affect the edit filter dialog? looking at them, it looks like it would put focus in the first term (for a new filter). currently, it looks like for a new filter (and an existing filter) we have focus in the filter name area. adding the call to searchVal.focus() in createSearchRow is bad for editing existing filters, since we'll update focus on every row created, right? where does that leave the focus when we're done? does hitting ctrl w do the right thing if a search is in progress? make sure calling close() properly calls our onclose handler which stops the search.
Reporter | ||
Comment 9•23 years ago
|
||
Comment on attachment 50490 [details] [diff] [review] Better patch (I'm starting to like xbl... :) ) Seth, good points. The edit filter dialog would be adversely affected by this. And onclose is _not_ called. In view of that, and the fact that focusing the textfield makes hitting ctrl-w a pain on Linux anyway, I'm going to attach a simpler patch.
Attachment #50490 -
Attachment is obsolete: true
Reporter | ||
Comment 10•23 years ago
|
||
Comment 11•23 years ago
|
||
If you are just going to focus the outermost box, I don't see a reason to do it manually at all. Can't you just skip the .focus() call and do only the ctrl+w thing?
Reporter | ||
Comment 12•23 years ago
|
||
No, because then nothing has focus as the dialog comes up. At that point closing the dialog requires clicking on something first (or hitting tab then ctrl-w, maybe; I have not tested that). This seems poor from an accessibility keyboard-only-UI-access standpoint. Oh, and clicking on the main XUL window does _not_ focus it (a feature apparently). So you have to know to click on a form control if you're clicking.
Comment 13•23 years ago
|
||
Isn't window.close() supposed to notify the onclose event handler? Doesn't seem like something that is supposed to be done manually.
Reporter | ||
Comment 14•23 years ago
|
||
According to hyatt, no. window.close() will call onunload(). Clicking the windowmanager's [x] will call onclose() and then onunload()
Comment 15•23 years ago
|
||
May I ask why we have an onclose() at all if it's bogus (i.e., doesn't trigger on window closure)? This could be something serious we need to fix.
Reporter | ||
Comment 16•23 years ago
|
||
Hakan, onclose() triggers if the window is closed externally (ie by the windowmanager). I believe the assumption is that if we're closing the window from inside the window itself we will handle closure properly. The point of onclose() is that if it returns "false" the window is _not_ closed. In other words, onclose() is where you put things like confirmation dialogs that allow the user to "cancel" closing a window that has unsaved content. Or so I understand from talking to hyatt.
Comment 18•23 years ago
|
||
*** Bug 121437 has been marked as a duplicate of this bug. ***
Updated•23 years ago
|
Summary: Search window in mailnews has no intrinsic way of closing itself. → Search messages window has no intrinsic way of closing itself.
Comment 19•22 years ago
|
||
*** Bug 123766 has been marked as a duplicate of this bug. ***
Comment 20•20 years ago
|
||
nominating for aviary1.0, and giving to Scott (punt as needed) to see if this could be fixed for Thunderbird. on tbird this would be applicable to the Search Messages and Search Addresses dialogs. on a related tangent, see also bug 183419 --which requests adding a Close button.
Assignee: sspitzer → mscott
Flags: blocking-aviary1.0?
Assignee | ||
Updated•20 years ago
|
Flags: blocking-aviary1.0? → blocking-aviary1.0+
Assignee | ||
Comment 21•20 years ago
|
||
I made Boris's patch also work for the address book search dialog and the filter list dialog. I had already hooked up escape to close all of these dialogs. This patch just adds ctrl-W support. I didn't seem to need the JS that set focus within the box anymore. It worked fine without it. I wonder if something changed over the last couple years that made that not necessary :)
Attachment #52041 -
Attachment is obsolete: true
Assignee | ||
Updated•20 years ago
|
Updated•20 years ago
|
Product: Browser → Seamonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•