- From: Tab Atkins Jr. via GitHub <sysbot+gh@w3.org>
- Date: Tue, 04 Apr 2017 18:11:00 +0000
- To: public-houdini-archive@w3.org
"Jank" in the "looks terrible" meaning, not the "slow/jittery" meaning. I don't *necessarily* need Array subclasses. At bare minimum, I need a value iterator; currently, those are broken in WebIDL and force you into being a Proxy. (This is why I said, in one of the IDL issues, that I could work around it by just using a kv iterator and manually setting up the keys as meaningless indexes - that gets me in the neighborhood of the correct behavior that value iterators *should* have.) Having an Array subclass would be *ideal*, tho - without it, we can't reasonably make some of these classes mutate-able. Currently we're planning on just accepting that, so that you have to create fresh objects instead; alternately, we could go the terribly ugly route of having .get/.set arrayish methods. -- GitHub Notification of comment by tabatkins Please view or discuss this issue at https://github.com/w3c/css-houdini-drafts/issues/239#issuecomment-291585268 using your GitHub account
Received on Tuesday, 4 April 2017 18:11:08 UTC