These are some readers' responses. Read the full article to see what all the fuss is about.
-
Popular
Categories
- .Net & C# (1)
- Architecture (3)
- C++ (5)
- Coding (4)
- Copyright, etc. (3)
- HTML/CSS (2)
- Java (14)
- JavaScript (6)
- JUnit (3)
- Recommendations (9)
- Risks (8)
- Software projects (2)
- SQL (4)
- Testing (6)
- Tools (5)
- Usability (1)
- Web (5)
- Web publishing (16)
- Windows (1)
- WordPress (27)
39 responses
Other comment pages: « 1 [2]
NIIIIIIIIIIIIIIIIIIIIIIIIIIICE!
hello!
I have a similar problem with ajax callbacks… but I cant see a way to use this plugin to resolve… can you help me please?
Thanks
Thanks this is exactly what I was looking for!
I would recommend renaming this to jquery.elementReady.js as this better reflects the name taken up by this in the jquery object.
Very cool idea. I think this is definitely something that once tested more should be placed in jquery core. Performance is a big deal!
Evan, you’re right; I should rename it. Perhaps in the next release.
I found onElementReady, a similar plugin that does more or less the same thing. It takes a slightly different approach and has different tradeoffs. When I have time I may even see if my own plugin could benefit from some of these ideas.
This website is now testing the next version of elementReady. The only substantive change is that you can now change the polling interval from its default of 23ms. Not that you’d want to do that…
On closer inspection, I can’t really use any ideas from the other onElementReady plugin mentioned above. It offers more functionality but is consequently less robust and scalable than elementReady. I can’t believe I just used the “robust and scalable” buzzphrase!
Other comment pages: « 1 [2]