Consider allowing <polymer-element> to accept a prototype chain

[sorvell]

A user tried this construction inside a

Polymer('x-foo', (function () {
  var knob = function() {
    this.foo = 'foo';
  }
  knob.prototype.zonk = 'zonk'
  return new knob();
})());

The user was confused that the resulting element had a 'foo' property but not a 'zonk' property.

[sorvell]

The complexity seems unwarranted at this point. Instead, we should issue a warning if the object passed itself has a non-trivial prototype.

[sorvell]

Dup of #647.

[sjmiles]

#647 is a dupe of this issue (#211), not vice-versa.

[florianv]

I was experimenting with Platform.mixin and I found a workaround trick to have the prototype chain taken into account when registering a new element.

function Entity() {
    this.message = 'Hello!';
}
Entity.prototype.created = function () {
    console.log(this.message);
};

function Person() {}
Person.prototype = new Entity();

// The resulting object will be an instance of the first argument
// The prototype chain of the second argument will be taken into account
Polymer('some-element', Platform.mixin(new Person(), new Person()));

[tjsavage]

Closing this issue due to age and the release of version 1 release of Polymer - please feel free to re-open if this is incorrect.