- From: Bede Overend <notifications@github.com>
- Date: Tue, 29 Aug 2017 23:04:40 +0000 (UTC)
- To: w3c/webcomponents <webcomponents@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
Received on Tuesday, 29 August 2017 23:05:21 UTC
I've come across what I think is a bug in CE Upgrades, however I'm not sure if it's intended, and apologies if I'm missing something in the spec. Basically, if my Custom Element definition uses a getter and setter, these will be overwritten with the corresponding property _value_ that exists on the element when that element is upgraded, losing those getters and setters. See [this JSBin](http://jsbin.com/ribused/2/edit?js,console) - the first element after upgrading retains the initial `foo` value, and the getters and setters are lost. The second element which is created after the CE definition is registered, demonstrates expected functionality. Reading the [upgrades definition](https://html.spec.whatwg.org/multipage/custom-elements.html#upgrades) I can't quite figure out intended behaviour? Not sure if in fact I should just be reporting this to Blink / WebKit -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/w3c/webcomponents/issues/660
Received on Tuesday, 29 August 2017 23:05:21 UTC