Buzztouch team: I hope you can take a few and give me your thought I know 'old' 1.4 stuff.... Okay so trying to get the webview to show the location of a users when on a webpage, if the page is using GeoLocation. I am trying to figure out how to put the below code into the Screen_customURL. webView.setWebChromeClient(new WebChromeClient() { public void onGeolocationPermissionsShowPrompt(String origin, GeolocationPermissions.Callback callback) { callback.invoke(origin, true, false); } });

Forgot to add the link to the class. http://developer.android.com/reference/android/webkit/GeolocationPermissions.html So I have the min Aandroid:minSdkVersion=7PK level set to 7 to use this class.

So.. much longer discussion needed, and I don't mind having it offline, but for now.... WebViews in Android use one of two possible setups. Either a WebViewClient or a WebChromeClient. The difference is how they process HTML, Javascript, and other browser-centric things. In most cases, programmers generally think the WebChromeClient is 'better' and more flexible. v1.4 does not use a WebChromeClient, it uses a WebViewClient. This is because chrome didn't exist (in Android) when it was written, not because it's somehow necessary or needed or whatever. Either should work but the Chrome client is needed to use what you're mentioning. So... it's a matter of 'converting' Screen_CustomerURL.java a bit. Look at that file and find where it sets the web client (around line 79), you'll see it easily. Next, visit a few URLs, like this one http://lexandera.com/2009/01/adding-alert-support-to-a-webview/ and see if you can get your head around the difference between the two approaches. If you can, cool, just change-it-up to use the Chrome Client instead. This is for sure where we are headed with 1.5. Have not done any of the HTML logic in 1.5 for Android yet. If you can get the ChromeClient running, getting the onGeoLocation part to work will be easy (with a little hacking around of course)

Yeah that is right where I was looking at. The issue I was and still having is the the 'override' methods around the 'intent' causes errors. It's looking like more of coverting the entire class to get 'ChromeClient' to function.. I thought I had it working but the page just keep saying loading... I have been though lot's of samples etc. I'll keep at it. I have a nice travel app that will needs this function.. So it is keeping it from going live.