Compatibility with Licorize

Ask for help about NoScript, no registration needed to post
mfel

Compatibility with Licorize

Post by mfel »

I recently tried to start using Licorize (http://licorize.com/applications/licori ... /index.jsp), sort of a hybrid bookmarking/task-management app. They have an extension and a set of bookmarklets, neither of which seems to work if the domain for the host page (the page you want to bookmark) isn't allowed, even if licorize.com and googleapis.com (which the bookmarklet calls) are allowed. I'm not sure what the problem is with the extension; for the bookmarklet, I can tell that it's working part of the way (a div with an iframe is created), but then something goes wrong. My Javascript knowledge isn't good enough to figure out where it's going wrong, though.

If the domain for the host page is allowed, the extension and the bookmarklet seem to work fine.

I don't know if there's anything you can do on your end--this might be something they have to fix. The issue has been brought up on their support site (http://community.licorize.com/questions ... e-noscript), but the developer just replied "We assume JavaScript enabled."
Mozilla/5.0 (Macintosh; U; Intel Mac OS X 10.6; en-US; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.15
User avatar
Giorgio Maone
Site Admin
Posts: 9524
Joined: Wed Mar 18, 2009 11:22 pm
Location: Palermo - Italy
Contact:

Re: Compatibility with Licorize

Post by Giorgio Maone »

In fact, if they work inside an iframe there's not much I can do about it.
NoScript already tries its best to let bookmarlets work on JavaScript-disabled pages, by running all the code is possible to run in multiple event loop passes while temporarily enabling JavaScript, but to let the code be called back after an iframe has loaded it would require JavaScript either to be kept enabled or to be re-enabled asynchronously, which is very difficult if not impossible.

Therefore, they should either change the way they implement their bookmarklet, to make it work as synchronously as possible, or write their add-on the proper way, which absolutely doesn't require JavaScript to be enabled on the content-side in order to work (otherwise NoScript itself couldn't exist).
Mozilla/5.0 (Windows; U; Windows NT 5.2; en-US; rv:1.9.2.15) Gecko/20110303 Firefox/3.6.15
Post Reply