Closed Bug 133073 Opened 23 years ago Closed 23 years ago

Active panel being loaded although sidebar is hidden

Categories

(SeaMonkey :: Sidebar, defect)

Product:
SeaMonkey
Component:
Sidebar
Platform:
x86
Linux
Type:
defect
Priority:
Not set
Severity:
major

Tracking

(Not tracked)

Status:
VERIFIED WORKSFORME

People

(Reporter: BenB, Assigned: samir_bugzilla)

Details

(Keywords: privacy, qawanted, regression) 

Reproduce:
1. javascript:window.sidebar:addPanel("Broken Panel",
"http://server.panel.invalid/panel.html");
2. Close sidebar via View|Sidebar
3. Wait

Actual result:
Msg pops up "Unable to contact server.panel.invalid".

Expected result:
Hidden Sidebar and all its panels are inactive.

Additional Comments:
- Hit this by accident, not sure, if there are better / more correct
reproduction steps.
- Seems like bug 53239 has never been fixed correctly or it regressed.
Keywords: mozilla1.0, privacy
Keywords: regression
Can't reproduce this on a 2002032508 Win2K or Linux build.
Status: NEW → RESOLVED
Closed: 23 years ago
Resolution: --- → WORKSFORME
Can we maybe have others test this before marking as wfm?
I am using a proxy, in case that matters.
Keywords: qawanted
verified.
Status: RESOLVED → VERIFIED
sujay, did you test it yourself?
Ben,
Do you have a panel that is doing something in the background?  Have you
examined the panel's (<browser>'s) src attribute using the DOM Inspector?  Is it
the same as the content attribute or about:blank?  I couldn't reproduce this but
if you can reproduce it by, say, a panel that keep's tossing alerts up every few
seconds even after closing the sidebar then the bug needs to be reopened for
exmaination.  

Something like this:
<html>
  <head>
    <script>
    function tossUpAlert()
    {
      alert("panel-hidden-but-active test");
      setTimeout(tossUpAlert, 5000);
    }
    </script>
  </head>
  <body onload="setTimeout(tossUpAlert, 5000);">
  </body>
</html>
This just surfaced again in bug 139894
sgehani, sorry, but I have no time to make such dedicated tests. That's IMO the
job of your QA (WFM means "All attempts at reproducing this bug were futile,
reading the code produces no clues as to why this behavior would occur").
Product: Browser → Seamonkey
You need to log in before you can comment on or make changes to this bug.