Waiting for content

I have the same issue!

Earlier today we experienced some issues across all browsers after a “bugfix” appeared to cause more issues than it fixed. Are you still experiencing problems and, if so, what browsers are you testing?

I was able to fix this problem by deactivating and reactivating the widget within the WordPress plugins menu.

I did contact kmueller62 and let him know that this simple fix worked for me, but it sounds like he’s still having trouble after trying it.

Edit: I was using Chrome 25.0.1364.172 on the Mac when I could replicate this bug.

I’m using both Chrome and Firefox. on a PC. As Tony said I deactivated, uninstalled, reinstalled, reactivated, and still having the issue.

Everything looks OK for me now.

Hey kmueller62, I have been trying to reproduce the issue using Chrome 26 and Firefox 19 but things seem to be working on my end. Are you using any addons in those browsers that could be interfering with scripts on the page?

Now I’m seeing this behavior on some posts, but not others (within the same blog). For example:

If I click the Send to Kindle button here, the popup appears, I log in, and I see the full post’s content within the popup (in other words, it works perfectly):

https://toc.oreilly.com/2013/04/goodreads-amazon-winners-and-losers.html

Now if I click the Kindle button on this article, I get the popup, log in, and get the dreaded “Waiting for Content…”:

https://toc.oreilly.com/2013/04/libraries-to-become-community-publishing-portals.html

I’m using Chrome 26.0.1410.43 (newest) on OS 10.8.3. The only extensions I have installed are Google PageSpeed Insights and 1Password, both of which are disabled.

Tony, the second article triggers a really fascinating bug. Check out the following snippet of HTML from your page:

<a href='https://toc.oreilly.com/tag/3ms-cloud-library' title='3M's Cloud Library Tag' rel='tag'>3M's Cloud Library</a>

You will notice that the title attribute contains a single quote that is not properly escaped! I am willing to bet that you are using a plugin where someone forgot to use esc_attr. The problem is that later in the popup, JavaScript loops through the attributes of this element, and one of them ends up being tag', an illegal name. So, we end up with something like this getting executed:

var fragment = "<a href='https://toc.oreilly.com/tag/3ms-cloud-library' title='3M's Cloud Library Tag' rel='tag'>3M's Cloud Library</a>";
jQuery(fragment).removeAttr("tag'");

Either jQuery or the browser cannot make sense of an attribute name containing the single quote, and an InvalidCharacterError is thrown that the popup never catches. I would recommend finding the other WordPress plugin that is generating invalid HTML. To stop this error in the short term, add .entry-utility to your exclusion list in the Send to Kindle advanced settings to stop the invalid markup from getting to the popup in the first place

Fantastic!

Thanks for your quick and thorough troubleshooting, David. Exempting .entry-utility worked like a charm. I can’t replicate this bug on any of the blog’s articles now.

Now I just need to dig deeper and see what’s causing those unescaped quotes.