{"push_id":1172834217,"size":1,"distinct_size":1,"ref":"refs/heads/master","head":"657d3b2b97a0fd5ff1c353857f5b052f41bd3e0d","before":"1633b9aadab815e6daba17950c4ff81a80b896ed","commits":[{"sha":"657d3b2b97a0fd5ff1c353857f5b052f41bd3e0d","author":{"name":"Domenic Denicola","email":"8af53decf034cd6e55eaab2c9ec2801b277ccbd5@domenic.me"},"message":"Prevent double custom element reaction enqueuing via upgrades\n\nAs already discussed in the spec (as of #1365), it is sometimes possible\r\nto enqueue two upgrade reactions, via a constructor that does things you\r\nare not supposed to do. The fix in #1365 prevented upgrading twice.\r\nHowever, it did not bail out early enough, and allowed\r\nattributeChangedCallback and connectedCallback reactions to be enqueued\r\n(redundantly) before the bail-out. This commit moves the bail-out logic\r\nto the beginning of the algorithm, so as to avoid any such\r\ndouble-enqueuing.\r\n\r\nFixes https://github.com/w3c/webcomponents/issues/523.","distinct":true,"url":"https://api.github.com/repos/whatwg/html/commits/657d3b2b97a0fd5ff1c353857f5b052f41bd3e0d"}]}
{"actor":{"display_login":"domenic"}}