InformAction Forums

Hi all,
I'm using Firefox 12 and I've installed Grabmybooks.

This extension grabs content from web sites and converts it to e-books and you can open a page inside the browser where you can see and/or edit your e-book.

Problem is that it's not possible to see the images in any window of this extension. Grabbed content from other sites or preview of the cover you can select from your pc. The page created by GMB has no address (also, if I try to see the page code it's the about:blank one) and NoScript doesn't show anything relevant in the menu (I've already allowed about:blank but that's not enough).

Globally allowing all scripts works and I can see all the images I need, so I think there's something that should be allowed but I don't know what...

I've seen the ABE FAQ but I don't know what I should write in the exception and I'm not even sure if that's the part where I should add something.

I've contacted the developer of GMB and he's working on it but since I told him maybe I was going to ask here as well he told me I could ask if there is a way to not block the content of tabs with a certain name as the tabs of GrabMyBooks have a specific name ("grabMyBooks - My Book" etc.).

I've seen someone was requesting something like that, though, so I guess it's not possible at the moment...

Do you have any idea on how to make it work?

Thanks in advance,
Rb

rb12 wrote: Globally allowing all scripts works and I can see all the images I need, so I think there's something that should be allowed but I don't know what...

I agree; that sounds likely. Have you looked in the Recently Blocked Sites menu? It sometimes shows sites that don't appear on the main menu (for complicated reasons).

The problem seems more subtle than just "don't block this tab".
In facts, the images are not blocked, but just appear not to be inserted by the extension unless scripts are globally allowed.
I suspect the developer needs to switch some of his inline script execution to use Components.utils.Sandbox, because I've already observed glitch in execution of scripts in the context of about:blank windows with recent Firefox versions, which are worked around by running through a sandbox.

Thanks, I told him about this topic so I guess he'll read your advice soon.

@Thrawn: I did but I didn't notice anything that seemed to be connected with that specific page.