Google cannot read ALL JavaScript in every situation. Yet **they most definitely can read at least some of it in some situations. **
The article quoted was from 2012. A LOT has changed since then.
A May 2014 post up in the Google Webmaster Central blog mentioned how they can read it / execute it sometimes, while others they can't, though they do not go into specifics.
A direct quote from Matt Cutts:
“Once that JavaScript has all been loaded, which is the important reason why you should always let Google crawl the JavaScript and the CSS – all those sorts of resources – so that we can execute the page,” he continues. “Once we’ve fetched all those resources, we try to render or execute that JavaScript, and then we extract the tokens – the words that we think should be indexed – and we put that into our index.” source: Webmaster Video April 7, 2014
Oh - and if you block that JS in your robots.txt file, Google MAY respect that, and Google MAY ignore that. While Robots.txt files USED to be a firm "directive", nowadays they're "just one more signal / hint".
Do not assume that in your unique situation Google will or will not find that content, they will or will not see it as duplicate content just because they "may" or "may not" be able to figure out your JavaScript.
Want to avoid that insanity? Yeah - generate the content you contain in those pop-ups on actual unique URLs that get loaded in those pop-ups. Then, on those specific URLs, do a noindex,nofollow meta robots tag, AND a canonical tag pointing to the main product description page where that content appears in its primary form.
Or write entirely unique content for those pop-ups.