- From: smaug---- <notifications@github.com>
- Date: Sun, 25 Jun 2017 09:59:33 -0700
- To: whatwg/dom <dom@noreply.github.com>
- Cc: Subscribed <subscribed@noreply.github.com>
- Message-ID: <whatwg/dom/issues/208/310914332@github.com>
> Yes. It's the one discussed at length in this thread, and concretized by PR #469. I noted you commented over there, so I'm a bit confused why you state here you're unable to find the API proposal. PRs should be for actual changes for the spec once the proposal is ready. I wasn't going to do any review there. It makes tracking all the discussion hard if some discussion happens in issue and some in pr. PR should be just once the proposal is concrete and just minor editorial reviews are needed. > Yes; jQuery is a prime candidate, since that is where this feature originates. As are all the frameworks built on top of it. In general this feature is highly desired by frameworks since they like to be able to manage their event listeners en-masse. What about other script libraries than jQuery? React.js happens to be hip and cool currently, would it use this stuff? What about other libraries? > I certainly understand that everything has a cost. I'm a bit surprised you think I need to be reminded of that. We all need to be reminded about that all the time. Or at least I need to remind myself. (Sorry if I'm a bit reluctant right now. I just happened to review implementation for .labels attribute recently and realized how bad API even such a small feature can be - if implemented correctly, it slows down pretty much all DOM mutations) -- You are receiving this because you are subscribed to this thread. Reply to this email directly or view it on GitHub: https://github.com/whatwg/dom/issues/208#issuecomment-310914332
Received on Sunday, 25 June 2017 17:00:10 UTC