That demo is a v. 4 demo, but if I'm correct, that intercept has been a CKEditor feature (or bug, depending on how you look at it) in earlier versions as well. Yet, the functions are unhindered & native in the CKEditor forms on Sitepoint. How was that accomplished?
I don't care about the security issues that are said to be the reason for the intercept. I have learned that the W3C has drawn up a draft that would make the IE method -- just ask the user to give permission for that site if the functions are called -- the W3C standard, and that the draft stands a good chance of being accepted. But implementation, and all (potential) clients updating their FF and Crome to a version with that standard implemented, may take quite a while.
If you wouldn't know how this was done on Sitepoint, maybe you would know the person(s) who would, so that I can send them a PM, asking them to join this thread?
Thanks in advance.