-
Notifications
You must be signed in to change notification settings - Fork 58
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Replace events.js to be more interop #104
Comments
Haha, actually they are 98. ;d |
Something Tram-One does in it's fork of nanomorph is take in a function which should supply a list of events. This allows frameworks to keep track of their own list of events, or apps to provide which events should be kept track of. At worse, most apps provide a hard-coded list of events, which should have the same performance as the current implementation, but allows consumers to append new events. At best, frameworks can keep track of events, in the same way jQuery does (with it's own event attachers) or Tram-One does (using |
Hm yea, this sounds like a good idea too. |
I'd be willing to make a PR for these changes against nanomorph if people were interested. It wouldn't even have to be breaking (we could have a default list that might be tree shaken out, depending on how the final bundling works) |
Something like this
Also, currently, there are only 45 event names, but as of today it seems they are 95. As, probably no so common or used, but why not. Also it will decrease the bundle sizes, and will use this list only on server.
The text was updated successfully, but these errors were encountered: