Uncaught TypeError - invalid input

[ghost]

Hi,

I'm getting the following messages when including uri.js:

I've tried various combinations (with/without jquery, ipv6, punycode; minified, only whitespace). Same error in Chrome and IE10, maybe this issue is related to SharePoint 2013 wrapping the script files? Including jQuery or other scripts in my SharePoint page does work fine.

Regards

[rodneyrehm]

Is that live somewhere? What's the input that causes this? use the debugger to break where the error is thrown to see what the passed value is. (apparently it's not a string, DOM node, URI instance, or object representing window.location)

[ghost]

This is not publicly live, sorry.

Should have mentioned: the error occurs even if not using any URI(), it's just included (besides jquery itself) without calling any method.

[rodneyrehm]

is the jQuery plugin loaded as well? Can you please try the debugger anyway?

[rodneyrehm]

closing because OP did not provide a test-case for reproduction.

[mdoelker]

I encountered this error myself today. It occurs when setting href/src using a String object rather than a string. I noticed it when setting an image src through jQuery using a String object which works fine when using jQuery but will fail when URI.js with jQuery plugin is loaded. Easy fix is wrapping the value with String(), thus converting it to a primitive string.

So why would you use String objects over primitives? Apparently jQuery calls .each() with this being a String object whereas the value passed to the callback is of type string like you would expect. See this example:

$.fn.logType = function () {
    this.each(function (i, value) {
        console.log(value, typeof this, typeof value);
    });
};

$(["one", "two", "three"]).logType();

/*
logs:

one object string
two object string
three object string
*/

So it's easily possible to run into this problem without even knowing what you did wrong.

See this fiddle that produces the error: http://jsfiddle.net/n3y27v2f/

[rodneyrehm]

Thank you @mdoelker! I just committed a fix, please check if that solves your problem