Closed j5bot closed 13 years ago
Sorry for the silence. I've been trying to come to a decision on this one.
On the one hand, loadOnce() is valuable. On the other, it adds a lot of bytes. But meh, not a huge deal, and it can be optimized.
Complicating this, though, is the fact that LazyLoad is kind of in maintenance mode these days. I'm not using it much myself, although I do want to keep it usable. I'm not sure I want to add any major new features to it, though. There are other script loaders with lots of great features. I think LazyLoad's strength is in doing the bare minimum, but doing it well and with very little code.
So, while I'm grateful for the patch, I think I'd prefer not to pull this change, but I'd encourage you to maintain it in your own fork.
.both() method implemented as .load, added once parameter to .js() and .css() methods as well as helper method loadOnce()
commit message: added load(), loadOnce() methods to allow for mixture of CSS and JS urls as well as ensuring that a particular resource is only loaded once