Dec
6th
2013
Aaand Knighty broke it again. And I fixed it again, I think. · 5:37am Dec 6th, 2013
Title says it all. This time, both the script and the style will need to be updated.
This one took significantly more tweaking to fix. Certain element ID's were removed, at least, and I just cleaned it up best I could. This is not how I wanted to spend my evening. If this keeps happening, I'm not sure what I'll do 
Report
Cast-Iron Caryatid · 236 views
·
Thank you again for all your work with this.
I'm not sure if this affect what you are working on or not, but...
Userscipts & AJAX Subrequests
1590062
I am quite aware of that, yes. I've actually been quite active in the comments there in support of the decision. Under normal circumstances, I would have already made a blog post to assure people that they can keep using my script, but I haven't actually gotten a response to my inquiries
Rest assured, as-is, my script is perfectly in line with the letter of the rule. The only AJAX requests it makes are single actions in response to clicks to refresh the page without reloading it. My concern is with the larger cover images loaded by the script. They're not loaded with AJAX, but they do result in more data transferred, as well as more http requests when the page is loaded fresh (The smaller versions are first requested, then the script loads, replacing them with higher resolution versions, which the browser automatically requests).
I will poke the admins again about this, but the worst case scenario is that I am forced to remove the cover image replacement functionality from the script, which I will do if that's what they want.