Closed Bug 231531 Opened 21 years ago Closed 21 years ago

In <chrome://global/content/bindings/tabbrowser.xml>, "Warning: reference to undefined property this.mPanelContainer"

Categories

(SeaMonkey :: Tabbed Browser, defect)

Product:
SeaMonkey
Component:
Tabbed Browser
Type:
defect
Priority:
Not set
Severity:
trivial

Tracking

(Not tracked)

Status:
RESOLVED DUPLICATE of bug 179787
Milestone:
mozilla1.7alpha

People

(Reporter: sgautherie, Assigned: sspitzer)

Details

[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6) Gecko/20040113] (W98SE)

This one happens (twice) just before bug 162432 ("Error: redeclaration of const
MOZILLA_HELP") happens (on first 'Compose' load):
{
Warning: reference to undefined property this.mPanelContainer
Source File: chrome://global/content/bindings/tabbrowser.xml
Line: 1440
}
This line is
{
      <handler event="select" action="if (event.originalTarget ==
this.mPanelContainer) this.updateCurrentBrowser();"/>
}

This one appears only with |user_pref("javascript.options.strict", true);| !
Well, now I know why I was wondering:
Forget about MailNews and bug 162432 !
(My mistake :-<)

It happens at each loading of a new Browser window (Ctrl-N),
including initial loading of Mozilla if started by calling the Browser.
Component: Mail Window Front End → Tabbed Browser
Product: MailNews → Browser
[Mozilla/5.0 (Windows; U; Win98; en-US; rv:1.6b) Gecko/20031208] (W98SE)

Was already there is v1.6b.
Summary: In <chrome://global/content/bindings/tabbrowser.xml>, (strict) "Warning: reference to undefined property this.mPanelContainer" → In <chrome://global/content/bindings/tabbrowser.xml>, "Warning: reference to undefined property this.mPanelContainer"
Fixed in v1.7a nighly.
(How come I did not find it before filing this bug :-<)

*** This bug has been marked as a duplicate of 179787 ***
Severity: normal → trivial
Status: NEW → RESOLVED
Closed: 21 years ago
OS: Windows 98 → All
Hardware: PC → All
Resolution: --- → DUPLICATE
Target Milestone: --- → mozilla1.7alpha
Product: Core → SeaMonkey
You need to log in before you can comment on or make changes to this bug.