Hi,

Somehow I am having troubles understanding the scoping problem in the code below. I assumed an anonymous function would capture dynamically the scoping of its surrounding vars. From what I read on Javascript this should work.
As I am not a Javascript expert, in fact, its my first use of the language, I might as well have applied the concept wrong.

In the example below I would expect isWincognito and isTabcognito to point to the values determined by the callback functions.

Any help is greatly appreciated!

Code:

	function isIncognitoMode() {
		// it seems that the scope of is(Win|Tab)cognito 
		// not captured properly when accessed in anonymous function

		var isWincognito = false;
		var isTabcognito = false;

		// get win & tag incognito states
		chrome.windows.getCurrent(function(win) {
			isWincognito = win.incognito;
		});
		chrome.tabs.getCurrent(function(tab) {
			isTabcognito = tab.incognito;
		});

                // somehow is(Win|Tab)cognito do not point to the values 
                // determined by the callback functions.
		//console.log(this.isWincognito);
		return isTabcognito || isWincognito;
	}

Thanks!

Fabio

The problem is not the scope ... it's a racing condition frequently happening with (asynchronous) callbacks.

1. You set isWincognito and isTabcognito to false
2. You initiate two asynchronous functions ... the program flow doesn't wait for the callbacks to end
3. You return false
4. "Some time after" the return the callbacks are being executed and change isWincognito or isTabcognito in the correct scope (the closure) ... but the return is "long" done