Closed
Bug 356703
Opened 18 years ago
Closed 18 years ago
Browsers associated with closed tabs aren't loading a blank document
Categories
(SeaMonkey :: UI Design, defect)
Tracking
(Not tracked)
VERIFIED
FIXED
People
(Reporter: stephend, Assigned: csthomas)
References
Details
(Keywords: helpwanted, regression)
Attachments
(1 file, 1 obsolete file)
3.90 KB,
patch
|
neil
:
review+
jag+mozilla
:
superreview+
|
Details | Diff | Splinter Review |
Build ID: 2006-10-14-13, Windows XP SeaMonkey trunk. Probably fallout from bug 350416 or friends. Summary: Flash-derived audio doesn't stop when closing its tab. Caveat: I searched, and couldn't find a duplicate of this. Additionally, this DOES NOT occur in Firefox trunk (Minefield). Steps to Reproduce: 1. Load a page which contains Flash-based audio, such as Pandora.com or YouTube.com 2. Open a new tab. 3. Now, close the tab with the Flash audio. Expected Results: Audio stops. Actual Results: Audio keeps playing.
Reporter | ||
Comment 1•18 years ago
|
||
So, just as I suspected: setting browser.tabs.undoclose.depth to 0 fixes this...
Blocks: 350416
Assignee | ||
Comment 2•18 years ago
|
||
Backing out https://bugzilla.mozilla.org/attachment.cgi?id=240756&action=edit has no effect. Why is the hidden browser not actually navigating away? Use DOMI to change the linkedbrowser in one of your non-closed tabs to point to the closed browser, and note that it's still on the old page.
Assignee | ||
Updated•18 years ago
|
Summary: Flash-derived audio doesn't stop when closing its tab. → Browsers associated with closed tabs aren't loading a blank document
Reporter | ||
Updated•18 years ago
|
Flags: blocking-seamonkey1.1b?
Assignee | ||
Comment 3•18 years ago
|
||
stephend, this isn't on branch because it crashes gecko.
Flags: blocking-seamonkey1.1b? → blocking-seamonkey1.1b-
Assignee | ||
Updated•18 years ago
|
Keywords: helpwanted
Assignee | ||
Updated•18 years ago
|
Flags: blocking-seamonkey1.5a+
Assignee | ||
Comment 4•18 years ago
|
||
The key lines would be: - oldBrowser.stop(); +// oldBrowser.stop(); I'm pretty sure the first patch chunk is irrelevant as it's for a different bug. I don't know why removing the .stop() before didn't seem to work. The interesting thing is that even with .stop(), the blank tab's title changes, but the page content stays there. I saw biesi saying something about clearing the current page once the next load starts - is it possible that the title changed but the "load" didn't start yet for document-clearing purposes?
Comment 5•18 years ago
|
||
Sorry, I thought the LOAD_FLAGS_FROM_EXTERNAL would suffice to evict the page. We can't allow the blank document to load because of bug 354927.
Assignee | ||
Comment 6•18 years ago
|
||
(In reply to comment #5) > Sorry, I thought the LOAD_FLAGS_FROM_EXTERNAL would suffice to evict the page. > We can't allow the blank document to load because of bug 354927. > Would a new load flag work? ("Don't prompt for SSL"?)
Comment 7•18 years ago
|
||
The SSL dialogs work off the progress notifications.
Assignee | ||
Comment 8•18 years ago
|
||
As far as I can tell, this doesn't change the behavior of https://bugzilla.mozilla.org/attachment.cgi?id=200420 - I get an "entering secure" which is immediately followed by a "leaving secure" alert (kinda odd that the leaving secure happens while the entering is still visible though...). Do we want to add an API for extension authors to add/remove listeners so that they don't go and add a listener, thus regressing bug 313335 when tabs are reopened?
Assignee: guifeatures → cst
Attachment #244457 -
Attachment is obsolete: true
Status: NEW → ASSIGNED
Attachment #245957 -
Flags: superreview?(jag)
Attachment #245957 -
Flags: review?(neil)
Assignee | ||
Comment 9•18 years ago
|
||
Comment on attachment 245957 [details] [diff] [review] patch Let's pretend I had this comment before the secFlags line: //XXXcst warning: make sure these flags match nsDocShell
Assignee | ||
Comment 10•18 years ago
|
||
Comment on attachment 245957 [details] [diff] [review] patch One odd thing I did notice was that doPreview sometimes seemed to fire to show the tooltip, and it was firing at a point where there was no contentWindow, causing that code to throw. Not sure what to do about that. (try {} in doPreview?)
Comment 11•18 years ago
|
||
Comment on attachment 245957 [details] [diff] [review] patch >+ const CiIWP = Components.interfaces.nsIWebProgress; Please use const nsIWebProgress here. r=me with that fixed.
Attachment #245957 -
Flags: review?(neil) → review+
Comment 12•18 years ago
|
||
Comment on attachment 245957 [details] [diff] [review] patch sr=jag with Neil's nit fixed.
Attachment #245957 -
Flags: superreview?(jag) → superreview+
Assignee | ||
Comment 13•18 years ago
|
||
Checking in mozilla/xpfe/global/resources/content/bindings/tabbrowser.xml; /cvsroot/mozilla/xpfe/global/resources/content/bindings/tabbrowser.xml,v <-- tabbrowser.xml new revision: 1.168; previous revision: 1.167 done Things that need to be specially verified: bug 313335, undo close of a tab that had an ssl page, ssl warnings on tabs that were previously closed and reopened.
Status: ASSIGNED → RESOLVED
Closed: 18 years ago
OS: Windows XP → All
Resolution: --- → FIXED
Reporter | ||
Comment 14•18 years ago
|
||
Verified FIXED with build 2006-11-21-09 of SeaMonkey trunk under Windows XP. My understanding of comment 13 is: [22:45] <stephend> if I have netscape.com in one tab, then https://original-oncourse.iu.edu/login/profile/default.asp in another tab [22:45] <stephend> close the HTTPS tab [22:45] <stephend> then restore it, I don't get its alert [22:46] <CTho> stephend: that's the point If this is wrong, let me know.
Status: RESOLVED → VERIFIED
Updated•17 years ago
|
Keywords: fixed-seamonkey2.0a1
You need to log in
before you can comment on or make changes to this bug.
Description
•