I am battling a problem. Very annoying.
Web links keeps opening in chromes in-browser instead of links opening up in google chrome beta for android.
I think this is called android system webview.
How do I stop this behavior?
https://youtu.be/GMqcHPOtpLo
Related
Hey all,
This problem has been killing me for a few days, I've tried searching the web and so far I've come up with not much.
I've got a widget which uses a WebView to load a page from a URL and read the contents of the page. The reason for the WebView is that I need to emulate the browser in order to get the page to display the content, a HttpGet won't get it back (reliably).
None the less, at some point the WebView stops loading new content and appears to keep loading a cached page instead. In the code it appears to have gone to the web to get a new page but what is returned is old data.
Those with the Android 2.2 build get a new button for applications in the settings area which allows them to clear the App Data. Doing this blows away whatever cached data the WebView is using and it starts to work again.
So what I would like to do is programmatically blow this App Data away. Only problem is that I have no idea what data it is. I'm not explicitly make it anywhere in my app, the WebView control appears to be making it itself. Would anyone know what is going on here and how I can avoid it?
I've turned all caching off (in every way), it had no effect.
Code:
browser = new WebView(context);
browser.getSettings().setJavaScriptEnabled(true);
browser.getSettings().setCacheMode(WebSettings.LOAD_NO_CACHE);
browser.setDrawingCacheEnabled(false);
browser.clearCache(true);
browser.addJavascriptInterface(new MyJavaScriptInterface(), "HTMLOUT");
browser.setWebViewClient(new TelstraWebViewClient());
browser.loadUrl(URL);
Cheers
As I am a newbie, I am not able to start a thread in "Nook Touch Android Development", so I post the thread here.
I am focusing about rooted 1.1 nook touch.
I just wonder if this is my own problem or it is a common problem,
that the webkit component seems to have problems.
The the problem is, any app using the webkit component, when the user scrolls the view, or even "touched" the webkit view, the app cannot update the view again. although in some apps, user can still scroll it, but the app cannot put in new information.
For example: the default build-in browser, it is normal if i just click the url and change it, it will jump to the required web page. but once i touch the main view, i cannot refresh / go to another web page.
not only for default browser, as it is useless for a rooted nook. but other apps may also use webkit component for formatted text. this problem will affect numbers of apps that we can use.
anybody here have the same problem with me?
i am using firmware 1.1 and rooted by SalsichaNooter 0.4
Thanks, and sorry for my bad english
no one have such a problem?
i even tried to write an app, having 2 buttons and a webkit view
before "scrolling" the webkit view, everything is fine
after i "scroll" the view, both buttons cannot work
but the program is not hang, just the webkit is not able to refresh again
i also uploaded the apk
could anybody have a try?
Our school app loads a webpage within a webview and, like the right click > Inspect to view source and properties of a website in chrome, is there a way in Android to view the HTML/CSS etc... of a page loaded in webview? Alternatively, is there a way to figure out exactly the link of the page in the webview so I can enter it in a normal browser to Inspect on chrome?
Chrome or Android System WebView?
On the v20 WebView is actually disabled, on the Motos you have to go into developer options to change to chrome.
Chrome seems to run faster but starts stuttering after awhile.
The other option I suppose is not to use WebView at all and open in a chrome tab.
I go out of my way to turn off webview and redirect to chrome browser.
How can I integrate eg. Bromite as the default renderer for news items?
Always opening them in an external browser is annoying, yet I strongly detest the autoplay "feature" in the normal chrome browser. Installing an old version on chrome might fix the autoplay issue, but might also remove useful features (eg. tab groups) and possibly introduce security vulnerabilities.
I'd prefer non-root/non-flash solutions, but if such options don't exist, I'm also interested in root/alternative rom solutions.
Is there another subforum where this question is more likely to be answered?