Closed
Bug 102914
Opened 24 years ago
Closed 24 years ago
mailnews and address book on component bar temporaraly disabled after closing a tab when dom.disable_open_during_load is set
Categories
(SeaMonkey :: Tabbed Browser, defect)
SeaMonkey
Tabbed Browser
Tracking
(Not tracked)
VERIFIED
FIXED
mozilla0.9.8
People
(Reporter: MozillaUser, Assigned: jst)
References
Details
(Whiteboard: [HAVE FIX])
Attachments
(1 file, 1 obsolete file)
|
1.99 KB,
patch
|
jst
:
review+
brendan
:
superreview+
|
Details | Diff | Splinter Review |
On Windows 95, build 2001100203 and 2001100303
Open a tab (or two or three, it doesnt matter how many)
Close a tab (any tab, it doesnt matter if it was the original tab, or the one
you just opened)
Now try clicking the buttons in the component bar for opening a new mailnews
window or address-book window. No response
The buttons for new browser window and new composer window are fine
The mailnews and address-book buttons will be re-enabled if you load a new page
or reload the current page in any open tab.
Comment 1•24 years ago
|
||
worksforme win2k 2001100308 trunk.
| Reporter | ||
Comment 2•24 years ago
|
||
hmmm... still seeing it on build 2001100403
| Reporter | ||
Comment 3•24 years ago
|
||
Hmmm. I tried this ona different computer, Windows 98 build 2001100303 and I
couldnt reproduce it, but it is still happening on my Win 95 machine. Can
anybody else with Win 95 try this out?
Comment 4•24 years ago
|
||
I'm getting this on Win98 with the 0.9.5 release build.
Comment 5•24 years ago
|
||
worksforme
Status: UNCONFIRMED → RESOLVED
Closed: 24 years ago
Resolution: --- → WORKSFORME
| Reporter | ||
Comment 6•24 years ago
|
||
I can still reproduce this with build 2001102903 on Windows 95.
However, I will not re-open, because I now realize that I cannot reproduce this
on a new clean profile, only on my existing profile. So, this must be some sort
of stale profile data issue. I am still trying to figure out what i can
delete/edit in my profile to make it go away.
| Reporter | ||
Comment 7•24 years ago
|
||
Aha! I figured out what in my profile was causing this. It wasnt mysterious
stale data after-all. It was the pref
user_pref("dom.disable_open_during_load", true);
in my prefs.js file. When I added that line to the prefs.js of a brand new
profile, I was able to reproduce this bug.
That pref is to prevent window.open from inside an onload handler. The only
place it is read is at
http://lxr.mozilla.org/seamonkey/source/dom/src/base/nsGlobalWindow.cpp#2309
That code was put in by mstoltz on Aug 30 21:06 to fix bug 92955
Status: RESOLVED → UNCONFIRMED
Resolution: WORKSFORME → ---
Summary: mailnews and address book on component bar temporaraly disabled after closing a tab → mailnews and address book on component bar temporaraly disabled after closing a tab when dom.disable_open_during_load is set
Comment 8•24 years ago
|
||
Marking NEW. I can reproduce this on Linux build 2001112308 and there is a
duplicate.
Status: UNCONFIRMED → NEW
Ever confirmed: true
Comment 9•24 years ago
|
||
*** Bug 111882 has been marked as a duplicate of this bug. ***
Updated•24 years ago
|
OS: Windows 95 → All
QA Contact: blakeross → sairuh
Hardware: PC → All
Comment 10•24 years ago
|
||
ok, what I think this is: When a tab is closed, a NS_PAGE_UNLOAD event, but no
NS_PAGE_LOAD event is fired. Therefor nsGlobalWindow.mIsDocumentLoaded is false,
and JavaScript is not allowed to open a window (because of the
dom.disable_open_during_load). This could probably be fixed, by firing a page
load event somewhere, BUT I think this approach is fundamentally flawed,
because, not the window, but the document the script belongs to has to decide,
if the JavaScript code is allowed to open a window.
With a current implementation, a page beeing loaded in one tab, can prevent a
script running for another tab (or not for any webpage at all) from opening a
window. This does not make sense. Currently it is not possible to start Mail,
while a page is beeing loaded (without working with tabs at all).
I might be wrong with this, but this is how it looks to me.
Comment 11•24 years ago
|
||
jst: can we make the logic in nsGlobalWindow.cpp for abuse-checking apply only
to content windows? That should fix any chrome window opening problems, I hope.
/be
| Assignee | ||
Comment 12•24 years ago
|
||
Sounds reasonable to me, does this patch fix the problem?
Comment 13•24 years ago
|
||
*** Bug 112599 has been marked as a duplicate of this bug. ***
Updated•24 years ago
|
Status: NEW → ASSIGNED
Target Milestone: --- → mozilla1.1
Comment 14•24 years ago
|
||
*** Bug 114986 has been marked as a duplicate of this bug. ***
Comment 15•24 years ago
|
||
*** Bug 116280 has been marked as a duplicate of this bug. ***
Comment 16•24 years ago
|
||
Does this patch (assuming it's not a rotten one) also fix bug 101189 ?
Comment 17•24 years ago
|
||
adding bugs that this patch should fix to dependency list.
Comment 18•24 years ago
|
||
*** Bug 118357 has been marked as a duplicate of this bug. ***
Comment 19•24 years ago
|
||
Changing priority to normal based on Geraint's comments in bug 118357.
Severity: minor → normal
Comment 20•24 years ago
|
||
Why is this on hyatt's list? Reassigning to jst, who owns the dom, and who will
likely fix it quickly.
/be
Assignee: hyatt → jst
Status: ASSIGNED → NEW
| Assignee | ||
Comment 21•24 years ago
|
||
Attachment #59285 -
Attachment is obsolete: true
| Assignee | ||
Comment 22•24 years ago
|
||
Mitch, would you review this please?
Status: NEW → ASSIGNED
Whiteboard: [HAVE FIX]
Target Milestone: mozilla1.1 → mozilla0.9.8
Comment 23•24 years ago
|
||
Comment on attachment 63840 [details] [diff] [review]
Slight modification of the above patch.
sr=brendan@mozilla.org
Attachment #63840 -
Flags: superreview+
| Assignee | ||
Comment 24•24 years ago
|
||
Comment on attachment 63840 [details] [diff] [review]
Slight modification of the above patch.
Rick says r=rpotts
Attachment #63840 -
Flags: review+
| Assignee | ||
Comment 25•24 years ago
|
||
Fixed.
Status: ASSIGNED → RESOLVED
Closed: 24 years ago → 24 years ago
Resolution: --- → FIXED
Comment 27•24 years ago
|
||
*** Bug 117122 has been marked as a duplicate of this bug. ***
Updated•17 years ago
|
Product: Core → SeaMonkey
You need to log in
before you can comment on or make changes to this bug.
Description
•