- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Thu, 22 Feb 2018 20:01:30 +0000
- To: public-houdini-archive@w3.org
Right, per <https://github.com/heycam/webidl/issues/258#issuecomment-285157433> I'm just implicitly pretending that every attribute auto-defines a backing slot, so I can manipulate that instead of incorrectly trying to do something with the public property. Until IDL decides one way or the other on that topic, I don't think I can reasonably have Bikeshed auto-define slots for everyone, and I'm definitely not going to manually define slots for every single attribute on every single interface (along with manual definitions of the fact that the public property reflects the slot, etc) - it would just be horrifying to read/write. (This issue confused me quite a bit, as I use this convention thruout the entire spec; I thought something weird was going on in this particular spot for you to point it out.) -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/711#issuecomment-367803759 using your GitHub account
Received on Thursday, 22 February 2018 20:02:04 UTC