Can you provide a test case where you'd pass an objectified string instead of a native one ?

I know that using objectified strings is probably not a common case, especially that they get 'stringified' again when concatenated with literal strings:

new String("test") + ""

In my case issue was caused by function extending String prototype.

It was 'truncate' function (taken from prototype.js)

String.prototype.truncate = function(length, truncation) {
    length = length || 30;
    truncation = truncation === undefined ? '...' : truncation;
    return this.length > length ?
        this.slice(0, length - truncation.length) + truncation : this;
    };

Let's say I used it like this:

$("div").html(value.truncate(20));

Everything was fine when

value

was a string longer than 20 chars. It got truncated and displayed. But when it was shorter than 20 chars (so the truncate method returned

this

) the return value was a String object and

html

function failed to run.

Whenever you return

this

from extended String prototype it returns object, not literal string. So simple test case may be function that does 'nothing':

String.prototype.self = function(){ return this; }

What it actuality does is turning literal strings into String objects

I created a page where I run these cases:

http://bartaz.github.com/sandbox.js/string_object_test.html

I know that's not a common issue and it has easy workaround (concatenating with empty "" string before putting into

html

method).

Interesting...i've never returned

this

explicitly when adding a method but I see what you mean. In general I avoid creating String or Number objects like the plague. There are a few cases where Javascript itself won't accept String objects but will accept literal strings. One that I recall is the argument to

eval()

.

If you have your method return

String(this)

instead of

this

it will solve the problem.

This is somewhat similar to #4533 but that one seems easier to fix.

Ok, I think it's quite fair to assume that the bug is in 'truncate' function that should return literal strings in both cases.

But when using additional JS libraries sometimes you don't know if you will always get literal (not object) strings and may be surprised when passing them into jQuery.

It seems to be quite easy to fix, so would be nice to have.

This ticket has been marked as missing a test case. In an effort to reduce the number of outstanding tickets in the bug tracker, it will be closed automatically in 30 days. In order to prevent this from happening, please provide a working test case. If a test case has already been provided and our records are wrong, please respond to the ticket so that it can be fixed. Thank you!

Automatically closed due to 14 days of inactivity.