Thank you very much for looking into what my options could be. I tried your suggestion and find that I can detect the error but still end in that page. Perhaps its once again the speed at which this thing is going through. My listener triggers are a little interesting though. See below output from my logcat and my commentary (marked as ^^ ). Sorry for the length of this.
I/Corona (29621): Event type & URL is other file:///data/user/11/com.appynerds.xxx/app_data/infoFinal.html
^^ above, first time the listener is called for initial load request. Event type is other.
I/Corona (29621): Event type & URL is loaded file:///data/user/11/com.appynerds.xxx/app_data/infoFinal.html
^^ above, second time the listener is called for initial loading of my local html. Event type is loaded.
^^ above, I tap on the fake link pointing to my contact page. This is what I want to trap. Now the internet is off so this is supposed to return an error. Event type is link.
^^ above, fourth time the listener is called. event type is blank. URL is the last link tapped now coming back with an error. So far so good.
I/Corona (29621): error code -2
^^ further down in my listener I check for error and print the code. Still the same listener call (ie fourth time it is running)
I/Corona (29621): Event type & URL is history file:///data/user/11/com.appynerds.xxx/app_data/infoFinal.html
^^ in my error trap I call webView:back. What you see above is the 5th time the listener is called. How the event type is history and url is my original local html.
^^ Now this is bizarre... All was good until the 5th listener trigger and I was expecting to land in my original html page with an event type of loaded. I end up with a loaded for my contact page which gave me the error in the first place. Since internet is down I also end up with the Android's page not loaded message. Yikes.
So this 6th triggering of the web listener going back to the error page instead of obeying the webView:back is something I need to understand a little more and avoid if possible.