Are they somebody looking into this ticket?
I assume so, but I think there is a backlog.
If there is progress by the assigned technician, Can the technician update the same?
Sham, this bug has not yet been triaged; you'll need some patience.
Approxi(In reply to Jean-Yves Perrier [:teoli] from comment #5) > Sham, this bug has not yet been triaged; you'll need some patience. Approximately, how much time would it take?
Any update on this ticket?
I think the only problem in the exposition lies in the "More flexible constructor" section. Here, and in the immediately preceding figure, the inheritance scheme seems to be incoherent with the initial presentation which used "constructor.call(this)", indeed here that constructor invocation is lost, so it appears legitimate to ask where, in this new presentation, the inheritance lies.
I think there is a major problem in the article. The article says that the properties added to WorkerBee by constructor Employee are inherited properties through the prototype. But this is wrong. The constructor function Employee() is not called as a constructor and adds the properties in the worker object itself.