Midori did seem to work--at least it loaded up all right for me the first time--but perhaps you should change the default home page from
www.google.com in the distribution. Perhaps creating a local splash page that the browser defaults to would be a good idea.
In particular, this would be an excellent way to include some critical information that you haven't included in your posting above: such as which menu items work and which ones will brick the reader.
For instance, just to see what would happen (it's the old tech writer in me) I clicked on "Full Screen" and indeed got a full screen view of the browser--but also lost my tabs and any ability to call up the reader's task manager, or to close the program. This necessitated a reset of the machine to resolve it. The next time I opened Midori it showed me a crash-recovery dialog and then froze the machine exiting that. Now it locks the machine solid whenever I try to start it; my next step will be to do a reinstall and see if that works.
So, here's my suggestion: create a default LOCAL home page that includes information about what menu options are dangerous. (I haven't been able to try any others or I'd tell you about them here as well.) OR, better yet, if you can, disable those menu items in the build, or at least rename them, eg. instead of calling that menu item "Full Screen" call it the more accurate "Force Reinstall".
This experience was had on a 1.7 machine, by the way.
LATER NOTE: I tried a complete reinstall--no good. Having crashed once, Midori will no longer start. When I load the program it pops up a dialog saying it thinks it crashed last time, but any option I choose to get out of that causes the whole system to hang. The long and short of it is, Midori is on my system but no longer works at all.
I wouldn't recommend this build to anyone until these issues get sorted out.