Symbol bug set unconfigure object trigger stack overflow

[ghost]

function set_(o, k, d) {
    Object.defineProperty(o, k, Object.assign({
        enumerable: true,
        configurable: true
    }, d));
    return o;
}

function set(k) {
    set_(Object.prototype, k, {
        set: function (v) {
            console.info('set %s of %O to %s', k, this, v);
            set_(this, k, {value: v, writable: true});
        }
    });
    return function (o, v) {
        o[k] = v;
        return o;
    };
}

set('a')({}, 7).a // 7
set('a')(localStorage, 7).a // stackoverflow for IE 11

[zloirock]

I don't quite understand what do you mean. I see this problem in IE11 without core-js too.

[ghost]

https://jsfiddle.net/gob1j3dc/

[zloirock]

Yep, usage Symbol polyfill with the current approach on IE11 localStorage is not a good idea. Exotic environment objects (and their non-standard / buggy implementations) out of the core-js scope. Or you can propose any solution?

[ghost]

There is no solution seems

Supplement recommended in the document

[zloirock]

Thanks for the report. Added note about it.

[ghost]

var Test = Symbol();
var connection = new WebSocket('wss://echo.websocket.org/')
connection[Test] = 'Test'; // stackoverflow for IE 11 (Symbol.useSetter only)

check is WebSocket object use Symbol.useSimple ?

[zloirock]

@LiaoSept thanks for the warning. It's a very specific case, I think the note in the readme enough.

[ghost]

var TestObject = {};
Object.seal(TestObject);
TestObject[Test] = 'Test'; // Cannot define property 'Symbol()_m.*': object is not extensible

var TestObject = {};
Object.freeze(TestObject);
TestObject[Test] = 'Test'; // Cannot define property 'Symbol()_m.*': object is not extensible

[ghost]

@zloirock

[zloirock]

@LiaoSept sorry, I missed your comment.

Symbol polyfill uses defineProperty and defined in the strict mode, we can't detect the mode of caller code. I don't think something can be done here, you can propose something or add PR.