290882 - StockTicker extension causes a window to report the wrong width

Status: RESOLVED DUPLICATE of bug 303434

(Firefox :: General, defect)

Description

[Julien Lecomte]

User-Agent:       Mozilla/4.0 (compatible; MSIE 6.0; Windows NT 5.0)
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.6) Gecko/20050317 Firefox/1.0.2

Firefox 1.0.2 + StockTicker extension 0.5.2 available from 
addons.update.mozilla.org.

I open a window (window.open) with a width of 200 pixels. The window is indeed 
200 pixels wide, but window.innerWidth reports 385 pixels (changes depending on 
the stock that is currently being displayed).

Note: StockTicker appears as an additional panel in the status bar of every 
window.

Reproducible: Always

Steps to Reproduce:

Comment 1

[Julien Lecomte]

Attachment: Test page

Comment 2

[Julien Lecomte]

Attachment: popup

This contains a table with a width of 100% and reports window.innerWidth every
second.

Comment 3

[Julien Lecomte]

Attachment: StockTicker extension

StockTicker 0.5.2

Comment 4

[Julien Lecomte]

Steps to reproduce:

Download and install StockTicker.
Download test.html and popup.html
Open test.html and click on the "test" button
The window that is opened is 200 pixels wide but window.innerWidth reports 
something completely different and the table fills over 100% of the window 
width...

Comment 5

[Matthias Versen [:Matti]]

Please report that to the stockticker author.
bugzilla is not the place to report errors with extensions

Comment 6

[Julien Lecomte]

I am reopening this bug because I do not think the StockTicker extension is 
responsible here. Basically, having a panel in the status bar of a browser 
window with a long label in it causes window.innerWidth to report the wrong 
value.

Comment 7

[Nickolay_Ponomarev]

I think that a simpler testcase (i.e. a single XUL file with window instead of
an overlay to browser.xul) would be welcome.

Comment 8

[Julien Lecomte]

Filed bug 303434 with a better description and a simple xul overlay. Also, I 
filed it against Core/Layout.

*** This bug has been marked as a duplicate of 303434 ***