sorry about the bad formatting of the bug report the formatting up there should be:

scrollTop  = win.pageYOffset || docElem.scrollTop;
scrollLeft = win.pageXOffset || docElem.scrollLeft;

becomes

scrollTop  = (win && win.pageYOffset) || docElem.scrollTop;
scrollLeft = (win && win.pageXOffset) || docElem.scrollLeft;

Thanks for taking the time to contribute to the jQuery project! Please provide a complete reduced test case on jsFiddle to help us assess your ticket.

Additionally, be sure to test against the jQuery Edge version to ensure the issue still exists. To get you started, use this boilerplate: http://jsfiddle.net/FrKyN/. Open the link and click to "Fork" (in the top menu) to get started.

Sorry, I can't make a repro case in jsfiddle because the bug only occurs when jQuery is running inside of a Chrome Extension, but the proposed fix is trivial.

For more explanation of what's going on... the jQuery function getWindow will return null if a document node has no defaultView or parentWindow property.

function getWindow( elem ) {
	return jQuery.isWindow( elem ) ?
		elem :
		elem.nodeType === 9 ?
			elem.defaultView || elem.parentWindow :
			false;
}

So under the condition where elem.nodeType === 9, but elem.defaultView and elem.parentWindow are both null or undefined, the function returns null or undefined.

This code is then called by the offset function like this, with the assumption that win will never be null or undefined:

	win = getWindow( doc );
	clientTop  = docElem.clientTop  || body.clientTop  || 0;
	clientLeft = docElem.clientLeft || body.clientLeft || 0;
	scrollTop  = win.pageYOffset || docElem.scrollTop;
	scrollLeft = win.pageXOffset || docElem.scrollLeft;

In this caase, an exception is thrown when win.pageYOffset is hit.

What I propose above is to do a null check before using win.pageYOffset and win.pageXOffset. Another solution would be to return false from getWindow in this case

function getWindow( elem ) {
	return jQuery.isWindow( elem ) ?
		elem :
		elem.nodeType === 9 ?
			elem.defaultView || elem.parentWindow || false :
			false;
}

Either change will fix the problem.

Unfortunately, if we don't have a way to test for this being needed, we have no way to prevent regressions. Can you provide some more information about why a Chrome extension is running that code without a window? For example, why ask for an offset if you can't get it? What's the impact on the code of not having an offset? Would it make more sense for the Chrome extension to check that in advance?

Because we get so many tickets, we often need to return them to the initial reporter for more information. If that person does not reply within 14 days, the ticket will automatically be closed, and that has happened in this case. If you still are interested in pursuing this issue, feel free to add a comment with the requested information and we will be happy to reopen the ticket if it is still valid. Thanks!