Board Thread:New on Hitler Parody Wiki/@comment-4356266-20140513213156/@comment-4356266-20140514185459

It does took a while. With the YouTube API there are the manuals provided by Google, so I can always refer to the document now and then.

Processing the returned data takes a lot longer to figure out. Because the way the response (in XML) are formatted, and the fact that some browsers' javascript engine parses XML differently than others, I have to stick to gecko/Firefox's engine (being the FF master race that I am :P ) when writing the script. The biggest obstacle is parsing the publish date YT gives back (reads something like this: "2013-04-09T17:37:40.000Z") into a human-readable format.

After that there were the testings. I need to figure out how to tell jQuery to correctly position the popup (including not letting it overlap the first-level heading).

And then Darwin and the Visual Editor came out. These introduced new code into the website as a whole. Back then I was unsure if the bugs experienced by some people are a result from the popup itself, the popup's script interfering with the native script, the native script itself, or any combination of the above. That's why I pulled back the open beta twice.

With the new features having its implementation stabilized, I feel that it's the right time to bring back my script. I still don't know if the previous problems by several editors was even partly caused by my script - I have the script running for my personal use for months and nothing severe happened.

There is still problem with the parsing, as I can tell. I opened the wiki on Chrome on a whim and found that Chrome's javascript couldn't parse some of the numbers, thus they appear as "NaN". I could brainstorm into how to fix it, or I could just tell prople to use Firefox instead. :P