267251 - Inconsistent global scope for extensions between OSX and Window/Linux

Status: RESOLVED EXPIRED

(Firefox :: General, defect)

Description

[Curtis Duhn]

User-Agent:       Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041026 Firefox/0.9.2 StumbleUpon/1.993
Build Identifier: Mozilla/5.0 (Windows; U; Windows NT 5.0; en-US; rv:1.7.3) Gecko/20041026 Firefox/0.9.2 StumbleUpon/1.993

In trying to figure out why OutSidebar 0.8 works under Windows and Linux but not
under OSX, I discovered an inconsistency between the platforms.  I don't have an
OSX machine readily available, so I haven't been able to analyze it as deeply as
I would normally like to before submitting a bug, but the behavior is clearly
inconsistent, so I figured I'd go ahead and submit it.


Reproducible: Always
Steps to Reproduce:
My extension overrides the default toggleSidebar() function found in browser.js,
like so:

function newToggleSidebar(aCommandID, forceOpen) {
  // My code executes here...

  // Invoke the original toggleSidebar function
  oldToggleSidebar (aCommandID, forceOpen);
}

// Save a reference to the original toggleSidebar
oldToggleSidebar = toggleSidebar;
// Replace the original toggleSidebar function with my implementation
toggleSidebar = newToggleSidebar;

Actual Results:  
In Mac OSX, my newToggleSidebar() function never gets called.  This leads me to
believe that extensions don't share the same global scope with browser.js under
Mac OSX the way they do under Windows and Linux

Expected Results:  
Under Windows and Linux, my newToggleSidebar() function replaces the original
toggleSidebar() implementation, and invokes that original implementation after
executing its own custom actions (resizing and re-positioning the browser).

Comment 1

[Gervase Markham [:gerv]]

This is an automated message, with ID "auto-resolve01".

This bug has had no comments for a long time. Statistically, we have found that
bug reports that have not been confirmed by a second user after three months are
highly unlikely to be the source of a fix to the code.

While your input is very important to us, our resources are limited and so we
are asking for your help in focussing our efforts. If you can still reproduce
this problem in the latest version of the product (see below for how to obtain a
copy) or, for feature requests, if it's not present in the latest version and
you still believe we should implement it, please visit the URL of this bug
(given at the top of this mail) and add a comment to that effect, giving more
reproduction information if you have it.

If it is not a problem any longer, you need take no action. If this bug is not
changed in any way in the next two weeks, it will be automatically resolved.
Thank you for your help in this matter.

The latest beta releases can be obtained from:
Firefox:     http://www.mozilla.org/projects/firefox/
Thunderbird: http://www.mozilla.org/products/thunderbird/releases/1.5beta1.html
Seamonkey:   http://www.mozilla.org/projects/seamonkey/

Comment 2

[Gervase Markham [:gerv]]

This bug has been automatically resolved after a period of inactivity (see above
comment). If anyone thinks this is incorrect, they should feel free to reopen it.