Closed
Bug 28663
Opened 26 years ago
Closed 25 years ago
choose app window does not close on exit
Categories
(Core :: XUL, defect, P5)
Tracking
()
RESOLVED
WORKSFORME
M18
People
(Reporter: Tanyel, Assigned: danm.moz)
References
Details
(Whiteboard: [nsbeta3-[minus]] will be fixed by bug 47203. see 2000-8-16 comments)
When there is an unknown file type and the "pick app" window opens, if I close
the browser window, the "pick app" window remains open and there is no way to
close it. It was the build downloaded on 2-20-2000.
![]() |
||
Comment 1•26 years ago
|
||
assigning to the browser product
![]() |
||
Comment 2•26 years ago
|
||
this time for sure
Assignee: endico → trudelle
Component: Misc → XP Toolkit/Widgets
Product: Architecture → Browser
QA Contact: nobody → paulmac
Version: 5.0 → other
![]() |
||
Comment 3•26 years ago
|
||
I'm unable to reproduce this using today's Netscape build running on Win98.
Resolving as wfm, if you're still seeing it, please provide the exact steps and
information needed to reproduce.
Status: NEW → RESOLVED
Closed: 26 years ago
Resolution: --- → WORKSFORME
![]() |
Reporter | |
Comment 4•26 years ago
|
||
Okay. First, I loaded the browser on my Windows 98 computer with 32 megabytes
of RAM, using the 2-21-2000 build. Then I typed the address of a directory on
one of my local drives. Mozilla produced a list of files in that directory.
Then I clicked on a Microsoft Word file in the file list. The "Unknown File
Type" box came up. Then I clicked on the X to close the browser window without
closing the "Unknown File Type" box. After the browser window closed, I
clicked on "Cancel" in the "Unknown File Type" box. Then it locked up. This
happens every time I do it.
Status: RESOLVED → REOPENED
Resolution: WORKSFORME → ---
![]() |
||
Comment 5•26 years ago
|
||
No doubt related to low memory. reassigning to danm as p3 for m16
Assignee: trudelle → danm
Status: REOPENED → NEW
Target Milestone: M16
![]() |
||
Comment 6•26 years ago
|
||
Mass-moving all M16 non-feature bugs to M17, which we still consider to be
part of beta2
Target Milestone: M16 → M17
![]() |
||
Comment 7•26 years ago
|
||
spam, open xptoolkit qa contact moving over to jrgm
QA Contact: paulmac → jrgm
![]() |
||
Comment 9•25 years ago
|
||
mass-moving all bugs to m21 that are not dofood+, or nsbeta2+
Target Milestone: M18 → M21
![]() |
Assignee | |
Comment 10•25 years ago
|
||
Not a low memory problem, but a problem with modality. This is a facet of the
"modal windows don't have proper parents" bug 25684. These are seldom easy to
fix, but generally important.
Keywords: nsbeta3
![]() |
||
Comment 12•25 years ago
|
||
Is anyone else seeing the lockup that Tanyel describes? Anything really bad
happening, or is this just a leftover window?
![]() |
Assignee | |
Comment 13•25 years ago
|
||
So does this bug describe the "pick app" dialog, or the "unknown content type"
dialog? It seems to begin with one, then move on to the other. I'm going to
assume it describes the unknown content dialog, which is the only one I'm able to
make appear with recent builds. (The pick app dialog is supposed to work for
certain mime types right now, but it doesn't seem to be.)
Alright yes, there are problems with the unknown content type dialog. It isn't
modal or dependent -- making it either would solve the specific complaint in this
bug report (that the dialog remains open after the browser window has been
closed.) But the dialog remaining open isn't the real problem, it seems to me. In
my testing, there always seems to be a crash coming at some point after you've
closed the browser window.
So, it would be trivial to make this dialog modal or dependent, but then it
just crashes somewhere else. Something's quite broken here. However, this entire
dialog is being removed, to be replaced with the pick app dialog (see nsbeta3+
bug 47203, which describes ftp downloads specifically, though it's actually
applicable to all protocols). The new pick app dialog works completely
differently -- it's supposed to be modal, for one thing. And the background file
download will be handled differently.
There are probably other bugs lurking behind that door. But since the dialog
described in this bug is slated for removal, this bug at least is slated to
magically disappear. I'm making this bug dependent on that one, reducing its
priority, and intending to ignore it unless something bad happens.
Depends on: 47203
Priority: P3 → P5
Whiteboard: [nsbeta3+] → [nsbeta3+] will be fixed by bug 47203. see 2000-8-16 comments
![]() |
||
Comment 14•25 years ago
|
||
PDT downloading this bug to [nsbeta2-].
Whiteboard: [nsbeta3+] will be fixed by bug 47203. see 2000-8-16 comments → [nsbeta3-[minus]] will be fixed by bug 47203. see 2000-8-16 comments
![]() |
||
Comment 15•25 years ago
|
||
resolving as wfm now that bug 47203 has landed
Status: ASSIGNED → RESOLVED
Closed: 26 years ago → 25 years ago
Resolution: --- → WORKSFORME
You need to log in
before you can comment on or make changes to this bug.
Description
•