jQuery and Cross-site Scripting
·
Never trust user input, even if it’s coming from an allegedly trustworthy source.
·
Never trust user input, even if it’s coming from an allegedly trustworthy source.
·
One of the first critiques I find myself writing while I review JavaScript code is “cache your selectors.”
·
I like abstraction layers because they make life easier for developers. I dislike abstraction layers because they raise issues for new developers who have yet to master them.
·
A message in my inbox this week asked for help removing jQuery from the front-end of a site. In this particular case, jQuery wasn’t being used and just slowed down the page.
·
Last year, I had the opportunity to present at jQuery Portland about unit testing. It was my first non-WordPress speaking event, and it was incredible!
·
I use Vagrant for local development on WordPress. It made perfect sense to use it for local jQuery development, too. This weekend I put the finishing touches on a patch to add Vagrant support to the jQuery project – now you can leverage the power of this awesome tool as well!
·
As a moderator on the WordPress Stack Exchange, I end up spending a lot of time on the site. I see lots of great questions, lots of not-so-great questions, and several you’ve-got-to-be-kidding-me questions. But the question I see the most often frustrates me: How do I remove WordPress’ jQuery and use Google’s CDN version instead?
·
Some time ago, I made a mistake. Rather than taking the time to truly understand how events worked in jQuery, I built my own JavaScript library to handle event delegation. It worked, but why reinvent the wheel? It turns out jQuery is perfectly capable of serving as a global event bus for all of your