Closed
Bug 573534
Opened 14 years ago
Closed 14 years ago
onLinkIconAvailable takes aBrowser argument but doesn't use it
Categories
(Firefox :: Tabbed Browser, defect)
Firefox
Tabbed Browser
Tracking
()
RESOLVED
FIXED
Firefox 4.0b2
People
(Reporter: kairo, Unassigned)
References
()
Details
onLinkIconAvailable is currently located in http://mxr.mozilla.org/comm-central/source/mozilla/browser/base/content/browser.js#3925 and called from tabbrowser, see http://mxr.mozilla.org/mozilla-central/search?string=onLinkIconAvailable - and it takes aBrowser as first argument but actually uses gBrowser and never aBrowser, so either that argument should go away (as it is in SeaMonkey) or be used - or possibly have a comment as to why it's not being used. Or is the case WindowsPreviewPerTab.jsm the reason why we need to keep that argument?
Comment 1•14 years ago
|
||
The argument is bogus, the patch in bug 519216 removes it.
Depends on: 519216
Reporter | ||
Comment 2•14 years ago
|
||
(In reply to comment #1) > The argument is bogus, the patch in bug 519216 removes it. Ah, good, then I don't need to care that SeaMonkey doesn't have it. ;-) Also, what about http://mxr.mozilla.org/mozilla-central/source/browser/components/wintaskbar/WindowsPreviewPerTab.jsm#543 - is that called by the same callers and need to change as well in bug 519216 then?
Comment 3•14 years ago
|
||
(In reply to comment #2) > Also, what about > http://mxr.mozilla.org/mozilla-central/source/browser/components/wintaskbar/WindowsPreviewPerTab.jsm#543 > - is that called by the same callers and need to change as well in bug 519216 > then? No, it uses a "tabs progress listener", where the browser argument is actually expected and useful. See addProgressListener vs. addTabsProgressListener.
Reporter | ||
Comment 4•14 years ago
|
||
Ah, OK, I'm not too good at those things, just stumbled into it because I need to do some tabbrowser stuff in bug 554908 to make other patches of mine working better. ;-)
Updated•14 years ago
|
Status: NEW → RESOLVED
Closed: 14 years ago
Resolution: --- → FIXED
Target Milestone: --- → Firefox 3.7b2
You need to log in
before you can comment on or make changes to this bug.
Description
•